Defining a Minimum Useful Version of a Software Project
A first release should complete a useful journey, even if it does not include every future idea. Reducing scope works best when the remaining experience…
Read guideTHE STUDIO JOURNAL
Practical articles on project planning, with checklists and related reading.
Showing 1–8 of 8 posts
A first release should complete a useful journey, even if it does not include every future idea. Reducing scope works best when the remaining experience…
Read guideAcceptance criteria describe how the agreed work will be checked. They are more useful when they refer to observable behaviour than when they rely on…
Read guideDiscovery is more productive when the business brings examples of the problem rather than only a preferred solution. A few real records or customer…
Read guideNew information can change a project, but the effect on delivery should be made explicit. A small-looking request may affect content, data or testing beyond…
Read guideUser testing can begin with a few realistic tasks and careful observation. The aim is to find where people misunderstand the product, not to collect…
Read guideMaintenance should identify recurring responsibilities rather than simply promise that the website will be looked after. Content, forms, integrations and…
Read guideTwo quotations may cover different work even when their headlines sound similar. Compare the deliverables and responsibilities before treating the total…
Read guideA post-launch review should compare the delivered website or application with the goals agreed at the start. It is an opportunity to learn from real use,…
Read guideFROM IDEA TO SOMETHING REAL
Tell us what you’re trying to create, improve or automate. You don’t need a technical specification — just tell us the idea.
Start a project