I just found out about Zombie Scrum and I had a great laugh! Go ahead Google it – zombie scrum. It’s hysterical and 100% true.
And it’s why I feel compelled to write. It has a name now – ‘ZOMBIE PROJECT MANAGEMENT’. It drives me insane – at all levels.
To be clear – this is not just about scrum and agile, this is about waterfall too and all hybrids. This is equivalent to bean counters, box checkers, boring status meetings. This should be at the VERY top of every ‘common project management mistakes’. Going through the motions, no emotional intelligence, no foresight, no life, no caring. That’s what this is really talking about – moving those stickies across the wall without giving a sh*t about what you’re doing or why. Makes me so frustrated.
I LOVE the term Agile Coach. What a great segue away from the mundane to something active and alive. Waterfall is too old fashioned – for many reasons and at many levels but it’s not completely obsolete yet. I’m not a huge proponent of Agile by the way – it has it failures too. I am a proponent of do what’s needed in the situation you’re in – maybe it’s agile, maybe it’s waterfall, maybe it’s a hybrid, maybe it’s pure lean. Take the time to see what is going on and pick the right process and methodology for the personalities/project/time you have to do it.
I was told once by a consultant who specialized in culture, that when she looked around everything pointed to culture as the problem and the solution. I didn’t believe her. I thought everything was about being productive and working together because that’s what mattered to me.
When I looked at what, how, why I do (Thank you to Simon Sinek), I found a system: What = Same Road, Same Time, Same Direction. How = I manipulate the fabric of team dynamics. Why = Create Accountability.
When I put it all that together and saw the system I create – you can’t have a system of positive accountability unless you have a positive culture that supports it.
The reason I can turn projects around, even ones that are going up in flames, is that I change the micro culture of the project and create a system of accountability.
Large projects take on a life of their own. They are unwieldly with lots of moving parts and issues coming at us from all sides. It’s a lot to hold on to so these usually become ‘programs’ and we hire a group of project managers to keep track of all the details. That’s all well and good – details matter.
Having been responsible for this type of project before but on my own, it’s tough to take a step back from the details and look at the project as a whole. Where is it heading? Are we going off the rails with all the problems? Are these ‘normal’ problems and we are continuing in our forward momentum? Are we going awry? Is there one cause or one person who is a bottleneck? Is there a department that is always behind or a person making things overly hard?
I’ve talked about the ART of project management and this is where the rubber hits the road. This is where the expert resides. Finding the answers to these questions is being the conductor – looking around at your orchestra, seeing patterns and seeing the difference between symptoms and the real problems.
I’ve done a lot of different project plans and I’ve seen a lot more. I’ve seen people put in a series of status meetings as tasks which only front loads the project level % complete. I’ve seen Sponsors want individual steps for each repeatable task put in the plan because they feared we would forget them. I’ve done 5000-line project plans because there was that much to do. I’ve done little 40-line ones that are very high level and just keep us on track.
All very purposeful and useful and very like a bean counter.
I wish MS project/SmartSheets/etc was more fluid and allowed for us to see past the tasks and look at the project as a river system with lots of small trickles and streams. All leading into a large river that supported the environment and provided even more than what we originally needed. Instead, I find projects get blocked and misguided due to not taking the time to do business requirements and not thinking through the design and not taking the time we need to be successful. Of course, there are constraints of time, resources, and scope but we take short cuts and remove scope due to our misunderstandings and assumptions, so we produce small rivers that don’t support even our basic needs.
What if we did the right thing from the beginning? Is that so hard?
Expectations are TOUGH. You need some of them but not too many of them and they need to be just above where you are, so you strive to be more but not too high and they need to be realistic, so you feel motivated. How in the world can you make that work? Especially as a matrixed project manager who doesn’t know these folks very well.
Expectations are CRITICAL. This is what gives your team the belief that they can do it. But, can also demotivate them if it feels out of reach or not presented with appropriate belief.