The sprint plan is created by all members of the Scrum team collaboratively. In this ceremony, all the prioritized user stories are taken and it is decided which ones to sprint based on the sprint objective and the team's capacity.
It defines what can be delivered in the Increment resulting from the Sprint that begins and how the necessary work will be done to deliver the Increment.
It is a daily meeting, of maximum 15 minutes, with all the members of the development team to discuss the progress that has been made towards the Sprint objective and plan the work for the next day.
Then each member answered the other team members These or similar questions: Have I kept the commitment I made yesterday? What commitment will I commit to today? Do I see any impediment to achieve it?
This is an informal meeting, not a follow-up. At the end of the Sprint, a Sprint review is carried out to inspect the Increment and adapt the Product List.
During the Sprint review, the team and stakeholders collaborate to determine the following things that could be done to optimize value. The entire Scrum Team attends and stakeholders are invited.
It is an opportunity for the Scrum team to inspect itself and create a plan for improvements that are addressed during the next Sprint.
The purpose of the Sprint Retrospective is Inspect how the last Sprint was in terms of people, relationships, processes and tools; Identify and order the most important elements that went well and the possible improvements and, Create a plan to implement improvements to the way the Scrum Team performs its work.
He Is the person who knows and understands the needs of users, knows the business totally, and is responsible for transmitting that understanding to the development team (or solution team).
It is made up of developers, who executed the complex work beyond the code. They carry out project activities to create and deliver a preview of the finished product in each sprint.
He is a leader who is at the service of the Scrum Team and the organization, helping them understand and live agility. He Know the status of the project, take care of events and that the team is multifunctional
It is an ordered list of everything that is known to be necessary in the product. It is the main source of requirements for any changes to be made to the product. The Product Owner is responsible for the Product List, including its content, availability and ordering. The Product List evolves as the product and the environment in which it will be used do as well. Constantly changing to identify what the product needs to be suitable, competitive and useful.
It is the sum of all the items on the Product List completed during the Sprint. Let's remember that Scrum is light and easy to understand, which is not so easy to stay aware of its essence and not fall into the common mistake of applying a series of practices just to apply them.
It is the set of items from the product list selected for the sprint, plus a plan to deliver the product increment and achieve the sprint objective. It makes visible all the work that the development team identifies as necessary to achieve the Sprint goal. To ensure continuous improvement, the sprint to do list includes at least one high priority process improvement identified in the immediately preceding Retrospective.