Articles on Scrum and Agile Project Management
ScrumMasters are accountable for increasing visibility and tackling organizational obstacles, while creating an Agile environment in which team members thrive. Quiet firing may represent the mother of all organizational impediments.
User stories and story points are often used as a technique to define requirements and estimate work by Scrum teams. This article explains why it is not a good practice to use story points as an estimation tool with planning poker.
Data platforms are becoming more necessary for software development than ever before. However, with the rise of new technologies, the way developers interact with these data has changed as well.
If we have always to remember that it is more important to be Agile than to do Agile, there are still many organizations practicing Scrum in a “cargo cult” mode. In this article, Mark Haynes describes, with a facetious bias, some of the common anti-patterns of Scrum Masters.
Every year brings new challenges and seasonal peaks such as Cyber Monday and Black Friday. During these events, businesses experience an unusual amount of pressure followed by a faster pace of work, a higher volume of transactions, etc. Companies are most vulnerable during seasonal peaks because of the many challenges they must conquer.
With its iterative approach, the Scrum framework enables teams to minimize risk and manage risks confidently. Risk can creep into various elements when managing a project and prevent you from delivering a valuable project. But it takes much more than risk awareness to head off these risks.
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.
Scrum Expert Copyright © 2009-2023 Martinig & Associates