I discussed the origins of the agile approaches in Part 5. In this post, I’ll discuss how you can create an agile approach that fits your context. Why should you create your own agile approach? Because your context is unique to you, your team, project, product, and culture. You deserve an agile approach that helps […]
Which levers does your team need to manage risk in your project? Do you need to cancel the project if you can’t finish a phase? You might not have the time. You might not have the ability to do this project. That’s the point of Serial lifecycles in Part 1. Maybe you need feedback from
So far, we’ve discussed the lever of canceling a project at any time with the serial lifecycles in Part 1. That’s assuming you replan and/or cancel. We added another lever of looking for more feedback with iterating over the requirements in the iterative lifecycles in Part 2. Teams have another lever. They can release increments
Back in Part 1, I wrote about how stage-gate approaches were as agile as we could use at the time. We had one delivery, so our agility was about canceling the project if we couldn’t finish it. However, some smart people also realized that we had another lever, aside from estimation, to replan the project.
Are you trying to make an agile framework or approach work? Maybe you have technical or schedule risk. Or, maybe you’ve received a mandate to “go agile.” Maybe you’d like to experiment with better ways of working. Or, maybe you’re trying to fit an agile framework into your current processes—and you’ve got a mess. You’re
Several of my clients want to use some sort of maturity assessment for their agile transformations. Often, the maturity levels demand adherence to specific practices or processes. Some of those practices and processes work for my clients now. (I’m not so sure about others.) As my clients evolve, will what they do now continue to
Three Ideas to Boost Your Productivity Several Pragmatic Manager subscribers have asked me about how to build and maintain their productivity. They say they have these problems: The longer they work apart from other people, the less they have the “peer pressure” of a collaborative schedule. They find it hard to maintain focus for a long time.
I’ve spoken professionally at conferences for 25 years. I enjoy it. And, several people—all men, so far—have suggested I should “make room” for other voices. To me, that’s a solution in search of a problem. I ask them what problems they want to solve. They want speakers who are: More diverse in gender More diverse
Your team says they use Scrum in two-week iterations. And, in order to “finish” everything inside the timebox, you don’t do any of these things: Refactor to simplify the code or the tests. Create automated tests. Use formal acceptance criteria on a story or for the iteration or the project. That means you have work
Several weeks ago, I posted my innovation principles, based on Modern Management Made Easy, book 3. I developed them because I was discovering the user journey through the book. I needed a way to link the ideas together. Of course, I also created principles for managing yourself (Book 1) and for leading and serving others