It was interesting to know about discussions Pete Deemer had with would be CSMs in his recent certification class. It was both inspiring and matter of feeling proud as he beautifully described how relevant Gandhism (Gandhigiri in lighter sense) is to the role of ScrumMaster.
Below text is what Pete posted in scrumdevelopment yahoogroup:
For those who weren’t in the class, the question was asked “How can the ScrumMaster have any power or influence, since the team doesn’t report to them, and they don’t have the authority to give orders?”
We talked about how in the absence of “managerial” authority, a ScrumMaster can still have enormous influence. But it’s earned influence, and it comes from gaining the trust and the respect of the team, by serving them zealously, and protecting them courageously. This isn’t the cheap authority that comes with an fancy job title; it takes time and work to grow, but it’s a lot more hardy and deep-rooted. And we talked about models for this out there in the world – starting with Mahatma Gandhi, a man who through courage and a spirit of selfless service changed the course of history, all without ever having a high title or powerful position.
I just became Certified Scrum Master (CSM) after attending the required 16 hours training by Pete Deemer. I attended the training at Mumbai on 23,24 February.
Scrum is an agile, lightweight process that can be used to manage and control software and product development using iterative, incremental practices. Wrapping existing engineering practices, including Extreme Programming and RUP, Scrum generates the benefits of agile development with the advantages of a simple implementation. Scrum significantly increases productivity and reduces time to benefits while facilitating adaptive, empirical systems development. Learn more…
Those looking to get Scrum Training in India can visit – http://www.goodagile.com/
Agile development emphasizes close collaboration between the programmer team and business experts; face-to-face communication (as more efficient than written documentation); frequent delivery of new deployable business value; tight, self-organizing teams; and ways to craft the code and the team such that the inevitable requirements churn was not a crisis.
It helps the companies to adopt proactively to ever changing requirements. They are revolutionary in the sense that they contradict the tradional waterfall model in many ways and present a whole new different yet very practical approach to software development process.
Read the Manifesto for Agile Software Development at: http://www.agilemanifesto.org/
and visit the agile alliance at http://agilealliance.org/ to get more info about agile methods.