Common questions
Frequently asked questions.
What does a maturity note actually contain?+
A maturity note is a written document of typically four to eight pages. It places the team at a named point on a maturity arc, describes the evidence that informed that placement, and lists a small number of specific, low-cost changes we believe would move the team forward. It does not prescribe tooling and is written to be read by the engineering team and shared with management as the team sees fit.
Do we need to prepare anything before the sessions?+
We ask for access to your CI/CD pipeline dashboard, a recent deployment log, and a brief conversation with whoever owns releases. Beyond that, we work with what is present — not with documentation you might feel you ought to have prepared.
Are the sessions conducted remotely or on-site?+
Both options are available. Most engagements run as a mix of remote observation and one on-site session, particularly for teams in the Klang Valley. For teams further afield, fully remote delivery is practical for the maturity review and pipeline advisory. The release workshop tends to benefit from everyone being in the same room.
We are a government-linked company. Can we engage you?+
Yes. We have worked with technology teams in both private and public sectors in Malaysia. Procurement can be handled by purchase order. Contact us to discuss the formalities before committing.
What if the review reveals more work than expected?+
The scope of each engagement is fixed. If our sessions reveal a situation that would benefit from a different or deeper engagement, we will say so in writing in the closing note — but we will not expand the current scope or re-price mid-engagement. You are free to return for a further engagement, and we will carry the context.
How long before we receive the written output?+
We deliver within five working days of the final session for the maturity review, within ten working days for the pipeline advisory document, and within three working days for the release workshop summary. These are the timelines we observe in practice, not minimums we commit to under pressure.