As I work with more clients on their programs, I see that what might work for a product owner for a team does not work for a program. In a program, if the product owner is shortsighted, does not take advantage of agile/lean for updates, and does not have small features, the program loses momentum. […]
Andy Hunt, the Pragmatic Bookshelf publisher, just sent me an email telling me that Manage Your Project Portfolio is featured in La República, Columbia’s “first and most important business newspaper.” That’s because getabstract liked it! Okay, my book is below the fold. It’s in smaller print. And, I have to say, I’m still pretty excited. If
I’m writing part of the program management book, talking about how you need to keep everything small to maintain momentum. Sometimes, to keep your work small, teams move from iterations to flow. Here are times when you might consider moving from iteration to flow: The Product Owner wants to change the order of features in
I did a little bit of work for the ProdBOK (the Product Management Body of Knowledge) earlier in 2012. It was a little bit of work. I had an opportunity to meet Greg Geracie, along with some other very nice people. When the BOK comes out, at some point later this year, I’ll get to
Chris asked in his comment, how about using the word ‘abandoned’ for projects that are “finished”? I just don’t think of completed projects as abandoned. Let’s separate the product from the project. Projects complete. Products may never be done, but projects do finish, sometimes whether we want them to or not. I was working as