In a recent agile podcast, one of the hosts said that story points existed "just so that some manager can get a report." That opinion might fly in a fantasy world where investments are made without any sense at all regarding what value might be provided, but that's not how the real world of business … Continue reading Getting Real About Story Points
On a large-scale agile project/program with multiple Scrum teams working toward the same overall goal, having user stories sized in a way that makes it easier to re-assign them from one Scrum team to another provides provides a planning and execution advantage when balancing work across teams to optimize delivery dates. Before adopting a common story points scale, there are a couple … Continue reading Normalizing Story Points Across Teams
A mature agile team intuitively knows what a story point means in terms of the relative size of a user story compared to other stories that it has sized in the past, but how does a new team that perhaps even has people who are new to agile get started with story points? As I … Continue reading Getting Started with Story Points
Sizing user stories is a key part of understanding the overall effort required to create a product release. Getting started is simple: pick a baseline story and assign a number of Story Points or Ideal Days that it will take to complete the story. Next, look at other stories in the backlog and decide whether … Continue reading Story Points or Ideal Days?