Agile fundamentals for teams

A review is an opportunity for teams to reflect on the work they've completed and share it with others. It’s a moment to pause, inspect the outcome of a delivery cycle, and decide on the next steps.  

In this video, we’ll walk through the purpose of a review, how to structure it, and the benefits it brings. 

The main purpose of a review is to inspect the outcome of the delivery cycle. It’s a chance for you to show the work you've completed and to engage in meaningful conversations about it. It's not only a demonstration. It's an opportunity for feedback and discussion that can inform your next steps. By the end, you and your stakeholders should have a clear understanding of the progress made. You can also discuss any necessary adjustments and what you'll focus on next. 

A review usually lasts around 1 to 2 hours for a 2-week delivery cycle. You can structure the session by: 

• Showing the work you’ve completed. 
• Celebrating your successes and acknowledging achievements. 
• Explaining any new insights or learning you’ve gained. 
• Raising any challenges or blockers encountered. 
• Discussing what’s next: setting the stage for the upcoming work. 

This keeps the review focused, informative, and action oriented. 

There are a range of methods teams can use for this. It's about finding what works for you and your context. Some examples of what others have done include: 

• Creating a team wiki to document and present their work. 
• Writing blog posts to share progress and learnings. 
• Publish open-source code to share technical advances. 
• Run a show and tell presentation to showcase what they’ve accomplished. 
• Publish a product metrics dashboard to give a data-driven view of a product’s performance. 

You can be creative in how you run your reviews. The key is to ensure transparency and openness with all involved. 

Reviews bring several benefits: 

1. They keep stakeholders informed about progress, making the development process more transparent. 
2. They allow you to gather valuable feedback. This helps you refine the product and align it with expectations. 
3. It promotes "Governance as You Go". Rather than a lengthy summative report at the end of a project, reviews give regular updates. This approach helps keep you on track without heavy documentation. 

By holding regular reviews, you can continue to adapt and improve. This in turn creates a more collaborative and informed development process. 

A review is a key part of your journey toward delivering value to users. This happens by showcasing your work, engaging stakeholders, and discussing your next steps. As a result, you can ensure you remain aligned with goals and respond to feedback.