Scrum
| Line 1: | Line 1: | ||
| + | Descriptions of Particular Methods | ||
| + | • Overview | ||
| + | – Application Context | ||
| + | • Type of decision | ||
| + | • Application context (project, program, portfolio; what type of industry; company size etc) | ||
| + | – Necessary data, information, people, resources to execute | ||
| + | – Summary of output | ||
| + | • Description of steps | ||
| + | – Summary of steps | ||
| + | – Description of steps (input, action, output) | ||
| + | • Application example | ||
| + | • Implementation advice | ||
| + | • Metrics | ||
| + | • Additional reading | ||
| + | • Work material (templates) | ||
Scrum is a development process [2] for dealing with [[Agile Project Management]] | Scrum is a development process [2] for dealing with [[Agile Project Management]] | ||
| Line 25: | Line 40: | ||
Meeting | Meeting | ||
| − | Daily scrum | + | Daily scrum [4] |
| + | Daily scrum is a meeting that is held everyday at the same time for everyday of the sprint. All team members participate, it as held at the same location everyday and should max last for 15 min. During the meeting three topics are discussed: | ||
| + | 1. | ||
| + | |||
Sprint goal | Sprint goal | ||
Sprints | Sprints | ||
| − | + | What does Done mean | |
Rules | Rules | ||
Artifacts | Artifacts | ||
| − | + | Product backlog | |
| + | stories | ||
- Sprint backlog | - Sprint backlog | ||
| − | + | Burndown chart [3] | |
| + | Sprint burndown chart release burndown chart | ||
When to use scrum | When to use scrum | ||
| Line 51: | Line 71: | ||
[1] http://www.techwell.com/2012/10/brief-history-scrum | [1] http://www.techwell.com/2012/10/brief-history-scrum | ||
[2] http://c2.com/cgi/wiki?ScrumProcess | [2] http://c2.com/cgi/wiki?ScrumProcess | ||
| + | [3] http://www.methodsandtools.com/archive/scrumburndown.php | ||
| + | [4] https://www.scrumalliance.org/community/articles/2009/november/daily-scrum-merely-a-status-report | ||
---- | ---- | ||
Revision as of 02:09, 25 November 2014
Descriptions of Particular Methods • Overview – Application Context • Type of decision • Application context (project, program, portfolio; what type of industry; company size etc) – Necessary data, information, people, resources to execute – Summary of output • Description of steps – Summary of steps – Description of steps (input, action, output) • Application example • Implementation advice • Metrics • Additional reading • Work material (templates)
Scrum is a development process [2] for dealing with Agile Project Management
Contents |
Background
History
The creator of The Scrum development process have been a frequent topic of debate, some say that is was created by Jeff Sutherland, John Scumniotales, and Jeff McKenna in 1993, others believe that Hirotaka Takeuchi and Ikujiro Nonaka invented Scrum in 1986. [1]
Overview of Scrum
What is Scrum?
What Scrum is not:
Framework -what scrum values
Challenges
Roles - Product Owner - Scrum development team - Scrum Master
Meeting Daily scrum [4] Daily scrum is a meeting that is held everyday at the same time for everyday of the sprint. All team members participate, it as held at the same location everyday and should max last for 15 min. During the meeting three topics are discussed: 1.
Sprint goal Sprints What does Done mean
Rules
Artifacts Product backlog stories - Sprint backlog Burndown chart [3] Sprint burndown chart release burndown chart
When to use scrum -what makes scrum work When not to use scrum -what makes scrum not work
Examples Reflections
See also
References
Further readings
Extrenal links
[1] http://www.techwell.com/2012/10/brief-history-scrum [2] http://c2.com/cgi/wiki?ScrumProcess [3] http://www.methodsandtools.com/archive/scrumburndown.php [4] https://www.scrumalliance.org/community/articles/2009/november/daily-scrum-merely-a-status-report
