Planning

Question 1

Planning

Answer 1

• How much shall we plan?
• A good plan is one that supports reliable decision making
• Will go from
  
  • Well be done in the fourth quarter
  • We will be done in november
  • We will be done November 7th

Question 2

Planning in Agile

Answer 2

Question 3

Three levels of planning

Answer 3

Question 4

Three levels of precision

Answer 4

Question 5

Release plan

Answer 5

• Release plan
  
  • List of main areas of focus
  • Two questions to initiate release planning
    
    • When do we want the release
    • what is the priority of each story
• Plan release by estimating how much work the team will be able to accomplish in each iteration
• Reasonable prediction about how many iterations it will take to product a release

Question 6

Prioritizing the stories

Answer 6

• Tecnical dimension
  
  • The risk the story cant be completed as desired
  • The impact the story will have on other stories if deffered
• Customer and user dimension
  
  • The desiribility of the story to a bread base of users or customers
  • The desiriability of the story to a small number of important users or customers
  • Cohesivness of the story in relation to other stories

Question 7

Types of plans

Answer 7

• Scopeboxed
  
  • Defines the features the team will build in advanced but the release date is uncertain
• Timeboxed
  
  • Defines the release date in advance but the specific features that release will include are uncertain

Question 8

Iteration plan

Answer 8

• Iteration planning are important to take the planning process one step further.
• Planning meeting
  
  • Customer and all of the deverlopers
• General sequence of activites
  
  • Discuss a story
  • Dissagregate the story into its constituent tasks
  • One deverloper accepts responsibility for each task
  • Developers individually estimate the tasks they´ve accepted and make sure they are not over-committed

Question 9

Daily plan

Answer 9

• Each team member looks a day ahead, have learned from the earlier days in the iteration and tell each other what they plan on doing
• Issues are raised, possibly addressed and the success of delivering the desired features within the iteration can be determined after the meeting

Question 10

The plan put together

Answer 10

Question 11

Initial velocity

Answer 11

Þrjár leiðir til að meta velocity

1. Nota gömul meðaltöl
2. Keyra 1-2 ítranir og sjá hvað kemur
3. Spá um það

• Should be expressed as a range
• Size of range depends on familiarity of the team, domain and technologies

Question 12

Measuring and monitoring velocity

Answer 12

• Only finished stories
• Difference between actual and planned velocity, graph both
• Dont try to predict trends in velocity after only one or two iterations
• The number of action hours spent completing task or story have not bearing on velocity
• Post big, visable chart in common areas where everyone can see them
• A cumulative story point chart shows total number of story points completed in the end of iteration
• An iteration burndown chart whos both progress in the form of story points completed as well as changes to the number of story point planned for the remainder of the release
• A daily burndown chart showing the hours left on each day of an iteration is very useful during an iteration

Question 13

Release burndown chart

Answer 13

• Shows both progress in the form of story points completed as well as changes to the number of story point planned for the remainder of the release

Question 14

Daily burndown chart

Answer 14

• A daily burndown chart shows the hours left on each day of an iteration

Question 15

Cumulative story point chart

Answer 15

• A cumulative story point chart shows total number of story points completed by the end of iteration