Scrum

Scrum-Guide.pdf

Scrum Reference Card

siehe local

Tutorial:

http://scrumtrainingseries.com/

http://www.xylus.de/blog/linksammlung-zu-m-thema-professional-scrum-master-vorbereitung/

http://blog.rainwebs.net/2010/10/10/important-scrum-videos/

Open Exam:

https://www.scrum.org/Assessments/Open-Assessments/Scrum-Open-Assessment

https://www.youtube.com/watch?v=eaTTy73MnEE

http://www.scrum-institute.org/Example_Scrum_Certification_Test_Questions.php

• ScrumMaster führt Liste der Hindernisse, die das Entwicklungsteam bei der Arbeit stören
• Liste wird im Daily Scrum besprochen
• enthält Priorisierung, Datum, Beschreibung
• ScrumMaster muss diese Hindernisse zügig beseitigen

• Tracks the remaining Product Backlog effort from one Sprint to the next
• x-axis die Sprints (1-n)
• Story Points for Y axis
• Depicts historical trends to adjust forecasts

ist die täglich aktualisierte visuelle Darstellung der Aufgaben, die das Team!während des 
aktuellen Sprints noch zu erledigen hat, und ist ebenfalls Eigentum des Teams

• shows burned Story Points not hours
• y-axis shows remaining Story Points, the x-axis shows days of the current Sprint
• the team updates the burn down chart on a daily basis
• Indicates total remaining team task hours within one Sprint
• Re-estimated daily, thus may go up before going down
• Intended to facilitate team self-organization
• Fancy variations, such as itemizing by point person or adding trend lines, tend to reduce effectiveness at encouraging collaboration
• Seemed like a good idea in the early days of Scrum, but in practice has often been misused as a management report, inviting intervention. The ScrumMaster should discontinue use of this chart if it becomes an impediment to team self-organization.  

Visualisierung Soll-Ist-Vergleich (per Kurve)

Story-Burndown-Chart: auf User Story bezogen

Sprint-Burndown-Chart: auf Tasks bezogen (nach Anzahl oder Aufwand)

• Specifies how to achieve the PBI’s what
• Requires one day or less of work
• Remaining effort is re-estimated daily, typically in hours
• During Sprint Execution, a point person may volunteer to be primarily responsible for a task
• Owned by the entire team; collaboration is expected

• priorisierte Übersicht über die in einem Sprint zu erledigenden Aufgaben / Tasks
• steht in Beziehung zu Items aus dem Product Backlog (i.d.R. 1 Item = n Tasks
• enthält eine Vorhersage der im Sprint abzuschließenden Arbeit, sowie einen Durchführungsplan
• Status wird durch das Team täglich aktualisiert
• Scrum Master kontrolliert Status und sorgt für die Einhaltung des Sprint Goals
• Taskboard: 4 Spalten: 1. Spalte User Stories, 2.-4. Spalte Tasks Offen / in Bearbeitung (WiP) / Erledigt (Done) (evtl. noch ToVerify) Markieren von nicht fertigen Tasks mit einem roten Punkt
• Consists of committed PBIs negotiated between the team and the Product Owner during the Sprint Planning Meeting
• Scope commitment is fixed during Sprint Execution
• Initial tasks are identified by the team during Sprint Planning Meeting
• Team will discover additional tasks needed to meet the fixed scope commitment during Sprint execution
• Visible to the team
• Referenced during the Daily Scrum Meeting
• Eigentum des Teams

• Specifies the what more than the how of a customer-centric feature
• Often written in User Story form
• Has a product-wide definition of done to prevent technical debt
• May have item-specific acceptance criteria
• Effort is estimated by the team, ideally in relative units (e.g., story points)
• Effort is roughly 2-3 people 2-3 days, or smaller for advanced teams
• hat einen "geschäftlichen Mehrwert"
• das Team muss einen Eintrag innerhalb eines Sprints erledigen können