I have a new book: Project Lifecycles: How to Reduce Risks, Release Successful Products, and Increase Agility. I wrote it because I’m concerned about what I see in too many supposedly agile teams: Crazy-long backlogs and roadmaps. Those create a serial lifecycle approach with too little experimentation. Worse, sometimes the team doesn’t demo or deliver. […]
Ted Williams said, “If you don’t think too good, don’t think too much.” I’ve got a bad head cold, so I’m not thinking too “good” at all. Here are three not-so-intuitive tips I use all the time, and that you might have missed: Move from “How much” to “How little” thinking. Finish something clean, every
Do you ever struggle with knowing if you should split stories? Or wondering if you have a valuable minimum? Jeffrey Frederick and Squirrel offered a signal for a too-small minimum in their podcast, MVP Cubed. That signal was when people became bored with the work. Let me add some additional tests: When the team can’t
Are you a manager accustomed to Management by Walking Around and Listening (MBWAL)? You can use MBWAL with collocated teams. MBWAL doesn’t work for distributed or dispersed teams. Remember, working remote is Not Business as Usual. (And won’t be for a while.) And, you might still have this question: “If no one’s in the office,
You’ve got an impossible project. You have no flexibility. The project is a fixed-price, fixed-scope, fixed-date project. And, you have a specific team to do the work. (There are other impossible projects. Such as when you have a collection of people who multitask among several projects.) Can an agile approach save these projects? No. An agile
I’ve led various project kickoffs over the years. Back in the closer-to-waterfall days, we had to introduce ourselves to each other. We could then move to the project purpose and release criteria. Now that agile teams stay together, we can change the kickoff to more project-specific work. I wrote an article several years ago, Keys
Dan, a product owner felt as if he was stuck between the proverbial rock and the hard place. His managers wanted “everything” in the next release.He knew the team couldn’t possibly deliver all of it. He hoped to get most of the features. He met with Polly, the agile project manager, and asked how much
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,