Occasionally, it is useful to set up a demo on a regular cadence to ensure cross-functional iterative alignment. This is helpful for high-impact deliverables that require integration across multiple functional teams. This is in-line with the seventh principle of the Agile Manifesto: "Working Software is the best measure of progress".
For multi-person groups or critical projects, we use a heavier weight grading process:
The demo master grades each step during the demo meeting. To make it less subjective, we use a scale that is widely understood and communicated. Our scoring definitions are as follows:
|5||Signed off from all Stakeholders|
|4||Demo'd according to the "definition of done"|
|3||Demo'd but incomplete and/or has bugs|
|2||Demo'd in some rudimentary state, work has started|
|1||Not yet started or cannot be demo'd|
A different demo process is used by the Single-Engineer Groups and does not require a demo score card.