Tag Archives: project team

Design Your Agile Project, Part 4

If you are thinking of agile as part of a program, each team has to have its own approach to agile. Why? Because each team has its own risks and problems. You don’t need to standardize agile for anyone. If … Continue reading

Posted in agile | Tagged , , , , , , | Leave a comment

Design Your Agile Project, Part 3

What do you do  for geographically distributed teams, if you want to move to agile? First question: does the team want to move to agile? Or, does the management want to move to agile? I am serious. I might take … Continue reading

Posted in agile | Tagged , , , , , , | 1 Comment

Design Your Agile Project, Part 2

The point of using agile is to get finish something valuable-to-the-business quickly, to get feedback. Why? For several reasons, but the first one is so you can change the project’s priorities. The second is so you can change the project … Continue reading

Posted in agile | Tagged , , , , , | 3 Comments

Design Your Agile Project, Part 1

The more I see teams transition to agile, the more I am convinced that each team is unique. Each project is unique. Each organizational context is unique. Why would you take an off-the-shelf solution that does not fit your context? … Continue reading

Posted in agile | Tagged , , , , , | 3 Comments

Cost of Delay: Why You Should Care, Part 6

I’ve outlined five potential costs of delay in the previous five posts: The delay from not releasing on time, part 1 The delay from multitasking,part 2 The delay from indecision, part 3 The delay from technical debt, part 4 The … Continue reading

Posted in portfolio management | Tagged , , , , , , , , | 1 Comment

Cost of Delay Due to Other Teams’ Delay, Part 5

Imagine you have a large program, where you have several teams contributing to the success of one business deliverable. You are all trying to achieve a specific date for release. One team is having trouble. Maybe this is their first … Continue reading

Posted in portfolio management | Tagged , , , , , , , , , | 3 Comments

Fixing—or Not—Healthcare Dot Gov

Did you see Dwayne Phillips’ post today, Adding People to a Late Project? Dwayne says: Adding people to a late project only makes it later. We have known this for decades. Especially in the article he refers to, it seems … Continue reading

Posted in project management | Tagged , , , , , , , | 9 Comments

What is the Future of Work?

I just read Scott Berkun’s The Year Without Pants: WordPress.com and the Future of Work. For me, it was a mixed read. Yes, you can make a totally distributed team work. What you need to do: Make all of the … Continue reading

Posted in books | Tagged , , , , , , , , | 7 Comments

Hours, Velocity, Silo’d Teams, & Gantts

I’ve been having some email conversations with some project and program managers turned Scrum Masters. In general here’s how things have proceeded: Their organizations decided agile was a great idea Their organizations decided Scrum was a great idea to implement … Continue reading

Posted in project management | Tagged , , | 9 Comments

Reduce Friction

On the bike at the gym this morning, I thought about increasing my level. When I exercise, more friction is good. But when you develop or use products, more friction is bad. Brian Marick talks about  this when he speaks … Continue reading

Posted in program management | Tagged , , , , | 2 Comments

Last updated by at .