Presentation is loading. Please wait.

Presentation is loading. Please wait.

A Few Agile Practices Or how to plan who does what over the next two weeks when Iteration I is due C Sc 335 Rick Mercer.

Similar presentations


Presentation on theme: "A Few Agile Practices Or how to plan who does what over the next two weeks when Iteration I is due C Sc 335 Rick Mercer."— Presentation transcript:

1 A Few Agile Practices Or how to plan who does what over the next two weeks when Iteration I is due C Sc 335 Rick Mercer

2 2 An Agile Practice The Planning Game The planning game involves user stories –The requirements or short descriptions of desired features Write stories and assign story points –Then estimate them using the Fibonacci sequence, 1 is the easiest, 13 is the most difficult Story points are estimates of relative complexity: 1 3 5 8 13 They are not hours to spent coding Learning to estimate is good –You get good at estimation by doing it

3 3 An Agile Practice: Iterations Iterations typically range from 1 to 4 weeks (when full time). –We use a two-week Iteration Because classes are ending 335 Projects should be about half done in two weeks Attempts to avoid procrastination First Iteration is due by Thanksgiving week –Face to face grading in team meeting times Monday, Tuesday, or Wednesday. Team Meeting Times TBA today –Thursday or Friday teams get graded in Econ 211 3:30-5:00 Tuesday 26-November

4 4 Sprints continued Plan Iteration 1 now –Write down as many stories as you can –Prioritize: Which “stories” should be developed first We need to see working systems, limited functionality –think text based output, and/or running tournaments to show who wins or loses, no user interaction required –Create the tasks needed to get the story working A task is a technical requirement such as implement a Command hierarchy for 5 commands Assign tasks to teams of 2 (or 1 in teams of 3) Finish tasks so the stories are satisfied in Iteration 1

5 Preview am Iteration in Progress Ken Schwaber task board mockup 5

6 Actual Task Board we can not do 6

7 How do we plan and track Recommended –Use a shared Google Spreadsheet to as many stories as you can Originally, all of this was kept in a spreadsheet in industry –Below the stories, write the tasks, and which two programmers (or programmer) will complete them Write done when done with the tasks or stories This helps plan and track the 335 final project Keeps the team on task Can see who did what 7

8 You could use Rally if you want 8


Download ppt "A Few Agile Practices Or how to plan who does what over the next two weeks when Iteration I is due C Sc 335 Rick Mercer."

Similar presentations


Ads by Google