1. Scrum Team
1.1. DevTeam
1.1.1. Self-organizing
1.1.2. Corss-functional
1.2. Scrum Master (SM)
1.2.1. Service to the DT
1.2.2. Service to the Organization
1.2.3. Service to the PO
1.3. Product Owner (PO)
1.3.1. Managing backlog
2. Artifacts
2.1. Product Backlog (PB)
2.1.1. an ordered list of everything that is known to be needed in the product
2.1.2. Responsible of PO
2.1.3. Description, estimation, value
2.2. Sprint Backlog (SB)
2.2.1. set of Product Backlog items selected for the Sprintplus a plan for delivering
2.3. Increment
2.3.1. Sum of all PB items completed during a Sprint and value of increment of previous Sprints
3. Pillars
3.1. Adaption
3.2. Transparency
3.3. Inspection
4. Quality
4.1. TDD
4.2. Early reviews
4.3. Coaching
4.4. Test automation
4.5. Ongoing refactoring
5. Events
5.1. Sprint
5.2. Sprint Planning
5.2.1. What can be done?
5.2.1.1. Product Backlog
5.2.1.2. Sprint Goal
5.2.2. How can be done?
5.2.2.1. Sprint Backlog
5.2.3. Who can join?
5.2.3.1. PO
5.2.3.2. DT
5.2.3.3. SM
5.2.3.4. someone to attend to provide technical or domain advise
5.2.4. 8 hours
5.3. Daily Scrum
5.3.1. What did i do yesterday?
5.3.2. What will i do today
5.3.3. Do i see any impediment?
5.3.4. 15 mins
5.3.5. Who can join?
5.3.5.1. DT
5.4. Sprint Review
5.4.1. What PB items have been done and not been done?
5.4.2. What problem occurred?
5.4.3. Demonstration of Done increment?
5.4.4. Revised PB
5.4.5. What to do next?
5.4.6. Review of marketplace and potential use
5.4.7. Review of timeline, budget, potential capabilities, and marketplace
5.4.8. 3 hours
5.4.9. Who can join?
5.4.9.1. Scrum team
5.4.9.2. Stakeholders collaborate
5.5. Sprint Retrospective
5.5.1. Inspect how the last Sprint went with regards to people, relationships, process, and tools;
5.5.2. Identify and order the major items that went well and potential improvements
5.5.3. Create a plan for implementing improvements to the way the Scrum Team does its work.
5.5.4. 4 hours
5.5.5. Who can join?
5.5.5.1. Scrum team