Are You a Whole Team?
This article proposes four “smells” that might indicate that you’re not optimally practicing whole-team approach in your Scrum software development project
This article proposes four “smells” that might indicate that you’re not optimally practicing whole-team approach in your Scrum software development project
In this funny blog post, Maurits Rijk lists the reasons that people will give to explain why Scrum will never work. A “dilbertian” exercise well done and that you shouldn’t take literally. Or maybe yes! ;o)
This article aims to bring to the table a consolidated Scrum Project Dashboard layout that could be easily maintained and updated by the Product Owner with day-to-day and well-known information provided by the team. He will be able to get stakeholder and management attention and support while providing an updated clear picture on the Project’s status.
In this blog post, Dewayne Washington make an interesting between the ScrumMaster role and the referee of a football game.
This is an article about opposition to Scrum. Most of the challenges in Scrum adoption aren’t technical, but social. Because Scrum makes ineffectiveness obvious and control organic, some people will fight tooth and nail to stop the effort.
“If the team is uncertain about how to achieve the sprint goal or if experimentation or prototypes need to be done, then the sprint should be shorter. Uncertainty implies that the work eventually required for the sprint might be significantly different from what was anticipated at the start. If this is the case, it’s better to change direction after two weeks than four.”
In this blog post, Samuli Heljo shares his experience about a Scrum team that transitioned to Kanban. It offers a lot of data about this experience and try to analyze the failures made and to come up with some solutions.
Scrum Expert Copyright © 2009-2024 Martinig & Associates