Review and Retrospective – Part 9
THE SPRINT REVIEW
The Sprint Review marks the end of a Sprint. During the sprint review the Scrum Team and the stakeholders review the progress made within the sprint. This is the time for everyone to see the hard work done by the scrum team as well as to collaborate on making the product better. This meeting is an inspect-and-adapt process for the product increment, and outputs from this meeting are considered for inclusion within Product Backlog.
Defining what “Done” is for the team
The Sprint Review is for showing what was “Done” during the Sprint. It is imperative for the Scrum Team to understand what “Done” means to them. The Definition of Done (DoD) lets the team focus on the standards to be met when working on features. Some examples of what can be included in the DoD would be:
- Code is peer-reviewed
- Documentation is updated
- Critical bugs and issues are fixed
- Error-free build
- Feature is tested on priority browsers and devices
- Configuration and build changes are documented
- QA is performed and completed
- Acceptance criteria are met
- Product Owner has given their sign-off
Acceptance criteria is a very important aspect of each user story. It details the minimum requirements to be met and is what the Product Owner looks for before accepting the deliverables as done. Acceptance criteria also helps the testers write their testing notes for the user stories, which developers can use for building and testing their code.
Coming up with the Definition of Done is a collaborative effort within the scrum team. Testers can contribute to this by suggesting the testing practices that should be done by everyone in the team.
59 Seconds Training Video
Master of Agile – Agile Scrum Developer With 59 Seconds Agile (Video Training Course)
Introductory Offer: Free Course
Master of Agile – Agile Scrum Developer With 59 Seconds Agile (Video Training Course)
What is this course?
This ‘Master of Agile – Agile Scrum Developer With 59 Seconds Agile (Video Training Course)’ provides an in-depth understanding of the Agile Scrum Developer roles and responsibilities
You will explore the Agile Scrum project life-cycle, including how an Agile User Story is created, to how we know when it is ‘done’
This course is aimed at those with or without prior knowledge and experience of the Agile values and principles
During this course you will learn the tools needed to succeed as an Agile Scrum Developer
What will you learn?
You will gain an in-depth understanding of the Agile Scrum Developer roles and responsibilities, and you will be able to
- Fully understand the role of the Agile Scrum Developer
- Understand the roles involved in an Agile project
- Create an effective Product Backlog
- Effectively participate in Scrum Meetings such as the Daily Stand-up, Sprint Review and Retrospective
- Identify the roles involves in the Scrum Team
What topics are covered within this course
You will cover the following topics during this course:
- An Introduction to Agile Project Management (Developer)
- The 12 Agile Principles (Developer)
- Introduction to Scrum (Developer)
- Scrum Project Roles (Developer)
- The Agile Project Life-cycle (Developer)
- Acceptance Criteria and the Prioritised Product Backlog (Developer)
- Initiating an Agile Project (Developer)
- Forming the Scrum Team (Developer)
- Epics and Personas (Developer)
- User Stories and Tasks (Developer)
- Implementation of Scrum (Developer)
- The Daily Scrum (Developer)
- The Product Backlog (Developer)
- Scrum Charts (Developer)
- Review and Retrospective (Developer)
- Validating a Sprint (Developer)
- Retrospective Sprint (Developer)
- Releasing the Product (Developer)
- The Communication Plan (Developer)
- Formal Business Sign-off (Developer)
Our Book Recommendations
We found these books great for finding out more information on Agile Scrum: