Difference between revisions of "Agile Experiment PDF-Import 2007"
From Apache OpenOffice Wiki
(→Iterations) |
|||
| Line 8: | Line 8: | ||
From 5.11.2007: 4-6 weeks | From 5.11.2007: 4-6 weeks | ||
| − | ==== | + | ==== Regular Meetings ==== |
| + | Daily Scrum: 13:40 - 13:55 | ||
| + | |||
| + | |||
| + | === Iterations === | ||
# 8.11. - 19.11. (Thu.-Mon.) | # 8.11. - 19.11. (Thu.-Mon.) | ||
# 20.11. - 3.12. (Tue.-Mon.) | # 20.11. - 3.12. (Tue.-Mon.) | ||
# 4.12. - 17.12. (Tue.-Mon.) | # 4.12. - 17.12. (Tue.-Mon.) | ||
| − | ==== 1st Iteration ==== | + | ==== 1st Iteration Special Meetings ==== |
{| | {| | ||
| Planning: || 8.11. || 10:30-12:00 | | Planning: || 8.11. || 10:30-12:00 | ||
| Line 23: | Line 27: | ||
| Teaminternal Retrospective: || 19.11. || 15:00-17:00 | | Teaminternal Retrospective: || 19.11. || 15:00-17:00 | ||
|} | |} | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| Line 72: | Line 49: | ||
''(Link to the Iteration Backlog pages)'' | ''(Link to the Iteration Backlog pages)'' | ||
| − | == | + | == Agile Methodolgy in General == |
| + | |||
| + | === Agile Manifesto === | ||
| + | * http://agilemanifesto.org/ | ||
| + | |||
| + | === English descriptions === | ||
| + | * [http://www.mountaingoatsoftware.com/scrum/ Lots of short, precise, useful information] | ||
| + | * http://en.wikipedia.org/wiki/Agile_software_development | ||
| + | * http://www.think-box.co.uk/pdf/scrum/IntroductionToScrum.pdf | ||
| + | |||
| + | === German descriptions (as most team members are german, these may be useful) === | ||
| + | * http://de.wikipedia.org/wiki/Scrum | ||
| + | * http://de.wikipedia.org/wiki/Extreme_Programming | ||
| + | * http://de.wikipedia.org/wiki/Crystal_Family | ||
| + | |||
| + | === Suggested Practices to Adopt === | ||
| + | * Scrum roles (Product Owner, Team, Scrum master) | ||
| + | * Colocation | ||
| + | * Team that includes definition, code-writing and testing together | ||
| + | * Time Boxing | ||
| + | * Continuous testing | ||
| + | * Short, fixed-time iterations | ||
| + | * Daily (or more frequent) integration + builds | ||
| + | * "Scope" is variable <=> "time", "cost" and "quality" are fix. | ||
| + | * Regular reflection | ||
| + | |||
| + | === Scrum "Smells": Hints that something goes wrong === | ||
| + | * '''Loss of Rhythm''' - Sprints are not always the same length. | ||
| + | * '''Talking Chickens''' - Non team members talk at daily scrums. | ||
| + | * '''Missing Pigs''' - Not all (fully assigned) team members attend the daily scrum. | ||
| + | * '''Persistent Signatures''' - Progress charts in later iterations look as fluctuative as in the first iterations. | ||
| + | * '''ScrumMaster Assigns Work''' - In planning, the scrum master assigns work, instead of the developers signing up. | ||
| + | * '''The Daily Scrum is For the ScrumMaster''' - Daily scrums feel like reporting sessions to the scrum master. | ||
| + | * '''Specialized Job Roles''' - A project team has highly specialized job roles ("architect", "tester" etc.) | ||
| + | |||
| + | == Links == | ||
[[Writer/ToDo/PDF Import]] | [[Writer/ToDo/PDF Import]] | ||
Revision as of 18:09, 6 November 2007
A loose gathering of resources and ideas about the Agile Experiment in developing PDF-Import in 2007.
Organization
Time Frame
From 5.11.2007: 4-6 weeks
Regular Meetings
Daily Scrum: 13:40 - 13:55
Iterations
- 8.11. - 19.11. (Thu.-Mon.)
- 20.11. - 3.12. (Tue.-Mon.)
- 4.12. - 17.12. (Tue.-Mon.)
1st Iteration Special Meetings
| Planning: | 8.11. | 10:30-12:00 |
| Teaminternal Planning: | 8.11. | 12:30-14:00 |
| Review: | 19.11. | 12:00-14:00 |
| Teaminternal Retrospective: | 19.11. | 15:00-17:00 |
Planning
Product Backlog
- (Link to the Product Backlog page for this project) -
Example and description of a Product Backlog
Hints for the Product Backlog Maintainer
Characteristics of User Stories
User stories shall be "INVESTed":
- independent
- negotiable
- valuable
- estimable
- small
- testable
Iteration Backlogs
(Link to the Iteration Backlog pages)
Agile Methodolgy in General
Agile Manifesto
English descriptions
- Lots of short, precise, useful information
- http://en.wikipedia.org/wiki/Agile_software_development
- http://www.think-box.co.uk/pdf/scrum/IntroductionToScrum.pdf
German descriptions (as most team members are german, these may be useful)
- http://de.wikipedia.org/wiki/Scrum
- http://de.wikipedia.org/wiki/Extreme_Programming
- http://de.wikipedia.org/wiki/Crystal_Family
Suggested Practices to Adopt
- Scrum roles (Product Owner, Team, Scrum master)
- Colocation
- Team that includes definition, code-writing and testing together
- Time Boxing
- Continuous testing
- Short, fixed-time iterations
- Daily (or more frequent) integration + builds
- "Scope" is variable <=> "time", "cost" and "quality" are fix.
- Regular reflection
Scrum "Smells": Hints that something goes wrong
- Loss of Rhythm - Sprints are not always the same length.
- Talking Chickens - Non team members talk at daily scrums.
- Missing Pigs - Not all (fully assigned) team members attend the daily scrum.
- Persistent Signatures - Progress charts in later iterations look as fluctuative as in the first iterations.
- ScrumMaster Assigns Work - In planning, the scrum master assigns work, instead of the developers signing up.
- The Daily Scrum is For the ScrumMaster - Daily scrums feel like reporting sessions to the scrum master.
- Specialized Job Roles - A project team has highly specialized job roles ("architect", "tester" etc.)
