Changes between Version 4 and Version 5 of Agile LCBRU
- Timestamp:
- 01/27/14 17:10:33 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Agile LCBRU
v4 v5 8 8 We have set up a task board in the office, and will use scrum in three-week cycles of development, or 'sprints'. 9 9 10 Each sprint begins with a 'Sprint Planning Meeting', on the Monday that starts the sprint, to review the 'backlog' and agree stories and tasks to be brought into the sprint. This meeting will be in two parts: firstly prioritising the backlog (a morning discussion to which key LCBRU people will be invited), and secondlyagreeing the plan for the sprint (an afternoon meeting which will be just the four technical team people).10 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). 11 11 12 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. 12 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. 13 14 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'. 13 15 14 16 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. 15 17 16 The first sprint begins on Monday 27th January 2014. It will conclude on Friday 14th February 2014. 18 19 '''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 20 17 21 18 22