Dividing scrum user stories into dummy tasks is evil

One of the keypoints of the scrum sprint planning meeting is the division of the user stories into tasks

  • it leaves less questions unclear to anyone, by dividing you find out more about the task
  • it helps provide better estimations
  • it gives all the team the same understanding of the user story scope, affecting at the sprint scope
  • it allows a better parallel work to happen, particularly on highly vertically specialized teams
  • team does it, team adapts it to the way to work (TDD, design mockups…)
  • the stories come up with their own roadmap which also serves as feedback for the PO
  • … I could add more stuff here

At the same time sprint planning meetings are considered a nightmare by some teams (quite hard yep). Earlier than later someone comes up with some sort of copy & paste candidate of a generic list of tasks as a solution to make the meeting lighter, for example

Read more →


Scrum roles and users

Last week I was reading some material on scrum, particularly on agile requirements acquisition for a post I plan to publish soon. I was reviewing the User Stories Applied For Agile Software Development book by Mike Cohn, definitively a recommended reading. 183072549

I like the Capt. Obvious facts about software development and how often we need someone to constantly remind our teams about those allegedly obvious statements. This is precisely the case, do you ever forget to target your efforts to what the user demands? I am sure you do, I also do

Writing user stories is the way to formalize requirements in some agile methodologies as scrum, the well-known formula As a role, I want goal/desire so that benefit. This definition itself forces us to think in the user roles and pushes us to go for a genuinely user-driven development

Read more →