Agile Skills Project Wiki

Search this site

Verbose Landing Page

Split_Testing_orig_starter

To skip over the background and get started right away as a contributor, go directly to Get Involved.

About
The Agile Skills Project is a non-commercial resource that will establish a common baseline of the skills an Agile developer needs to have, including a shared vocabulary and understanding of fundamental practices. The Project intends to:
  • Establish an evolving picture of the skills needed on Agile teams
  • Encourage life-long continuous learning
  • Establish a network of trust to help members find like-minded folk, and to identify new mentors in the community
Among the activities we have an interest in supporting are:
  • defining an Agile Skills Inventory
  • providing a repository for reference courses, interest groups, and other material
  • defining self and peer assessments
  • characterizing of external courses in terms of their coverage of the Agile Skills Inventory
  • defining a “learning ecosystem” including paths of learning, or Quests
  • offering means for publishing team or individual experience reports
  • supporting community rating of courses or trainers
  • supporting ratings for trainers and course
It aims to be independent of any specific form or style of Agile, and explicitly welcomes all such forms and related disciplines such as Lean or Kanban. The idea here is to build an inventory of all the skills that can aid an Agile team member, across the board.

Intended Audience 

The Agile Skills Project aims to be a resource for current and aspiring practitioners, teachers and course designers, and certifying organizations (Intended Audience). The project will focus on skills (see A Skill Is...) that are related to software development and software teams.

History and Context

The project's roots reach to the Chicago meeting in Spring 2009, where people were looking for a way to help developers get better at their craft. A couple months later Ron Jeffries posted the following:

Scrum luminaries freely grant the necessity for good developer practices, and the Scrum Alliance is thinking about developer certification. Some important people in the community are involved, and so am I. Read on …

Saying "certification", of course, was like swatting at a bee's nest, and we had a pretty heated discussion at the Agile Developer Skills list.  Soon the group held the Agile Developer Skills Workshop, which produced the Agile Skills Project Vision Statement.

For a more general statement of agile principles, see the Agile Manifesto.

Get Involved

  • Join the ongoing discussion on the Agile Developer Skills Google Group.
  • Read the Project Resources and request editing permissions as described below.
  • Start topics on the Google Group, then capture the results here on the wiki.

Editing Permissions

We've locked the site to discourage spam. We'll grant you access, just e-mail either of these gmail addresses: d.andre.dhondt or redhotglass .

Receiving email notification of wiki changes

Push notification of changes to specific pages or to any page of the wiki by can be activated by clicking "Subscribe to page changes" or "Subscribe to site changes" from the "More actions" menu at the top right. (You must be signed in to see the menu.)

Project Resources