10 tips on how to prevent business value risk
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Kurt Christensen on Feb 15, 2007
As it stands today, the [Certified Scrum Master (CSM)] program is a fairly hollow certification. Pay the tuition, sit through a couple days of class, and you're in. And while I realize there's quite the CSM training industry taking advantage of the current program... I would encourage those that continue to milk it to take a step back and consider whether they're doing more harm than good.Arguments for and against certification have been lobbed back and forth within the agile community for years. But assuming certification is even a worthwhile goal, what can be done to make the certifications meaningful? The Agile Chronicles article offers many of the same suggestions voiced by Martin Fowler and others:
Make it a certification with some real substance:
- Have some real pre-reqs: relevant experience and an assessed level of knowledge about scrum & agile methods
- Incorporate a practicum of sorts
- Actually evaluate knowledge & practical experience, preferably via interview vs. written
Other professions have certification processes that demand all this and more. In a recent InfoQ interview, Kent Beck drew comparisons and contrasts between the agile community and the medical community:
I think it makes sense for practitioners to be accountable for their own skills and results. I don't think traditional certification processes - take a test, get a piece of paper - do this. On the other hand, other professions have meaningful certifications. If you are a board certified physician, it means something. The process is very different from the certifications in computing, though. It takes a long time, it's expensive, the examiners are experts, it requires a significant amount of study and a demonstration of the precise use of your knowledge in real situations.There are two problems with trying to implement such a rigorous certification process within the agile community. In medicine, the stakes are life and death, and so society demands a minimum level of competency before allowing anyone to practice medicine at all. Therefore, potential doctors have an incentive that simply doesn't exist in the software community, and isn't likely to ever exist. In addition, board certification for medical doctors is overseen by a non-profit organization which essentially acts as a regulatory agency. In the software community, the few certification bodies which do exist do so for profit, and thus have at least a partial interest in seeing more people become certified.
Transforming Software Delivery: An IBM Rational Case Study
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
The classes offered by the Scrum gurus are valuable. The certifications they award are also valuable.
That said, the essence of Scrum can be described to anyone in the span of 5 - 10 minutes - as it should be.
Anyone who as participated on a Scrum team, can most certainly participate and/or lead another Scrum team. That's the beauty of Scrum - it's simple, straight forward and effective. Toss in a few XP practices, and you've got a winning development process - IMHO.
While I agree that the CSM thing is getting out of control (and I expressed my dubts about the use of the word "certification" in 2003 on the Scrumdev list) I invite people to actually read the descriptions of the certification levels: www.scrumalliance.org/view/certification
It's very clear from that page that a CSM has just attended a basic course, nothing more. Only a CSP (Practitioner) has certified, demonstrated competence. As far as the ScrumAlliance is concerned of course...
Scrum and PMP certifications are designed to provide a baseline skill level for customers of our profession to use in determine a person's minimum competency. Neither organization warranties the quality of the individual's work, just that the person has done what is needed to meet the certification criteria.
If these two approaches were dance steps, SCRUM would be the waltz and PMP would be the Minuet (aka Menuet).
Scrum and the waltz are made up of a small number of very easily learned steps and a couple of variations. Easy to master, the waltz is effectively emp;loyed for teaching 9 year olds the basics of 1,2,3 1,2,3 1,2,3 and world champion dancers, skaters, and rollerbladers the components to attaining gold medals, money and closets full of outrageous clothes.
PMP and the Minuet are composed of dozens and dozens of structured, detailed steps that are chosen carefully and learned over time to produce movie backdrops for times long past.
So what do you want to do?
> PMP [is]... composed of dozens and dozens of structured, detailed steps that are chosen carefully and learned over time to produce movie backdrops for times long past.
Well Mike, that explains a LOT! ;->
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
Sean Cribbs explains what Map-Reduce and Riak are, why and how to use Map-Reduce with Riak, and how to convert SQL queries into their Map-Reduce equivalents.
4 comments
Watch Thread Reply