Agile change and transformation
Many teams who are already using Scrum would like to know what benefits they can get by moving to Kanban. Dropping the Sprint timebox can seem quite scary but on the other hand spending less time planning and estimating seems attractive to many developers. How do you know that you haven’t thrown the baby out with the bathwater?
In a slightly provocatively titled “Why I’m done with Scrum” blog post, Jimmy Bogard provides four reasons reasons why he decided to abandon using Scrum to adopt a lean approach to software development.In his first two reasons, he discusses the inefficiencies of the iteration system.
It would be so easy if everyone at our companies just used Scrum or at least Agile. No one would lean on the team for dates and deadlines, and everyone would know that change is a good thing. It’d be one great big happy project management family. But let’s face it: an all-Agile organization isn’t always possible.
There is a tendency to use agile software development approaches and all their practices simply because it is in the book. Why don’t we select the tools based on the context of the task we are trying to complete?
The adoption of Agile approaches has introduced new ways of thinking about Project Management, which impact Project Management Organizations in various ways. This paper divides the range of practices commonly found in Project Management Office (PMO) into Project Management, Program Management and Portfolio Management. It identifies how the introduction of Agile processes such as Scrum impacts the PMO.
The Agile Karlskrona test is a simple self-assesement test that tries to answer the “How agile are you?” question. With 11 questions, this test should help you find where “on the road” from waterfall to agile your software development team is at the moment.
Companies that transition to Agile often adopt the analogy that sprints are just mini waterfall. This article provides five reasons why Scrum sprints are not mini-Waterfall. Each argument is illustrated by a diagram that provides a clear visual evidence of the difference between the Agile approach and a traditional process.
Scrum Expert Copyright © 2009-2023 Martinig & Associates