Let’s be honest. Exec dashboards always look fine — beautiful works of fiction. Lines go up. Colors stay green. Progress looks unstoppable, and everyone’s hitting their “targets” — at least on slides. Meanwhile, teams are drowning in dependencies, decisions crawl through molasses, and nobody’s entirely sure if all this activity is producing actual outcomes. It’s […]
Stop Abusing Agile
Bob asked, “Is the project on schedule?” Will said, “We do Agile. We don’t follow a schedule.”Bob was left wondering how he might report this to the governance teams. Cathy asked, “What scope will be delivered in the next 2 months?” Joe answered, “We are agile. We do not estimate all work upfront. All I […]
You’ve got more capacity than you think
Managing a business today means leveraging your existing capability to maximize throughput. Why am I focusing on throughput? If you think about your organizational value stream, you only make money (or realize revenue) when you deliver a product or a service to your customer. Having a large volume of work within your organizational pipe while not delivering anything means your investments are tied up with work-in-progress inventory. The more work-in-progress inventory you have the more investments are needed. How are you going to fund this investment? The faster your deliver, the faster you realize revenue. Hence, the focus on throughput.
Predict project failure using cumulative flow diagrams
One of the biggest challenges I face as a project manager is the ability to predict the project or program’s future. What impact would the change request have on the project? Are we going fast enough to meet the program deadlines? Are the team’s estimates good enough? Assuming the team will meet most of its estimates, what can we do to go faster? Why do I need to wait for 5 months before I can touch and feel the product? These are just a few of the questions that needed answering throughout the project lifecycle. Critical Chain changed all that. I was, at last, able to predict project failure long before projects got off the rails
Kanban saves the day
I was brought in to deliver a project on-time with less than 2 months remaining. While the project scope and deliverables were clear, getting to the solution was not.
R&D was required to get some of the features delivered and that was expected to take up a significant amount of time. The team was cross functional and dispersed – from vendors to in-house application development folks to network and server infrastructure folks within Canada and the USA. There was no time for detailed planning. The deadline was non-negotiable and the project had to be delivered by the due date.
It appeared that delivering on time was a tall order and the team was wondering how in the world they would get it all done.
Making Kanban work in matrix organizations
For those of us working in matrix organizations, this is reality. We have to constantly juggle between projects, maintenance and operational work. It takes forever for the work to get done. One who screams the loudest always appears to get attention. Work is typically assigned to teams based on schedules and forecasts. The nail in the coffin is that the estimates are treated as deterministic when they are, in fact, probabilistic; i.e. estimates turn into commitment as soon as it gets entered into the Gantt (or a roadmap)