More Great Agile Debates, Part 1
My previous “Great Agile Debates” have proven extremely popular, so I thought I would add to this body of knowledge with a new blog series.
My previous “Great Agile Debates” have proven extremely popular, so I thought I would add to this body of knowledge with a new blog series.
There, I said it. I know it’s controversial, but it’s true: there isn’t a Project Manager role in Scrum or Agile. That is, while there is no Project Manager in Scrum, many project management activities still need to happen. They just occur at different times and in different formats. PMs have struggled to find their …
Nothing in The Scrum Guide says you can’t pick a specific purpose for a Sprint, but is it a good practice? Are there special types of Sprints?
Scrum Teams without formal training are apt to make tons of mistakes because they don’t have experience or guidance. Here’s what can happen.
One critical decision when starting a new Scrum Team is the length of the Sprints. The Scrum Guide says “one month or less.” So, what’s ideal?
In agile (Scrum), teams are self-organized and self-managed, largely replacing the need for functional managers. So what happens to them?
Not delivering a “done” increment at the end of a Sprint can cause many negative consequences. It’s a bad habit and won’t make anyone happy.
Technical Debt is often neglected, but it’s like building a house of cards – eventually, something will give, and it will all collapse.
The right way to write User Stories is from a user’s perspective, taking a thin vertical slice through all the horizontal system layers.
My clients ask: “How do we deal with Production Support issues in Agile when our Scrum Team supports both the product and its development?”