Glen Alleman seems to have nailed it, with Alert – Was Poor PM the Root Cause of ACA Difficulties? Among the many problems: No overall program manager No way for stakeholders to know what Done looks like (no release criteria) No replanning I’m a huge fan of rolling wave planning. (Read Starting with Rolling Wave […]
Imagine you are transitioning to agile. You are a program manager, with a couple of agile projects, and a couple of traditional projects. How do you manage the program? Here’s what a program team looks like. For the sake of argument, assume that Sally is an agile program manager, because we can tell she’s working
Someone asked me again about self-assessments for their agile transition. That got me thinking about this problem of transitioning to agile. I don’t believe agile is for everyone in every circumstance. Some people claim agile has “crossed the chasm.” Certainly, many people are aware of agile. Many people understand that a cross-functional team works in
Imagine this scenario: you want to transition to agile, and you have a geographically dispersed team with people all over the world. You have two developers in the UK and two in Boston, two testers in Portland, Oregon, a product manager in Brazil, and you, the project manager are in Sweden. And, you are pretty
I hope that by now you see that you have any number of choices for your lifecycle if you are geographically distributed team and you are transitioning to agile. I do recommend a servant leader agile project manager, for coordination and risk management. With people all over the world, it’s difficult to coordinate the project,
Example 3: Using a Project Manager with Iterations and Kanban and Silo’d Teams Here, the developers were in Cambridge, MA, the product owners were in San Francisco, the testers were in Bangalore, and the project manager was always flying somewhere, because the project manager was shared among several projects. The developers knew about timeboxed iterations,
Example 2: Using a Project Manager with Kanban, Silo’d Teams This is a product development organization with developers in Italy, testers in India, more developers in New York, product owners and project managers in California. This organization first tried iterations, but the team could never get to done. The problem was that the stories were
I’ve been working with geographically distributed and dispersed teams for the past couple of years. Some of them on quite large programs, some of them reasonably small. What they all have in common is that they all want to transition to agile. Most of them start this way: someone takes a Scrum class, gets all
To continue our story from part 1 and part 2… The teams have determined their individual impediments to Continuous Integration. You, as the technical program manager, and the technical program team can take those impediments, with input from the teams can see the impediments to program-wide continuous integration. You have used a similar problem-solving approach,
Let’s set the context (which I did not do in my most recent post–sorry). Define a Program A program is composed of several feature teams, which may well be working on several projects or different feature sets. I assume they are. The goal of a program supersedes the goal of any of the projects, and