Articles on Scrum and Agile Project Management
If estimating is a core activity of traditional project management, Zuzana “Zuzi” Šochová explains to us in this article that it is not used by advanced Agile and Scrum teams. Instead, the focus should be on being more reactive to changes and responsive to feedback. We are realizing that Agile is not about plans, but planning as a continuous activity.
Has improving your Scrum team been like taking a walk to Mordor? “Not with ten thousand men could you do this. It is folly.” Tolkien, Lord of the Rings. The path seems wrought with peril. Why not just implement the ceremonies first, then focus on the intent later. Stopping there incurs the risk of slipping back into bad habits.
Conceptually Scrum is simple, so why is achieving a mature agile team such a daunting experience? Maybe because it’s not just a matter of implementing the ceremonies. Scrum teams need to embrace continuous improvements through an incremental and iterative process.
Today, many scrum teams and Agile organizations have incorporated some forms of remote work. This article presents the challenges of managing a distributed scrum team and provides actionable tips for success.
Creating effective Agile teams is not easy. This article explores three models that can inspire you in the Scrum team creation process: the Lencioni Model, the 7T Model and the Tuckman’s Team Development Model.
Uncertainty in the Product Backlog is a big risk for the schedule of a Scrum project. The problem is that the full scope of the release in Agile software development can be quite hard to estimate because the requirements are not well-know early on. Confounding this problem is that frequently the release date is a hard deadline.
Continuous improvement is one of the main concept of Agile and retrospectives is a technique used by Scrum team to achieve it. This article shares five situations that Scrum teams should avoid in their retrospectives.
Scrum Expert Copyright © 2009-2023 Martinig & Associates