Sprint planning is typically an industrious, productive process. Teams refine the backlog, set a target velocity, select user stories for the upcoming sprint, estimate effort and define tasks. Done correctly, teams leave planning with clear sprint goals and a clean sprint plan. Feels good, right? Despite all this planning, developers often leave planning without tasks…Read More Should Your Team Claim Tasks in Sprint Planning?
Have you ever actually bitten off more than you can chew? It’s not a pleasant feeling. And neither is an overloaded backlog. Like a juicy steak, a healthy sprint backlog is best when it’s consumed in bite-sized portions, or user stories. (And, if you’ve got a gaggle of oversized stories, your best course of action…Read More Tips for Breaking Down User Stories
Much like modern smartphones, some user stories are just too big for their own good – and the good of your development team. In fact, many teams limit the maximum size for user stories pulled into a sprint. Anything too big gets broken down into smaller pieces or put on hold. Scrum teams have a…Read More The Value of Limiting Maximum Effort on Stories
Effort pointing and story estimation are cornerstones of agile development, yet many teams push back against the necessity of estimating every single story. Some scrum masters feel estimations are time-consuming or inaccurate, and their developers may become discouraged when faced with large epics. That said, taking the time to work together and estimate user story…Read More Are Story Estimates Necessary?
Perhaps you’ll agree that Sprint Planning can be… taxing, to put it mildly. It requires practice and patience. Accurate estimation drives effective planning, and you have a variety of options when choosing an estimation method. The key is finding the one that works best for your team and enables you to build the most accurate…Read More Sprint Estimation Pointing Scales