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 […]
Back in Part 1 of this series, I explained all the problems I saw with this interview question: “The product owner and dev team cannot decide on a sprint goal, even after hours of discussion. They (the team) feel that the tasks for the sprint are too varied to manage to a single sprint goal.
Most projects encounter problems at some point, regardless of the size of the team and the people’s capabilities. For example, in a six-person team, TeamA, Tom resigned to follow his wife to her new job. Dick became quite ill and went out on short-term disability for the next three months. And Harry needed significant time
Meetings. We all have them. Most of us hate them. When I ask why, here are some of the responses I hear: They take too much time away from our “real work.” It’s too hard to find time to meet. Our calendars are too full. We can’t find a place to meet. If we’re back
I thought watermelon status was something “everyone” knew about. But it’s not! Read No More Watermelon Status Reports: How to Use Stories to Explain Project State. That’s a persona-based approach to help other people understand the project’s reality. You also might like Velocity is Not Acceleration to see charts and data I use and recommend.
Several people on social media have denigrated the terms “project manager” and “program manager.” These people claim there is no need for either role in an effective team, especially an agile team because the team can manage its own deliverables. While some agile teams can manage their own deliverables, that’s not the only role for
A colleague unfamiliar with lifecycles or agility asked, “How can we use sprints in this approach?” and pointed to a phase-gate approach with documentation deliverables after each phase. It looked just like the serial lifecycle in the image on the left. (That’s because a finance person drew the lifecycle.) I said, “You can’t use ‘sprints.’
So when does it make sense to customize your agile approach to gain a strategic advantage? Whenever you have a unique problem to solve that’s strategic to your business. Let’s start with a couple of examples. Example 1: Startup/Small Organization with Few Products SmallCo has revenue of about $30Million a year. They offer their product
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,
The original signatories of the Manifesto for Agile Software Development wanted to solve these specific problems: How can we: Bring more adaptability to software development? Stop “plan the work and work the plan” thinking? Release something of value earlier? Especially since teams now had these levers, from the iterative and incremental approaches: Prototype something for