More Agile Great Debates, Part 4
In the fourth installment of my blog series on “More Agile Great Debates,” I dive into another five topics that people like to argue about.
Who is on an Agile Scrum Team? Well, Scrum defines only three official roles: 1) Product Owner, 2) Scrum Master, and 3) Developers. Keep reading to learn more.
In the fourth installment of my blog series on “More Agile Great Debates,” I dive into another five topics that people like to argue about.
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?
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.
My clients ask: “How do we deal with Production Support issues in Agile when our Scrum Team supports both the product and its development?”