You’ve got interdependencies across the organization for a given project or program to release a product. You can see demos. That’s not the problem. You need enough insight or prediction to start the marketing campaign or to create training videos or product documentation. You need some kind of milestone criteria so you know you can complete […]
Program sponsors and the teams themselves want to know where they are in the program. What’s started? What’s not? How much more remains? It’s tempting to measure “everything.” That creates another problem: You might spend too much time attempting to gather data that doesn’t provide enough information. You might even miss seeing the real progress
Ryan Ripley and I spoke on his Agile for Humans Podcast, Agile Program Management with Johanna Rothman. We had a blast. We spoke all about Agile and Lean Program Management: Scaling Collaboration Across the Organization, estimation, value, and much more. I hope you listen.
I’m a new contributor to the TechBeacon site. I have an article up, called Small-world networks: a lightweight alternative to SAFe for scaling agile. Yes, it’s based on Agile and Lean Program Management: Scaling Collaboration Across the Organization. Hope you enjoy the article.
I sent my newsletter, Scaling Agile and Lean to Programs to my subscribers yesterday. (Are you one of them? No? You should be!) If you are trying to use agile for several projects that together deliver value (a program), you might be wondering what the “right” approach is. You’ve heard of frameworks. Some of them
I’m working on the program management book, specifically on the release planning chapter. One of the problems I see in programs is that the organization/senior management/product manager wants a “commitment” for an entire quarter. Since they think in quarter-long roadmaps, that’s not unreasonable—from their perspective. There is a problem with commitments and the need for
The lovely folks at Thoughtworks interviewed me for a blog post, Embracing the Zen of Program Management. I hope you like the information there. If you want to know about agile and lean program management, see Agile and Lean Program Management: Scaling Collaboration Across the Organization. In beta now.
If you saw Large Program? Release More Often, you might have noted that I said, You want to release all the time inside your building. You need the feedback, to watch the product grow. Some of my clients have said, “But my customers don’t want the software that often.” That might be true. You may
I’m working on the release planning chapter for Agile and Lean Program Management: Collaborating Across the Organization. There are many ways to plan releases. But the key? Release often. How often? I suggest once a month. Yes, have a real, honest-to-goodness release once a month. I bet that for some of you, this is counter-intuitive.
I published another Pragmatic Manager this week, Time for a Decision. It’s about program management decisions, and collaborating across the organization. Do you receive my Pragmatic Manager emails? If you think you are on my list, but are not receiving my emails, let me know. Some of you long-time subscribers are not receiving my emails