What is the ideal Sprint length in Scrum?
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?
When it comes to Agile options, the Scrum Framework is far and away the most popular. Check out this extensive collection of blogs about Scrum.
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?”
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!