It is mainly used in environments of product creation.

With SCRUM (literally "an ordered formation of players") we define a set of tasks that must be completed in a concrete time interval. The most common way is establishing which tasks are going to be done in a two-week-time period (Sprint) and materialize them in that time. If objectives could not be accomplished, it is necessary to analize what went wrong.

getting started

• communicate we are going to initiate working with it
• build prioritized backlog
• build Sprint backlog and start working
• set a date to start scrumming
• use burndown charts
• demo & review
• retro
• repeat!

Planning phase

Initial meeting of the sprint of maximum 4 hours duration. Product owner presents the top part of the backlog with the User Stories (objectives), explaining the reason of their importance. While the PO is explaining, dev team can make annotations for further questions. When this is done, different departments make a refinement meet and define tasks and time (or effort) estimation for achieving that goals. Once done, it is presented to the product owner who decides what User Stories accomplish that sprint based on the estimations and present them to Stakeholders.

User Stories must be unique and have a single objective not multiple.