Scrum in a few lines

To understand scrum, you should know where it comes from. Best and shortest story is the agile manifesto:

• Individuals and interactions over processes and tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan

See also: http://scrumtrainingseries.com

Scrum is an implementation of agile, which has:

- Product Backlog

• List of INVEST Product Backlog Items (PBI) written and maintained by Product Owner
• INVEST:  Independent, Negotiable, Valuable, Estimable, Small, Testable
• PBI should idealy not take more than 2-3 days to develop.
• Do a Who/What/Why check for every PBI

- Backlog grooming -- 1 hour (team + owner + master)

• prioritize / clarify / split large and estimate (S/M/L/XL) PBIs 
• (next sprints) add / remove / reprioritize the backlog if necessary

- Sprint Plannung 1 -- 1 hour (team + owner)

• go through "READY" and prioritized PBIs (stories)
• commit to stories for the next sprint

- Sprint planning 2 -- 1 hour, right after sprint planning 1 (only team)

• discuss and design each story (interfaces, tables, architecture)
• Goal: the team has a clear understanding of the "how"
• Identify PBI tasks 
• The task board contains:

               - stories
               - tasks to do  (stories are broken down in tasks)
               - work in progress
               - done

 - Daily Scrum -- 15 min

• who does what (1-2 min) - team talks
• update the task board
• update impediments backlog
• don't discuss technical issues
• finally: tasks are DONE (tested, refactores, shippable)

- Sprint Review -- 90 min:

• moderator: product owner
• showing new functionality by team
• feedback from user

- Sprint Retrospective -- 90 min (team, no managers):

• what went well
• what needs to be improved
• use output for sprint planning 1 + 2 of next sprint