For discussion: The Agile Methodology to Improve OASIS DITA Web Sites

[Doug Morrison <dmorrison@dita4all.com>]

The following description of agile methodology is put forward for 
discussion. The process includes reviews to change the methodology if 
found necessary, so nothing is set in stone.

The Agile Methodology to Improve OASIS DITA Web Sites
=================================================

2010-10-27 Draft 1.0 for discussion

Overview
========

Work to be done in the next sprint (a two week period) is decided at a 
Sprint Planning Meeting.
During the sprint, work items are carried out in priority order.

Agenda for Sprint Planning Meetings
===================================

1. Review of previous sprint

1.1 Review impediments to progress

1.2 Review whether agile process is functioning well. Proposals to 
modify it can be added to backlog and assigned a priority.

1.3 Review action items from previous sprint

1.4 Review actions remaining to be completed from previous sprint. 
Reassign if requested by current assignee.

2.  Add new action items taken from backlog, as deemed necessary
     Each new item will be discussed and broken down into smaller 
actions as necessary.
     Allocate items to a particular track:
     a) Main track
     b) Impediment resolution
     c) Infrastructure development
     d) Small Item Fast Track (SIFT)
     e) Other tracks as necessary

3.  Allocation of work items
     Allocate some of the work items to volunteers
     Any work item can be carried out by any volunteer.

Work During the Sprint
======================

1. Volunteers put their names against work items and carry them out, 
marking them as in progress, or done, as appropriate.

2. If impediments are encountered, the facilitator (scrum master) is 
notified. Resolution of impediment is discussed with facilitator, who 
has primary responsibility for resolving the impediment.

3. Before each Sprint Planning Meeting each volunteer should try to 
ensure that each work item has accurate status recorded.

4. Daily scrum meetings are not appropriate. Email will be used to 
indicate intention to do work, and record progress and impediments 
encountered (typically one email per week from each volunteer).

5. Exact priority order is not important. Opinions will differ. Priority 
of a work item is greatly enhanced by the words "I am willing to work on 
this".

6. Work quantity estimates for backlog items, if done at all, will be in 
terms of doughnuts to indicate that it is just a rough guesstimate.
Roughly speaking, a doughnut is about a day's work, ten doughnuts is 
more than a week's work.

As far as possible communication is carried out by email, to minimise 
length of online meetings.

The unwritten final rule: Common sense will be applied.


Reference
=========
Some terminology used above is explained in
http://www.writersua.com/articles/Agile_doc/index.html

-- 
Best regards,

Doug Morrison
Information Architect
http://dita4all.com