Product and engineering guides
Latest guides
Why Your Developer's Estimate Keeps Moving
Estimates move for five common reasons. Three of them are legitimate and two are not, and the difference is visible in how the reason is described.
What a Technical Audit Is, and When to Commission One
A technical audit is a read of the system by someone with no stake in how it was built. What it covers, when it is worth commissioning, and what to do with it.
What to Ask Your Development Team Every Week
A practical weekly agenda for a non-technical owner: the four questions that cannot be answered with a confident paragraph, and what a real answer sounds like.
"It's 90% Done" and What That Actually Means
Why "nearly finished" is the most expensive sentence on a software project, what is usually left when it is said, and how to check it without technical knowledge.
How to Tell If a Software Project Is Really Behind
The difference between a project that is hard and a project that has stopped, and the four signals that separate them without anyone having to read code.
How to Read a Sprint Report Without Being Technical
What each part of a sprint report is measuring, which parts can be gamed, and the three things worth looking at if you only have five minutes.
Building the product for what comes next
We would rather deliver one product that holds up than three that have to be rebuilt. That standard is the same on every project, whatever its size.
Ali Boran GazelCEO