AGILE IN ACTION

Thursday, 29 March 2007

Agile Alliance on Certification

Posted by Simon Baker

Here is the position statement on certification from the Agile Alliance . I’ve highlighted what I believe to be the key points.

This position statement is released by Agile Alliance board in response to questions we receive from our members regarding certification in Agile.

Now that Agile software development is becoming a mainstream practice, more and more employers need to staff teams that will perform it well. How can they know if a particular person will be an asset?

One way might be to favor employees who are vouched for by some certification body. It is the position of the board of the Agile Alliance that employers should have confidence only in certifications that are skill-based and difficult to achieve. We also believe that employers should not require certification of employees .

Certifications in our industry usually tell you that a person has been exposed to particular knowledge. Some certifications additionally tell you that she has passed
a test on that knowledge.

Knowledge is a wonderful thing, but businesses pay for performance. Performance requires skill.

A skill is not as simple to acquire as knowledge: the learner has to perform the skill badly, recover from mistakes, do it a bit better, and keep repeating the whole process. Especially f or the interrelated and interpersonal skills required of Agile software development, much of the learning has to take place on real projects . It is that learning that a certification should vouch for.

Vouching for someone else’s skill requires close observation or questioning by someone already possessing it. For anything other than uninterestingly simple skills, that’s a lot of work - which means it’s expensive. Therefore, the only skills worth formally vouching for are those that require substantial effort to learn.

While a skill-based certification can shorten the hiring or promotion process, there are many skilled practitioners who are not certified. Excluding them from consideration would be a poor business decision.

Moreover, the state of the practice moves on.Skills decay when unused. The question is not whether an applicant once possessed appropriate skill; it’s whether the applicant can do what’s required today. A certificate cannot substitute for the hard work of individual evaluation .

Certifications such as Certified Scrum Master and DSDM Foundation are knowledge-based and easy to achieve. We believe the courses that lead to them are good ones. We believe people who attend them get their money’s worth. But while the certifications may be evidence of good faith, useful knowledge, and a desire to learn, they are not in themselves evidence of skill.

Higher levels of certification, such as DSDM Practitioner or Certified Scrum Practitioner, require project experience, a written project synopsis, and an oral examination. They are skill-based. Other organizations like the Agile Project Leadership Network are working on skill-based certifications. We applaud their efforts.

Creative Commons Licence

Recent Posts

  1. Pursuing features increases total cost of ownership
  2. Organization complexity is a waste farm
  3. Managing costs provides a false sense of security
  4. State of Agile survey for 2011 tells a familiar story
  5. (I can't get no) satisfaction, let alone customer delight
  6. Positive emotions and purpose
  7. People don't buy what you do, they buy why you do it
  8. Too busy chopping wood to sharpen the axe
  9. So you want a fresh apple
  10. Systems are seductive

Archives

  1. 2012 (6)
  2. 2011 (24)
  3. 2010 (31)
  4. 2009 (41)
  5. 2008 (69)
  6. 2007 (152)
    1. December (11)
    2. November (7)
    3. October (17)
    4. September (8)
    5. August (7)
    6. July (13)
    7. June (15)
    8. May (24)
    9. April (14)
    10. March (19)
      1. Agile Alliance on Certification
      2. Saying 'No' doesn't have to be mean nor painful
      3. If everything is equally important, then nothing is important
      4. It's a stragedy
      5. Ready-to-go agile team
      6. Calling in well
      7. United Intent: Teams not groups
      8. Developing business awareness and acumen
      9. Multitasking is a way to avoid prioritisation
      10. Pull the wool over your eyes
      11. The scene about agility in A Few Good Men
      12. Don't skip the Prime Directive
      13. Adapting Scrum without compromising it
      14. Regular successes build momentum
      15. Agility and adaptation
      16. Go with the flow and find happiness
      17. Anti the anti team
      18. We're not limited by our abilities, but by our vision
      19. Offshoring is wasteful
    11. February (7)
    12. January (10)
  7. 2006 (128)
  8. 2005 (63)
  9. 2004 (2)

Tags

agile (43) big visible chart (15) conference (39) culture (18) extreme programming (21) leadership (18) lean (47) people (26) planning (17) retrospective (18) scrum (41) story (18) team (30) testing (18) xpday (19)