Many new-to-agile teams use some form of iteration-based agile approach. Often, in the form of Scrum. Back in Time You Spend in Agile Meetings (near the bottom of the post), I enumerated all the possible meetings. I suggested the team review its WIP limits and think about limiting the WIP for the entire team. When the […]
Whenever I teach agile approaches, I discuss the possible meetings a team might choose. Some people turn to me in dismay. They start adding up all the meeting time and say, “That’s a lot of meetings.” Could be. Especially if you use iterations. You might have these meetings: A retrospective once every two weeks. A
Do you struggle with your agile approach? Sometimes, iterations don’t work for teams. Sometimes, flow doesn’t work. Sometimes, you need both. To celebrate the release of Create Your Successful Agile Project: Collaborate, Measure, Estimate, Deliver, I am writing a series of articles on Infoq. The first article, Customize Your Agile Approach: Select Your Agile Approach That Fits
If you’re thinking about agile or trying to use it, you probably started with iterations in some form. You tried (and might be still trying) to estimate what you can fit into an iteration. That’s called “pushing” work, where you commit to some number of items of work in advance. And, if you have to
Some program managers whose organizations are transitioning to agile are not always clear on which program team they are managing. Sometimes, that’s because the organization doesn’t always realize they need more than one program team. If you are coordinating and collaborating across the entire organization, you are part of the core program team. If you