The Agile Atlas is a web site supported by the Scrum Alliance which is an information resource for Scrum and Agile practitioners. The purpose of this site is to provide an “encyclopedia” of information about Agile and related methods.
Sprint lengths should be chosen in relation to project duration; however, they should never be longer than four weeks. Consider a three-month project. If it has four-week sprints, the stakeholders will only get to participate in two demos before the project is released. This is not enough feedback to mitigate the risks. Shorter sprint lengths are a necessity.
Collaboration Games from the Growing Agile Toolbox is a free e-book written by Karen Greaves and Samantha Laing that proposes ten games to build collaboration in Agile teams.
Absent ScrumMaster, poorly defined requirements, inexperienced team, absent product owner, impossible goals. Sometimes things can go wrong even in projects that use an Agile approach like Scrum. The main issues are absent product owner or ScrumMaster, an inexperienced team, poorly defined requirements or impossible goals. In this article, Avelino Ferreira Gomes Filho shares some of his experience as a replacing ScrumMaster in troublesome Scrum projects.
In 10 years since the signing of the Agile Manifesto we’ve seen some notable successes, half-way efforts, fragile, scrum-but and just plain #FAIL. We tried to adopt agile methods to solve all types of problems, and many of those problems persist. What are the most common failure modes? How can organizations avoid falling into those failing patterns?
Running Agile software development projects using Scrum is not always an easy task. Sometimes you need to take a step back and look at the Agile best practices with a dose of humour.
Whether you follow a Agile framework like Scrum with its planning poker or a traditional project management approach, the estimation activity is always difficult to perform productively and consistently on the long term.
Scrum Expert Copyright © 2009-2024 Martinig & Associates