What if boss Peter runs into the office screaming 'OUR IMPORTANT CLIENT WANTS A FUCKING PINK BUTTON WHICH MAKES HEARTS APPEAR'?ĭevs tell boss to shut the fuck up and talk to Karen. Approximate due dates are assigned, Bob is a happy Bob. The sprint is filled with tasks, from the top of the global button backlog, up to the team's capacity as determined by velocity. They use the average of the last 5 sprints to calculate each developer's 'velocity'. Difficult tasks are broken up into smaller tasks, because there is a scrum point upper limit. Once every two weeks (a 'sprint') the button team convenes, uses the ease scores to assign scrum points.

The global buttonbacklog is sorted by priority. These three scores are combined to give a priority score. The button team compares the request to a reference button they've built before, and gives an ease score, with higher score being easier (inverse of scrum points). Karen asks the button team how hard it is to build a button. Karen assigns points for potential and impact (how much does a blue button improve Bob's life, how many people like Bob desire blue buttons) Sales employee Bob wants a clickable blue button.īob tells product owner Karen about his unstoppable desire for clickable blue buttons.