In software engineering, refactoring a module of code means that you change its internal workings while leaving its external interfaces intact. A developer might do this to make the internal workings of their software simpler, more efficient, or easier to understand. The key is that refactored code maintains it's contract with the surrounding system. Everyone can still get what they need from the refactored system component in exactly the way they have always gotten it.
There is something here we can draw from as project managers. As we make the switch to agile project management, we must stay plugged in with the language of the organization. We need to maintain the contract the business has come to expect. Over time we may be able to influence how our organizations think about project management best practice. At some point we may even be able to renegotiate the contract.
For now, we need to take what we know about adaptive and traditional project management and establish a framework for delivering in the language of the business. The PMI process groups and knowledge areas provide a well thought out and disciplined foundation on which to build. Our challenge is to approach the discipline of project management with an agile mindset. To figure out how to leverage agile practices within the constructs of the accepted project management best practices.
Over the next few weeks we'll break down the PMI process groups, knowledge areas, and processes to explore how we can build an effective agile framework using the established contracts.
Mike, I think this is really important. I am about to take the PMP exam and I find the agile methodologies quite dificult to framework on the "formal" processes and best practice of the PMI. I am trying to implement this methodology at work in the next couple of months. Your articles are really important to understand and balance agile vs PMI
Posted by: Lucas Ritondale | Wednesday, June 04, 2008 at 07:13 PM
Thanks for the reply Lucas. I agree this is an important topic. As agile goes mainstream, more and more traditional project managers will be looking for guidance on how to take what they know and learn how to apply the processes in a brand new context. As agilists, we need more PMs to properly understand what it means to implement agile.
The more we can educate, the better chance we have of seeing agile done right, with the right values, the right discipline, and the right results! Stay tuned, more to come over the next few weeks!
Mike
Posted by: Mike Cottmeyer | Wednesday, June 04, 2008 at 07:52 PM
Oh, I forgot to mention. I just read Michele Sliger's new book 'Software Project Manager's Bridge to Agility'. It is a good read, Michele and I think about this topic very similarly. If you are not already familiar with Mike Griffith's work over at LeadingAnswers, check out his blog at http://www.leadinganswers.com. He shares some great insights on how to adapt and blend PMI concepts for effective Agile project management.
Posted by: Mike Cottmeyer | Wednesday, June 04, 2008 at 07:56 PM
6 years ago I really wanted to be a PM and thought PMP certification was imperative to get there.
5 years ago I was working for a global 50 company and I only needed to take the test to get PMP certification (I had my hours and credits through my company).
4 years ago that global 50 company started to convert to agile and I decided that Agile was new, different, better than PMI defined methodologies and decided to go the way of Agile and not get PMP certified because I didn't want to associate with it thinking it would detract from my Agile path.
Here I stand today having been instructed by or worked with Martin & ObjectMentor, Schwaber, Cockburn, Larson, Rising, Rainsberger, etc... I'm implementing agile in a new company, and I've come to realize that both of these schools of thought are striving for the same goal -- successful business outcomes from motivated and happy teams.
I regret not getting that PMP certification so that I had more authority to speak to the co-existence of PMBOK and Agile approaches. I agree that it is imperative that we strive towards understanding all approaches and learn how to blend them as needed.
I really look forward to your posts Mike and applaud VersionOne's sponsoring of these types of discussions and information sources!
Posted by: Kevin Schlabach | Saturday, June 07, 2008 at 03:01 PM