Articles on Scrum and Agile Project Management
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.
Chances are, you’ve found yourself in a situation in which some members of your team don’t feel comfortable sharing what they truly feel, either with each other or with leadership. This type of discomfort can be caused by any number of factors: fear that the supervisor or leader will penalize people who speak up; concern over getting humiliated in front of others; and other unfortunate causes.
There are many discussions about what Scrum teams should include in their Definition of Done (DoD). However, security is rarely mentioned during these talks, even if more and more hacking incidents are revealed to the public. This article outlines some major security best practices for Agile teams.
Copyright © 2009-2022 Martinig & Associates