Rules to Better Specification Reviews
- Do you know what a Specification Review is?
- Do you conduct a Specification Review? (ask for a coffee not a marriage)
- Do you have corridor conversations?
- Do you know how to add value to a Specification Review?
- Do you use AI to generate your Specification Reviews?
- Do you know the Specification Review deliverables?
- Do you include general project costs in your estimates?
- Do you know how to give the customer a ballpark?
- Do you effectively present the outcomes at the Specification Review presentation?
- Do you know how thorough your customer's specifications are?
- Do you use User Stories format when appropriate?
- Do you make sure that all stakeholders are involved in the Specification Review?
- Do you know how to get accurate information from clients?
- Do you limit the project scope?
- Do you schedule a follow-up meeting after the Spec Review?
- Do you aim to start the work soon after the Specification Review?
- Do you shadow Spec Reviews?
- Do you know the value of User Journey Mapping?
- Do you know the value of Event Storming?
- Do you know how to run an Event Storming workshop?
- Dynamics and Teams - Do you link your customers in CRM to their respective Teams?
- Backlog - Do you keep your PBIs smaller than 2 days' effort?
- Do you know how to choose the best software architecture for your system?