1

Mobile Apps: Review and

Retrospectives Refresher

Agile Transformation Team

2

Agenda

Agenda:• Review Roles –• Review Sprint Review and Retrospective

guidelines –

3

Scrum Flow- Overview

In following the ASDLC, the VA will utilize Scrum according to the PMAS within the Active State. At the Team level, effective Sprints as a part of Scrum start with collaborative Sprint Planning and end with a Review for acceptance and Retrospective for the team to reflect on their work.

Each event should be time boxed to accommodate people’s schedules and time

MS2

Scrum Master Role Sprint Review/ Retrospective

Scrum Master is facilitator for both ceremonies covers the following aspects:• Principles and rules of Scrum• Prepare and set an agenda for the meetings• Get the team to participate early and productively• As a Servant-Leader, foster the required environment and

support• Optimize the development processes and empower the

team to be self-organizing, autonomous, and collaborative• Keep the meeting on track, request for demos, approvals,

and information from the team

4

5

Product Owner in Sprint Review/ Retrospective

Product Owner (PO) is only required for the Sprint Review if the team is comfortable, they may participate in the Retrospective• Their main purpose is to accept/ reject the work

presented at the Sprint Review• PO may offer feedback and information about items

presented

6

Team Role in Sprint Review / Retrospective

Scrum Team presents their completed stories to POand Stakeholders during the Review• Present demonstrations and functionality of the completed

stories• Ask for Acceptance and/or comments from PO and Stakeholders• Confirms weather agreed “definition of done” has been met

Scrum Team celebrates and reflects on their completed work during the Retrospective• Discuss what they felt went well, lessons learned, and how

they can continue success and improved on lessons learned next time around• May also recommend improvements to the definition of

done based on experience

7

Sprint Review

Accept

Reject

Sprint

AMA Criteria: Meeting with the Product Owner and stakeholders to demonstrate which stories have been completed*Also often referred to as a Sprint Demo

• Can you answer these questions:– Are the appropriate people attending– Is the software being demonstrated– Are artifacts being used– Is there an accept/reject decision

8

Sprint Review (cont.)

Characteristics:• Held at the end of a sprint• Scrum Master Facilitates between presenter, user story, and

owner of the task • Team members take turns presenting what they accomplished

in the Sprint• Product Owner Accepts or Rejects done backlog items based

on predetermined acceptance criteria and “definition of done”• Stakeholders view work completed and provide feedback

Accept

Reject

Sprint

SprintReview

9

End of Sprint Review

Please choose one

Accept Reject

The demonstration of completed work during this Sprint is now over

Retrospective

Rules:

A communication forum held at the conclusion of each and every sprint in which Agile teams come together to celebrate team successes, to reflect on what can be improved, and to develop a plan that the team will use to apply lessons learned going forward. 1. This is a safe environment what

is discussed in the retrospective, stays there

2. Sprint Discussion Points:1. What went well?2. What could be improved

(lessons learned)?3. How to maintain what went

well?4. How to improve lessons

learned?

Sprint Retrospective Overview

10

11

Benefits of Retrospective

Benefits of a more disciplined Retrospective:• Timely feedback on what works and what doesn’t• Provides early and frequent feedback to adapt• Boost team morale with collaborative processes• Generate new ideas for improvements• Keep the focus on the identified goals of the sprint,

release, and project• Celebrate successes!

12

Focus ON / Focus OFF

Focus ON / Focus OFF

13

Suggested Retrospect Components:

•Set the Stage•Welcome• Agenda• Rules of the retrospective

• Insights into the Retrospective•What happened during the Sprint?•What worked well and what did not work

well? For example internal and external communication, development process, resources, and people. • Think Six Sigma and root cause analysis for both

what went well and what did not.

14

Retrospective Elements

• Identifying needed process improvements at end of every Sprint - ensures that the project team is always improving • The Retrospective is a collaborative process between all members

of the Team, VA PM, Requirements SME/ Product Owner (optional), and the Scrum Master• Team members identify what did and didn’t go well and what can

be improved upon• Scrum Master prioritizes actions and lessons learned based on

Team consensus• Team devises solutions to identified improvements - helps to build

team ownership, autonomy, and self-organization• Can use a round table format if people are not answering questions• Easy first celebrate to win is if all items of the sprint were accepted

15

Sprint Retrospective Deck – (template)

<Project Name>: <Sprint#>: <Date>

What went well in the Sprint? What could be improved (lessons learned)?

1. Person 1 – comment2. Person 2 – comment3. Person “n” - comment

1. Person 1 – comment2. Person 2 – comment3. Person “n” - comment

How to maintain what went well? How can we improve the lessons learned?

1. Person 1 – comment2. Person 2 – comment3. Person “n” - comment

1. Person 1 – comment2. Person 2 – comment3. Person “n” - comment

16

Do you have any question?