3 ms·

I find help with sprint planning something every engineer should do. Sprints are owned by the team not the product owner

• mosselman 8y ago
  People should do what lies within their realm of capabilities. I know enough people who are fine programmers but who lack the overview or sense of connectedness between certain task or the ability to think about the business value of certain tasks in order to make decisions when things start to take too long or become too complex. Those people should not take care of handling the sprint when the person who normally does that is away. So no, not every engineer should take care of the team's planning.
  • UK-Al05 8y ago
    Well in my team sprint planning is a team job. Everybody gets together and plans the next stories. Usually different people have knowledge/interests on different stories, so nearly everyone gets some input. Heck in the scrum guide this is the way it's meant to be. If your engineers can't factor in business value, or work dependencies its usually because people are hoarding knowledge so they dont have the ability to factor that in.
    • mosselman 8y ago
      I didn't say the team as a whole wouldn't be able to contribute. I was saying that not all people are able to take over day to day planning individually. "its usually because people are hoarding knowledge so they dont have the ability to factor that in." That is like saying that everybody who isn't smart, must be good with their hands. Some people are just not good at certain things, no matter how much they are enabled to do those things. Which is completely fine.