Select Page

Milestones

Product owners and stakeholders like to keep an eye on the overall timescales. Provide a high level view of milestones and dates at each demo, explaining that these are not set in stone and will shift according to the work that takes place during each sprint....

Game changers

Based on feedback, learning from the retro, the current bashboard and budget, what do we know that will affect the project? Does the product owner have anything to declare that might impact the ultimate goal, scope, cost or budget?

MVP realignment

If certain tasks that have not been completed during a sprint, the scrum master must be honest about this and provide an explanation. It could be that the team have uncovered something which changes the overall estimate of the project, or if could be that the...

Bashboard

The Bashboard is named after our very dear scrum master, Barry Ashford. As well as being whimsical, this board helps the scrum master to manage blockers. Sometimes work cannot continue because of a blocker, and in this case, the sprint review is the perfect time to...

Burndown

The burndown shows where we are in terms of scope and cost. This graph can be exported directly from Visual Studio (look for the burndown icon in the top right corner). It’s important to make sure that the whole team keep their timesheets up to date, so that the...

How to run a demo

The scrum master hosts the demo, acting as compare as the developers talk through their tasks in the backlog, explaining the acceptance criteria and showing how they work in practice on the big screen. Allow 2 hours for the meeting and book a private space with a big...