
Demystifying Agile Estimation and Planning
Estimating in hours can be highly inaccurate. Estimating using relative wide band delphi like planning poker is key to understanding what you can do and when you can do it by as a team.
Estimating in hours can be highly inaccurate. Estimating using relative wide band delphi like planning poker is key to understanding what you can do and when you can do it by as a team.
Teams were bored with their Retrospectives. I was bored. They were just doing mechanical Scrum. Retrospectives are such a powerful tool to drive continuous improvement, so here’s what we did to fix the problem.
Agile Teams tend to use relative estimation rather than creating tasks, estimating hours, and then adding up all the hours.
How should we size Stories? Not by hours but through looking at new work relative to the size we gave to old work.
Sizing in Story Points represents a significant shift from estimating in hours. Understanding cycle time is key to getting it right.
So, what actually is a Spike? Where does the term come from and should all agile teams use them?
What’s an easy way to run a Backlog Refinement session so that assumptions, risks, ideas and draft designs are identified? Yin and Yang is one of our favourite patterns.
The Product Owner is a role in many Agile Frameworks. They are responsible for optimising the delivery of products and maximising the value of the work of the Team. But what does a Product Owner do?
The Scrum Master is a role in Scrum – an Agile Framework for optimising the delivery of products. In most
As an Agile Coach and Chief Scrum Master responsible for 8 teams in a service delivery program, when things went
© 2019 All rights reserved