More Great Agile Debates, Part 2
In the second part of my blog series on “Agile’s Great Debates,” learn about five more agile topics that people argue about and disagree on.
The Agile Product Owner role on a Scrum Team is THE key to success. Check out this blog collection covering the skills and traits necessary to succeed.
In the second part of my blog series on “Agile’s Great Debates,” learn about five more agile topics that people argue about and disagree on.
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.
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?
In agile (Scrum), teams are self-organized and self-managed, largely replacing the need for functional managers. So what happens to them?
My clients ask: “How do we deal with Production Support issues in Agile when our Scrum Team supports both the product and its development?”
Ideally, your Scrum Team includes full-time people with the right cross-functional skills; but if you have part-timers, you’ll have problems.
Without a caring, competent Product Owner, most products will fail to come to fruition, earn and retain market share, and evolve.
There should be no “special” Sprints in Scrum. The goal of every iteration is to create a working increment that is potentially releasable.
While Scrum is a flexible framework, it isn’t Scrum unless you have all the components, so NO, it’s not okay to skip some Scrum events!
So, you have a Scrum Team. But does your team have all the necessary cross-functional skills to get to a “done” increment each Sprint?