Create Successful Schedules: Three Tips to Rolling Wave Planning Do you ever feel under pressure to finish “all” of whatever this project is? And, the project might unfold in various ways, so you can’t quite plan “all” of it? Enter rolling-wave planning. You don’t have to know everything. You only have to know where you […]
I’m working on my roadmapping talk for Agile 2018. I finally had the transforming idea about how to position the talk: Roadmapping and product planning are about feedback loops. The shorter the feedback loop, the faster and more often we can learn. That feedback loop works in at least these ways: The faster we learn,
I had the chance to talk with Andy Kaufman on his podcast, Accelerating Your Agile Journey, PPP 2017. We’ve had the chance to speak informally and more formally on his podcast. This time, we had a wide-ranging discussion. We spoke about many of the ideas in Create Your Successful Agile Project: Learning early (instead of failing
Do estimates make you slightly crazed? Maybe you want to roll your eyes at the organization’s confusion between your estimate (guess) and a commitment. You’re not alone. I wrote an article about estimation, How to give IT project estimates—and when not to estimate at all. If you’ve ever struggled with estimating work, give it a read.
I explained about objectives and the differences between MBOs and OKRs in Part 1. I’m tackling the issues of “accountability” in this part. Examine Accountability What does accountability mean to you? I’m serious about that question. For many people—managers included—people are accountable when we can blame them for not doing something. If you don’t achieve
I have personal and professional goals. Sometimes, I state them as objectives: complete this book, learn that thing. Those are personal objectives. My personal objectives look like MBOs, Management By Objectives. These personal objectives contribute to my company, but they are not a corporate objective. Some of my goals are corporate objectives: release that book, build
Many new-to-agile teams use some form of iteration-based agile approach. Often, in the form of Scrum. Back in Time You Spend in Agile Meetings (near the bottom of the post), I enumerated all the possible meetings. I suggested the team review its WIP limits and think about limiting the WIP for the entire team. When the
When I teach any sort of product/project/portfolio management, I ask, “Who believes multitasking works?” Always, at least several managers raise their hands. They believe multitasking works because they multitask all the time. Why? Because the managers have short work-time and long decision-wait time. If you are a manager, your time for any given decision looks
Whenever I teach agile approaches, I discuss the possible meetings a team might choose. Some people turn to me in dismay. They start adding up all the meeting time and say, “That’s a lot of meetings.” Could be. Especially if you use iterations. You might have these meetings: A retrospective once every two weeks. A
Three Secrets to Creating Your Focus Time I don’t like multitasking at all. And, I have many projects in progress. How is it possible to jump from one project to another—and not forget where I am? My secret is focus time—small periods of time where I focus-and-finish work. Secret 1: Write down the work you