-
Two Types of Workflow: Software and Human System
May 24, 2012
-
10 Benefits of a Project Management Software System
May 24, 2012
-
Spotting a Failing Project: 9 Warning Signs
May 23, 2012
-
Values of Effective Project Managers
May 23, 2012
-
Calm in the Eye of the Storm
May 23, 2012
-
Management by Heroics
May 22, 2012
-
Project Planning for Project Sponsors: Why You Need To Be Involved
May 22, 2012
-
Lost in Projects - Integrated Project Management
May 22, 2012
-
10 Warning Signs that Your SharePoint Implementation May Be Heading for Difficulty
May 21, 2012
-
Smaller is Better and More Effective
May 21, 2012
The Baking (Agile) Manifesto - Trust and a Light Touch
January 21, 2009 | Author: PM Hut | Filed under: Agile Project Management, Communications Management, Program Management, Project Management Best Practices
The Baking (Agile) Manifesto - Trust and a Light Touch (#2 in the series The Baking (Agile) Manifesto)
By Melanie Carasso
In my previous article, The Baking (Agile) Manifesto - Collaboration and Creativity, I introduced the Baking Manifesto - a set of 4 values inspired by the Agile Manifesto and, yes, baking. I briefly covered the first value “Collaboration and creativity over silos and cookie-cutting”. Now for the second value…
Trust and a light touch over frequent temperature checks and thorough mixing
A well-known principle of baking is to not open the oven door too many times while your cake is baking. Doing so will cause the temperature to vary, and the cake will not rise evenly. Slamming the oven door after checking the cake is the ultimate “don’t” - air will escape from the batter and your beautiful chocolate sponge or tangy moist lemon cake will implode to form a crater you could lose a Mars rover in.
The same goes for programs. If you’re running a large program, there will most likely be a number of project managers managing parts of the program and reporting status, risks & issues to you. Let’s assume you have a couple of senior-level project managers and one or two newbies. You could spend all of your time taking the temperature of each project - especially those run by the newbies - throughout the program, so you don’t have to worry about someone taking a wrong step and jeopardising the program. You could go around slamming oven doors and rattling pans when you’re not happy with progress, but that definitely won’t have any sustainable positive effects on team morale or the status of the program.
Instead, try setting up some guidelines for everyone at the start of the program - including example reports, registers, etc - then gather the project managers together for regular status sharing sessions. You’re trying to be agile, so there shouldn’t be a huge stack of documents to wade through each meeting. Each project manager should be presenting a brief synopsis of their project - actual status compared with planned; the top 3 - 5 risks and issues; mitigation plans; and any other relevant news.
Trust your project managers to own their parts of the program and do a great job. A little bit of competitiveness is a common trait in good project managers, and they will rise to the challenge. Their job is to know a lot more than you about the details of each project. Coach the newbies during the early phases of the program, then step back a bit and let them test their wings. They will learn from what the seniors present and discuss, and you can apply a light guiding touch to both newbies and seniors as needed throughout the program. Of course, if you have an underperforming project manager, you’ll need to step in and provide a greater level of mentoring (or more) to get them back on track - a topic for another day. But if your organisation is hiring the right talent, even the most junior project managers will quickly learn from their own mistakes, develop their own unique style and approach, and evolve into competent, experienced project managers before your eyes.
Overmixing is another baking “don’t”. It’s tempting to keep on stirring until there are no more lumps, but that just makes for tough muffins. In the same way, keep your program meetings to a minimum, in terms of both participants and frequency. If you have a distributed team, it makes sense to get everyone together for a regular videoconference, so they can have some valuable face-to-virtual-face time. But if your teams are colocated, you should be able to get by with just the project managers attending the meetings, and maybe a senior tech lead or architect. Choose the frequency of the status meeting in accordance with the expected duration of the program. If it’s a 12-month (or longer) program, every two or four weeks is a good frequency for status meetings. If it’s a 3-month program, weekly meetings make sense.
Obviously you can’t step so far back that the program goes off the rails. I tend to take ad-hoc deeper dives with individual project managers in between the main status meetings, especially if I’m concerned about a particular area. Or I’ll set up quick weekly checkpoints for the high-risk or critical-path projects, to help identify and remove obstacles.
Trusting in your team and keeping your touch light will not only help your project managers own their projects and manage them with confidence; it will leave you more time to do the program management work you need to be doing - such as assessing the strategic value of your programs; keeping your stakeholders informed and engaged; and co-ordinating the dependencies between projects.
Melanie Carasso is the program manager at Atlassian, an Australian software company that develops collaboration and development tools including JIRA and Confluence. Melanie has been managing software projects and programs for the past 8 years in various regions of the waterfall-agile spectrum, at telecommunications, medical management and industrial automation companies. Before diving into software project management, Melanie worked as a research scientist in microelectronics and fiber optics at Bell Labs and IBM in the US. She holds a PhD in chemistry from the University of Sydney and is PMP certified. In her blog, The Agile Program Manager, she shares her thoughts on managing programs in an agile way.
Related Articles
feel free to leave a comment
Comment Guidelines: Basic XHTML is allowed (a href, strong, em, code). All line breaks and paragraphs are automatically generated. Off-topic or inappropriate comments will be edited or deleted. Email addresses will never be published. Keep it PG-13 people!
XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
All fields marked with " * " are required.
- Agile Project Management
- Ask the Hut
- Certification
- Change Management
- Communications Management
- Computer Based Information Systems
- Concepts
- Corporate Transformation
- Cost Management
- Critical Chain Project Management
- Delegation
- History
- HR Management
- Implementing Project Management
- Integration Management
- Lessons Learned
- Management
- Miscellaneous
- People Issues
- PMBOK
- PRINCE2
- Procurement Management
- Program Management
- Project Lifecycle Phases
- Project Management Advantages
- Project Management Advantages
- Project Management as a Career
- Project Management Best Practices
- Project Management Charts
- Project Management Definitions
- Project Management Ethics
- Project Management for Beginners
- Project Management Guides
- Project Management Musings
- Project Management Office
- Project Management Proposals
- Project Management Templates
- Project Portfolio Management
- Project Workforce Management
- Quality Management
- Requirements Management
- Risk Management
- Scheduling
- Scope Management
- SCRUM
- Soft Management
- Time Management
- Training
- Uncategorized
1 person has left a comment
[...] covered Collaboration and creativity over silos and cookie-cutting, and Trust and a light touch over frequent temperature checks and overmixing. Now it’s time to look at the third value of the Baking [...]