Skip to content
Permalink
8401415259
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Go to file
 
 
Cannot retrieve contributors at this time
61 lines (49 sloc) 4 KB

Agile Development

Each week you will be expected to complete a series of lab activities. You will be required to reflect on these in your assignment so make sure you keep records of what you have done.

You should refer to this week's presentation.

1 Conducting the Sprint

During this first sprint, your development team will need to carry out a Daily Standup meeting every morning. Before this meeting, the Scrum Master should:

  1. Check the Kanban board is up to date.
  2. add up the hours for all the tasks remaining incomplete on the Kanban board and using this to update the Burndown Chart.
╔════════════════╦════════════════╦════════════════╦════════════════╗
║ To Do          ║ Planning       ║ Implementation ║ Done           ║
╟────────────────╫────────────────╫────────────────╫────────────────╢
║   ┌────────┐   ║                ║   ┌────────┐   ║   ┌────────┐   ║
║   │        │   ║                ║   │        │   ║   │        │   ║
║   └────────┘   ║                ║   └────────┘   ║   └────────┘   ║
║                ║                ║                ║                ║
║                ║                ║                ║                ║
║                ║                ║                ║                ║
║                ║                ║                ║                ║
║                ║                ║                ║                ║
║                ║                ║                ║                ║
╚════════════════╩════════════════╩════════════════╩════════════════╝
From this Kanban board you can see that one of the tasks has been
completed (and so these hours come off the burndown chart).
One of the tasks has been started but is not yet complete (this stays
on the burndown chart)
The last task has not been fully planned out, this task should be a
priority until the next daily standup.
  40 ║*
     ║   *  o
  30 ║      *     o                 As you can see from this example, by the Wednesday
     ║         *                    meeting the team are behind schedule. They need to
  20 ║            *                 identify *why* this has happened:
     ║               *                * poor estimation?
  10 ║                  *             * one of the teams has hit a problem?
     ║                     *          * members of the team off sick?
  00 ║                        *
     ╚══════════════════════════    Can they make up the work by the Friday?
       M    T     W     T     F

During the meeting:

  1. The Scrum Master reviews the burndown chart and tells the team whether they are ahead or behind schedule:
  2. Now each member:
    1. explains what they have achieved since the last daily standup meeting.
    2. uses the Kanban board to identify the tasks they will work on until the next meeting (tomorrow), flags with the team responsible and moves these forward on the board.
    3. Describes any technical challenges that are holding back development work.

If any problems were identified during the standup these will need to be resolved by the appropriate team immediately after the daily standup. Make sure the resolution is explained to the Scrum Master before continuing work.

Now each team have tasks assigned and will need to implement these before the next daily standup.