A senior leader, Jim, emailed me to clarify how to track a project’s progress. He’s a sales guy by training and is now leading a technology-based company. He’s confused. When he asks about progress, he feels as if everyone takes one step forward and two steps back, just as in the Project Kisses of Death […]
In a recent conversation, I realized that very smart and experienced project managers do not always know the difference between activity-based plans and deliverable-based plans. While activities might result in an interim or internal deliverable, activities do not result in a user-focused deliverable. The team might make some progress, but not progress users can see.
I’m working on finishing a talk based on a recent Pragmatic Manager newsletter: Three Tips to Focus to Deliver Better Products Faster. I wrote that newsletter because I’d given several recent talks where the audience told me their “agile” teams could not collaborate. Those “teams” were component teams and they were not near each other.
I was on the Agile Uprising podcast this past Sunday, discussing my most recent book. See (and hear!): Project Lifecycles with Johanna Rothman. I had a great time discussing the issues with Jay and Claudia. Some of what we discussed: That managers want agility but do not care about any agile methods or frameworks. While we
I had a terrific time at the Hands On Agile Community meetup. Stefan Wolpers, the host, posted the video. Also, see the slides on my speakerdeck. Thank you, Stefan, and the entire Hands On Agile community.
Luke Pivac, a colleague from New Zealand, interviewed me last week. Here’s the video: We discussed several topics: My recent Unemployed Agilists posts. (That link just goes to the first post) My most recent book: Project Lifecycles: How to Reduce Risks, Release Successful Products, and Increase Agility. Luke very kindly included (automatically generated) subtitles, which
I have never found Gantt charts to be useful. When I say that to my clients, some of them tell me they do find use in Gantt charts. Specifically, the people who like Gantt charts say they can predict where the project is headed. In addition, they can see the various interdependencies across the work.
Susan, an experienced senior leader, wondered what to do. Her company’s market was on a roller coaster. Increased revenue meant a lot more customers, who clamored for more features. So, the product leaders pressured the teams to deliver faster. But she’d been in a roller coaster situation before. After two years of stupendous growth, revenue leveled off in just one
In Effective Agility Requires Cultural Changes: Part 1, I said that real agile approaches require cultural change to focus on flow efficiency, where we watch the flow of the work, not the people doing tasks. Too few organizations can do that. Then I offered three suggestions for teams in any lifecycle in Effective Agility: Three
For years, managers have been trying to find ways to make software product development faster and easier. As an industry, we’ve tried tons of things. Here are just the one I’ve experienced in the 70s, 80s, 90s: Structured Analysis and Design. (That was the precursor to Big Design Up Front.) The SEI’s Capability Maturity Model