In my first post, Why We Have Too Much Pressure and Planning & Too Little Delivery, I discussed the issue of too much planning and how that reduced delivery. In this post, I’ll address how to increase delivery by planning less. (I have a draft post of the system view of how too much planning reduces […]
I work with many teams that have extensive product backlogs. Each iteration has a backlog of more items than the team can typically finish. Worse, some organizations want many quarters’ worth of backlogs, as in the image in this post. There are several problems with long and extensive backlogs: They tend to be wishlists of
Several of my clients want to plan the product roadmap and then “work to the plan.” They think the roadmap is the long-term goal. But roadmaps aren’t goals. Instead, they are tactics for achieving a long-term goal. That means we need long-term goals based on both the corporate strategy and each product’s strategy. Those are two
So much of the planning I see in organizations is way overdone. Senior leaders still try to plan the project portfolio for a year. Product leaders are supposed to “commit” to year-long or longer roadmaps. And so many teams know “exactly” what they’re supposed to do for weeks, if not months at a time. We
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.
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
Regardless of whether you work inside an organization or you work for yourself, the start of the new year allows all of us to reset and restart. That means too many of us think we need to “plan” for an entire year. Before you consider an entire year, reflect on last year: How much of
Sherry, a middle manager in a relatively small organization, said, “We can’t plan for an entire quarter at a time. Our managers need to change what they want more often than that. But I’d like to plan for a quarter at a time and I really don’t want to ask people to multitask. What do
We use product roadmaps to see where we want to go and the options we might take to get there. Yet, so many of our roadmaps offer only a single and certain destination. If we don’t see options, we reduce our innovation decision points—and possibly disappoint our customers. Worse, we create products that don’t fulfill
What risks does your project have? Do you need feedback loops so you can: Cancel the project at any time (to manage schedule and cost risks. Assess technical risks so you can rework the architecture or design to manage feature set risks. Manage what you release to customers so you can manage defect, feature set,