1. Product backlog
1.1. Prioritised list
1.1.1. Described in User Stories
1.1.1.1. From writing to talking
1.1.1.2. Sub stories
1.1.1.2.1. Details in tests
1.1.1.2.2. Keep GUI out
1.1.1.3. User role modelling
1.1.1.3.1. Personas
1.1.1.3.2. Start with goals
1.1.1.4. INVEST
1.1.1.4.1. Independent
1.1.1.4.2. Negotiable
1.1.1.4.3. Valueable
1.1.1.4.4. Estimatable
1.1.1.4.5. Small
1.1.1.4.6. Testable
1.1.1.5. Slice the cake
1.1.2. High priority are detailed first
1.2. Only one list possible
1.3. Ever evolving
1.3.1. Product Roadmap
1.4. Holds everything that can be done
1.5. Business value added per item
1.6. Effort added per item
1.7. Refinement workshop
1.7.1. With Team 10% of time
1.7.2. Weekly
1.7.3. Requirement analysis
1.7.4. Splitting large into smaller items
1.7.5. (Re)estimating of new/existing items
2. Sprint
2.1. 1-4 Weeks
2.1.1. Sprint Planning Meeting
2.1.1.1. Part 1
2.1.1.1.1. Understand what PO wants
2.1.1.1.2. Review high prio items
2.1.1.1.3. Give team insight
2.1.1.1.4. Definition of "Done"
2.1.1.2. Part 2
2.1.1.2.1. How to implement items
2.1.1.2.2. Take top items from product backlog
2.1.1.2.3. Team decides how much they can do
2.1.1.2.4. 2-4 hours
2.1.1.2.5. Determine available teamhours for sprint
2.1.1.2.6. Decompose items into work/tasks
2.1.2. Start
2.1.2.1. Team commits to list
2.1.2.2. Release backlog
2.1.2.2.1. Release Burndown chart
2.1.2.3. Items do not change during sprint
2.1.2.4. Define Sprint Goal
2.1.3. Daily
2.1.3.1. Progress inspection
2.1.3.2. Take steps to complete work
2.1.3.3. Daily Scrum Meeting
2.1.3.3.1. 15 min
2.1.3.3.2. Standing
2.1.3.3.3. Synchronise work
2.1.3.3.4. Each teammember:
2.1.3.3.5. No discussions
2.1.3.3.6. No management attending
2.1.3.3.7. Estimate time to finish task
2.1.3.3.8. Sprint Burnout Chart
2.1.4. End
2.1.4.1. Software completely "done"
2.1.4.2. Sprint Review Meeting
2.1.4.2.1. Review/demo to stakeholders
2.1.4.2.2. Feedback for next sprint
2.1.4.2.3. Sprint retrospective
2.2. Timeboxed
2.2.1. Never extended
3. Roles
3.1. Product Owner
3.1.1. Maximising ROI
3.1.2. Identify features
3.1.3. Prioritise items on list
3.2. Scrum Master
3.2.1. Facilitator
3.3. The Team
3.3.1. 7±2 members
3.3.2. 100% available for sprint
3.3.3. Includes all expertise
3.3.3.1. No task assignment
3.3.3.2. Members take task
3.3.3.2.1. Support Pairing
3.3.4. Self-organising
3.3.4.1. Autonomy
3.3.4.2. Accountable
3.3.5. Should be stable
3.3.6. Have velocity
4. Arjen Douwes
4.1. Version 1.3
4.2. [email protected]
5. Scrumboard
5.1. Tasks
5.1.1. Not Yet Started
5.1.2. In progress
5.1.3. Done
5.2. Sprint Burnout Chart
5.2.1. Shows progress toward goal not hours spent
6. Waterfall
6.1. Build
6.2. Sequencial
6.2.1. Requirements/Functional documents
6.2.2. Test
6.3. Disadvantages
6.3.1. Good ideas must come in the beginning
6.3.2. Written docs have limitations in communication
6.3.3. No changes allowed
6.3.4. Planning almost impossible
6.3.5. No Fun
6.3.6. Sub optimised results
6.4. Complex problems
6.4.1. Behave unpredicable