Scrum
| Line 1: | Line 1: | ||
Sorry not much to review :/ you probably won't have time to review it later (as in friday), but if you can then that would be appreciated. | Sorry not much to review :/ you probably won't have time to review it later (as in friday), but if you can then that would be appreciated. | ||
| − | + | ||
| − | + | Scrum is a framework [2] for dealing with [[Agile Project Management]] | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | Scrum is a | + | |
== Background == | == Background == | ||
===History=== | ===History=== | ||
| − | The creator of The Scrum development process have been a frequent topic of debate, | + | The creator of The Scrum development process have been a frequent topic of debate, but from the Scrum Parers [5] the start of Scum has been dedicated to the Godfathers; Hirotaka Takeuchi and Ikujiro Nonaka, they where the ones that came up with he name Scrum and came up with the initial concept in their paper [The New Product Development Game] in 1986 [1]. While Jeff Sutherland was the one to apply the concept and tweak it for then introducing it together with Ken Schwaber at the OOPSLA 1995 conference. |
| + | Scrum was later introduced by Schwaber and Mike Beedel in the book first book about Scrum: Agile Software Development with Scrum in 2001. From the Scrum Papers [5] it becomes clear that there have been many contributors in forming the Scrum framework. From the begining a Scrum community stated emerging, a platform to unite the community was created called with the name Scrum Alliance (SA) [6] and Certified ScrumMaster (CSM) certification. | ||
| + | While in 2013 Schwaber and Sutherland published The Scrum GuideTM | ||
== Overview of Scrum == | == Overview of Scrum == | ||
| Line 39: | Line 23: | ||
Roles | Roles | ||
| + | In Scrum three are three main roles that need to be implemented there needs to be a Product Owner, a Scrum development team and a Scum Master | ||
Product Owner | Product Owner | ||
Scrum development team | Scrum development team | ||
| Line 78: | Line 63: | ||
[3] http://www.methodsandtools.com/archive/scrumburndown.php | [3] http://www.methodsandtools.com/archive/scrumburndown.php | ||
[4] https://www.scrumalliance.org/community/articles/2009/november/daily-scrum-merely-a-status-report | [4] https://www.scrumalliance.org/community/articles/2009/november/daily-scrum-merely-a-status-report | ||
| + | [5] http://jeffsutherland.com/ScrumPapers.pdf | ||
| + | [6] https://www.scrumalliance.org | ||
---- | ---- | ||
| + | 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) | ||
| + | – Order of magnitude 3500 words | ||
| + | – What counts is „quality density“. If you can say it in 2000 words, say it in 2000 words. | ||
Revision as of 17:58, 25 November 2014
Sorry not much to review :/ you probably won't have time to review it later (as in friday), but if you can then that would be appreciated.
Scrum is a framework [2] for dealing with Agile Project Management
Contents |
Background
History
The creator of The Scrum development process have been a frequent topic of debate, but from the Scrum Parers [5] the start of Scum has been dedicated to the Godfathers; Hirotaka Takeuchi and Ikujiro Nonaka, they where the ones that came up with he name Scrum and came up with the initial concept in their paper [The New Product Development Game] in 1986 [1]. While Jeff Sutherland was the one to apply the concept and tweak it for then introducing it together with Ken Schwaber at the OOPSLA 1995 conference.
Scrum was later introduced by Schwaber and Mike Beedel in the book first book about Scrum: Agile Software Development with Scrum in 2001. From the Scrum Papers [5] it becomes clear that there have been many contributors in forming the Scrum framework. From the begining a Scrum community stated emerging, a platform to unite the community was created called with the name Scrum Alliance (SA) [6] and Certified ScrumMaster (CSM) certification.
While in 2013 Schwaber and Sutherland published The Scrum GuideTM
Overview of Scrum
What is Scrum?
What Scrum is not:
Framework what scrum values
Challenges
Roles In Scrum three are three main roles that need to be implemented there needs to be a Product Owner, a Scrum development team and a Scum Master Product Owner Scrum development team Scrum Master
Meeting Daily scrum [4]
Daily scrum is a meeting that is held 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 [5] http://jeffsutherland.com/ScrumPapers.pdf [6] https://www.scrumalliance.org
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) – Order of magnitude 3500 words – What counts is „quality density“. If you can say it in 2000 words, say it in 2000 words.
