There was a time when software developers worked with consultants that will do things for their company or teach some technical knowledge. Agile approaches have brought forward another type of people: coaches.
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.
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.
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.
This article presents the retrospective & health radar tool, Trune. There are many Scrum retrospective tools out there, and the number is growing by the day. So why do companies like Intuit, IBM, Airbnb, Volvo, and Starbucks choose Trune as their retrospective tool for their Agile teams?
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.
There are still many open source kanban tools available, contrary to open source projects for Scrum tools that have mostly ended being transformed in a limited offer that supports a main commercial product. The simplicity of the Kanban approach has allowed open source software developers to create and maintain Kanban tools based on various platforms.