Road Map

This page serves to organize/prioritize epic stories and potentially group them by release and defines our ways of working.

Ways of Working

    • We communicate respectfully

    • Material is submitted to ADS mailing list for feedback and review

    • We do not top-post, even from mobiles

    • When we start work on a topic, we post our thoughts on acceptance criteria and solicit input from the email group

    • When we're working on a topic, we reply to all comments to acknowledge we got the message.

Definition of Done

    • New articles are peer reviewed

    • Wiki entries are spell checked at least by the author

    • Major changes in wiki page structure are peer reviewed

Sprints

Sprints were run from early March to early April 2010, but have been discontinued until we see more interest. The backlogs are still attached below. The epic stories listed below are still relevant, but since we don't have any way to gauge our velocity, the dates have been stricken out.

An Agile Game, facilitated by Cory Foy in June 2010, identified that the epic stories mentioned below were possibly not as high priority as had been thought originally. It seems that many of those interested in the Agile Skills Project want one of the following:

    • A way to recognize others who have excellent (or at least competent) skills in a given area.

    • A way to indicate to others that they are excellent in a given area.

These two desires are completely understandable, and in a mentor/apprentice scenario are complementary. The most sensible mechanism to accomplish this type of recognition appears to be some sort of Agile Skill Badge. Please see this page for how we think such a badge mechanism might operate and let us know on the Agile Developer Skills email group what you think of the idea.

Sprints are 3 weeks long. When you sign up for an item for the current sprint, you're volunteering to make sure it gets done before the deadline. Note--planned and historical sprints are in the subpages below.

April 9, 2010: Outreach & Quests

    • define a “learning ecosystem” including paths of learning, or “quests”

    • offer a means for publishing team or individual experience reports

    • contact like-minded organizations

May, 2010: Characterization of Training, Certifications, and Individuals

    • define self and peer assessments

    • support existing peer learning communities, by e.g., doing comments on session proposals in the name of ASP

    • characterize external courses in terms of their coverage of the Agile Skills Inventory

    • support community rating of courses or trainers

    • support ratings for trainers and courses

    • increase social capital (connect/ally with other like-minded groups)

July, 2010: Peer-reviewed learning resources

    • provide a repository for reference courses, interest groups, and other material

Future

    • pipe dream: provide an insurance product for software projects/teams that are contributing to the learning ecosystem