Changes between Version 6 and Version 7 of Agile LCBRU

Timestamp:

02/19/14 09:00:00 (10 years ago)

Author:

Nick Holden

Comment:

--

Agile LCBRU

@@ -8 +8 @@
 We have set up a task board in the office, and will use scrum in three-week cycles of development, or 'sprints'.
 
-Each sprint begins with a 'Sprint Planning Meeting', on the Monday that starts the sprint, to review the overall project backlog and agree stories and tasks to be brought into the sprint backlog. This meeting will be in two parts: firstly prioritising the backlog (a morning discussion to which key LCBRU people will be invited), and secondly estimating effort and agreeing the plan for the sprint (an afternoon meeting which will be just the four technical team people).
+Each sprint begins with a '''Sprint Planning Meeting''', on the Monday that starts the sprint, to review the overall project backlog and agree stories and tasks to be brought into the sprint backlog. This meeting will be in two parts: firstly prioritising the backlog (a morning discussion to which key end users will be invited), and secondly estimating effort and agreeing the plan for the sprint (which will be just the four technical team people).
 
-The user stories or requirements will be broken down into tasks - each task will be represented on the task board by a post-it note, and in the trac system by a ticket. Each sprint will be entered as a milestone in the trac system, so the tickets can be sorted by milestone, to get a record of which tasks were attempted in each sprint.
+The user stories or requirements will be broken down into tasks - '''each task will be represented on the task board by a post-it note''', and in the trac system by a ticket. Each sprint will be entered as a milestone in the trac system, so the tickets can be sorted by milestone, to get a record of which tasks were attempted in each sprint.
 
-Each day during the sprint we will have a fifteen minute stand-up meeting, in the office, in front of the task board. We will review the progress since the previous day, each of us will report on our progress, on our plan for the day, and on any obstacles in our way. We will volunteer to pick up tasks, and begin to move them from 'To Do' to 'Done'.
+Each day during the sprint we will have a '''fifteen minute stand-up meeting''', in the office, in front of the task board. We will review the progress since the previous day, each of us will report on our progress, on our plan for the day, and on any obstacles in our way. We will volunteer to pick up tasks, and begin to move them from 'To Do' to 'Done'.
 
-At the conclusion of the sprint, on the Friday afternoon, two meetings will take place: one to review the work done / not done, and demonstrate new functionality to end users, and one (called the 'retrospective', with the technical team only) to review the sprint and agree any process improvements for subsequent sprints.
+At the conclusion of the sprint, on the Friday afternoon, two meetings will take place: a '''Sprint Review''' to review the work done / not done, and demonstrate new functionality to end users, and  a '''Sprint Retrospective''' (with the technical team only) to review the sprint and agree any process improvements for subsequent sprints.
 
+To help track progress during each sprint, the tasks will be checked against a 'burndown chart' showing for each day in the sprint how many tasks remain uncompleted. We are using a simplified burndown chart for the time being.
+
+Following the first sprint, we have added two other visualisations on the main whiteboard in the office. One is a '''pain chart''' to list annoyances and blockages which we don't fix immediately. When they trigger repeated entries in the pain chart, we prioritise resolving them. The other is an '''improvement board''' where we list improvements in our own processes that we wish to make, and track implementation of the improvements.
 
 '''The first sprint begins on Monday 27th January 2014. It will conclude on Friday 14th February 2014.''' The task list for the first sprint is available by doing a search of the trac ticket list, or just clicking this link: http://lcbru-trac.rcs.le.ac.uk/query?group=status&milestone=Sprint+1
 
-25 tasks included in the sprint. 15 done. 10 not done.
-
-95 units work estimate. 56 completed. 39 not completed.
+25 tasks included in the sprint: 15 done, 10 not done. 95 units effort estimate: 56 completed, 39 not completed.
 
 '''The second sprint begins on Tuesday 18th February and concludes on Friday 7th March.'''
 
-
+24 tasks included in the sprint. 144.5 units effort estimate.