Skip to content
Permalink
Browse files
completed the gile processes lab
  • Loading branch information
aa7401 committed Oct 10, 2019
1 parent 7ba9fb8 commit faf4ad6a8747c15e19df87c5fd679d005202454f
Showing 1 changed file with 47 additions and 0 deletions.
@@ -1,2 +1,49 @@

# Agile Processes

You have now spend a couple of weeks working together as a team and have explored the psychology behind the team's effectiveness and interactions. This week you will introduce some simple agile processes in order to improve the overall effectiveness.

You will be continuing the development of the system but should now introduce the following steps:

## Planning

1. Start by loggin into MS Teams and add a new tab to your workspace. You should choose the Planner tool and label the tab **Kanban**.
2. Add three columns to the board:
1. Not started.
2. In progress.
3. Completed.
3. Go through the prioiritised list of features you created a few weeks ago and decide on which feature you will be developing next. Now discuss the jobs needed to complete this and add them to the left column (Not Started) of the Kanban board.
4. Now play planning poker for each job with each member of the team secretly deciding how many hours the task should take. Members reveal the hours on the fingers of one hand with 5 fingers representing more than 4 hours.
5. If there is a discrepancy between the team discuss then repeat the vote.
6. If the team agree the task will take more than 4 hours, split it into two smaller tasks and vote on each.
7. Record the predicted hours on the Kanban card.

One of the team should agree to be the **Scrum Master**. They add up all the hours of all the tasks and use this to create a burndown chart in a shared excel spreadsheet.

## Development

Now each person chooses one of the tasks to work on:

1. They drag the card to the middle column.
1. Assign themselves to the task (never assign anyone else).
2. Set the status to **In Progress**
3. They immediately start work on the task.
4. When someone finishes their task:
1. They drag it to the last column.
2. Set its status to **Complete**.
3. Pick another tasks and repeat step 1.

Note:

1. There must never be more than one card assigned to a person
2. No card can be assigned to more than one person.

## Daily Standup

Each time the team meet:

1. The Scrum Master should have updated the burndown chart before the meeting.
2. Each person in the team speaks for 30 seconds:
1. What have they completed since the last meeting?
2. What are they planning on completing before the next meeting?
3. Are there any issues the Scrum master needs to help them resolve?

0 comments on commit faf4ad6

Please sign in to comment.