|
Why not Subscribe? There's no cost and you can unsubscribe at any time. Live project leadership seminars coming soon: Free project management tutorials at PM Chalkboard. Read my latest book, "I'm Not God, I'm Just a Project Manager." Tweet |
Jethro's Latest BlogApr 18, 2012 Getting Agile-Resistant Teams to Become AgileIf you are trying to get a team resistant to adapt Agile, specifically Scrum, here's some advice. First, ensure you have executive management support and that you exhibit extreme patience. Yes: patience. Get your team together and don't mention Agile at all -- identify the processes that you all use that could stand to be improved. (Don't worry, your most vocal folks will come up with plenty.) Prioritize them and thank everyone for their time. You'll probably have a list of things like "roles unclear," "poor communication," "unrealistic expectations," and "specs kept on changing." These should be known simply as gaps. At another meeting, bring back this list and brainstorm ways to improve those gaps. Without preaching Agile, you'll probably find (as I did), that the "cure" for these gaps will naturally have an Agile prescription for them. For example, "specs kept on changing" could be cured by identifying the Product Backlog at the beginning of a project. Poor communication could be improved by 15-minute Daily Scrums. You get the idea... Next, introduce Scrum to "attack" each of those gaps on a small-scale project. Keep it simple, expect some failure, but I can assure you -- after the second or third project you'll have enthusiastic believers! It doesn't hurt to resync how a more intuitive, iterative process really can fix those gaps everybody complained about. Very Truly Yours, Jethro, of Leading Software Maniacs |
|
|
 |
 |
|||||||||
