You've probably read many articles on the difference between traditional project management and agile (specifically, Scrum). One practitioner has been surprised with how established agile practitioners don’t want to let project managers into their “club”. Why can’t project managers become agile?
Code inspections are an implicit, often unspoken best practice among agile project management teams. This silence has caused some people to question the quality control of the agile PM paradigm. Surprisingly, agile teams have not forgotten to mind the Ps and Qs of quality engineering--and not only continue to perform code inspections, but perform them more often. This results in even greater quality than traditional project management teams.
New ScrumMasters may understand the “what” and the “how” of their new practices, but they often don’t understand the “why”. Here we look at two common problems: project managers not creating the sprint burndown charts and teams not participating in the daily standup meetings.
While self-organized teams are valuable and shared responsibility is the way to manage any project, it seems like a project manager is needed to steer things in the right direction--just make sure you allow them to adapt.
So you heard about Agile and Scrum – someone told you it was the silver bullet, you picked up a book, went to a seminar and maybe even actually dished out a few bucks to go get your team certified to be ScrumMasters. You might have even tried a Pilot project so you can try the methods out. So the question is, what’s next? How can I ensure a successful Agile adoption? How can I learn from other people’s mistakes and develop an adoption roadmap that bypasses all the common adoption pitfalls? If you are interested in learning the key real world success factors for Agile adoption, then this webinar is for you!
|
"A classic is something that everybody wants to have read and nobody wants to read." - Mark Twain |
