When I started to work in 1977, we didn’t have testers. I wrote tests for my code, code reviewed with other people, and—every so often—tested other developers’ code. We missed lots of errors, both in logic and functionality. That led to a ton of product and project risks. (Yes, plenty of late and unplanned feedback […]
Susan, a senior leader, wants faster throughput. She can see people working hard. Yet, all the projects seem to take much longer than anyone expects. They’re doing a lot of the right things. No team is multitasking—the teams work on one project at a time. And the teams manage their inside-the-team WIP (Work in Progress).
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
Jim, a relatively new manager said, “I don’t have nearly enough time. I’m in meetings all the time. And I still need to do some of my previous technical work. I feel stretched from one end of the work day to the other.” We spoke for a few minutes. I asked him to eyeball the
Most managers I meet want to do a good job. They want to provide the vision for the people doing the work. They want to provide coaching if people need it. They want to know that people can deliver the outcomes the organization needs and the managers want. As their organizations move to agile approaches,
My most recent article on projectmanagement.com is 3 Questions to Ask Before Estimating an Agile Program. In both Create Your Successful Agile Project and Agile and Lean Program Management, I talk about the reality of estimates in most settings. The question is what kind of an estimate does your project or program need? I’m not opposed to
One of the things I like about agile is the fact that it encourages me to learn. I wish I were perfect, able to learn things as soon as I try them. However, I am all too human. It takes me time to learn. I just upgraded one of my text-processing programs, and now about
To summarize: your agile transformation is stuck. You’ve thought about your why, as in Becoming an Agile Leader, Part 1: Define Your Why. You’ve started to measure possibilities. You have an idea of who you might talk with as in Becoming an Agile Leader, Part 2: Who to Approach. You’ve considered who you need as allies and how to enlist them
To summarize: your agile transformation is stuck. You’ve thought about your why, as in Becoming an Agile Leader, Part 1: Define Your Why. You’ve started to measure possibilities. You have an idea of who you might talk with as in Becoming an Agile Leader, Part 2: Who to Approach. You’ve considered who you need as allies and how to enlist them
To summarize: your agile transformation is stuck. You’ve thought about your why, as in Becoming an Agile Leader, Part 1: Define Your Why. You’ve started to measure possibilities. You have an idea of who you might talk with as in Becoming an Agile Leader, Part 2: Who to Approach. Now, how do you create allies so you can unwedge