Sprint Retrospective

Finally, in Retrospective Meeting the team, scrum master and product owner discuss improvement in the overall process. The sprint retrospective a very important meeting and is mainly focused on how the team worked together during the sprint.

Meaningful retrospectives resolve project impediments, identify key issues, and create an environment of continuous improvement.

After 2-3 sprints, we held a Sprint Retrospective Meeting to look for ways to improve the next upcoming sprints. During the retrospective meeting, the entire scrum team, including the product owner and the scrum master come together to discuss three questions:

What went well?
What would we like to change?
How can we implement that change?

Sprint Review

A Sprint Review is an informal meeting held at the end of every Sprint to inspect the Increment and adapt the Product Backlog if needed. The sprint review is focused on the product increment created during the sprint.

It starts with a customer review and demonstration and ends with discussion and updates to the product backlog and release plan.

It is attended by the development team, the scrum master, the product owner and the stakeholders where the development team gives a demo on the sprint deliverable and determines what are finished and what aren’t.

It is mainly presented to the product owner for the approval and the review is given to team related to a feature in sprint review.

Daily scrum

Daily scrum meetings help keep the project on target as do regular inspections and reviews. Also know as Standup meetings attended by the Development Team and a Scrum Master.

It provides a simple means for team members to keep each other up to date without spending a lot of time in meetings or having to write and read piles of status reports.

It focus on quick discussion of progress, plans, and problems. The main purpose of the meeting is to let the members of the group quickly understand of:

  • What each person did yesterday
  • What they are going to do today
  • If there are any obstacle
  • If they need any assistance
  • It is daily event for the team to communicate more effectively and improve the productivity of the team.

Sprint Backlog

A Sprint Backlog is a list of the tasks and requirements to be completed within the sprint. Our Development team selects the top feature from the product backlog which they will deliver at the end of a sprint.

A short sprint allows us to release the working version of a product more frequently. After agreeing to do a particular feature, the feature is broken into a smaller task which is developed by product owner found in the sprint backlog.

The sprint backlog includes

  • The list of user stories within the sprint in order of priority.
  • The relative effort estimate for each user story.
  • The tasks necessary to develop each user story.
  • The effort, in hours, to complete each task.
  • At the task level, we estimate the number of hours ( also called Story Points) each task will take to complete.

Product Backlog

The Product Backlog is an ordered set of items that might be needed in the final product. In other words, it’s a kind of a wish list or a prioritised features list, containing short descriptions of all desired product functionality.

The Product Owner creates, maintains, and regularly re-orders the Product Backlog. He/ she describes it top items during the sprint planning meeting. He/she describes all items in a simple business language without technical specifications. The Product Owner uses the Product Backlog to adapt to emerging requirements, customer feedback, and market changes.