MPD

agile, MPD

Architecture and Programs: Incremental Progress Not Big Bang

I’ve been working on agile program management and a colleague emailed me about his program. He’s having trouble seeing how to do agile on a large program. The customer wants to see a working system before they add the features, so the customer thinks the program need to provide “all” the architecture, with some hard-coded

agile, MPD

The Value of a Demo

Some teams don’t do demos at the end of their iterations. Many of the teams who don’t do demos also have trouble finishing all the stories they committed to at the beginning of the iteration. They continue, iteration to iteration, not always finishing, not getting to releaseable at the end of the iteration. And, sometimes,

MPD, portfolio management

Catching Up With my Email Newsletter

I have been delinquent for those of you who subscribe to my email newsletter. I have not published one since April. On the other hand, I just posted Park Projects You Can’t Staff, For Now. The next newsletter is scheduled for Thursday morning. In case you’re wondering, I post the most immediate past newsletter when

agile, MPD

What Should Done Mean, Coda

Last week at Agile 2010, Joshua Kerievsky and I facilitated an Open Jam session (open space) about what done means. We discussed a variety of points. I believe we eventually agreed that context matters. It’s important to know what your product success criteria are. If you don’t use a project charter where you define success

agile, MPD

What Should Done Mean?

Josh Kerievsky has an intriguing post about . The idea is that a story is not done until: A story isn’t done until it is being used by real users in production and has been validated to be a useful part of a product. I have trouble with this definition: The development team is dependent

agile, MPD

Develop by Feature, Develop by Component, or Some Combination?

I’ve been working with Rebecca Wirfs-Brock on an agile architecture workshop. I’m working with Rebecca because she has such a depth of experience in architecture, as well as design. She’s working with me because of my project and program management experience. We’re pretty psyched. We’re working through the issues of large programs and architecture, and,

MPD, program management

Defining Program Management and How Agile Helps

It’s a good thing I said my post about musings was just that–musings! I didn’t bring all of you along. Sorry about that. Let me be more clear. A program is a collection of projects, where the value is in the overall deliverable. Yes, each project may have a deliverable that’s valuable, but the value

agile, MPD

Musings About Agile Program Management

I’ve been working with organizations who want to move their programs to agile. They’ve been successful with small projects. But now, they want to make agile work with large programs, programs that involve hardware or firmware, programs with many pieces of interdependent software features, programs of 50 to 300 (or more!) people. Now, you might

Scroll to Top