Agile Retrospective & review

Retrospective & ReviewBy: Bachan Anand

Dial-in Number: +17759963560 U.S. toll free: +18007414032 Room #: 699601 and press the # key.

What is Scrum

Scrum is an Agile framework that supports lightweight processes that emphasize:

Incremental deliveries

Quality of Product

Continuous improvement

Discovery of people’s potential

Scrum is not a methodology

Dial-in Number: +17759963560 U.S. toll free: +18007414032

Room #: 699601 and press the # key.

Foundations of ScrumEmpiricism

Detailed up-front planning and defined processes are replaced by just-in-time Inspect and Adapt cycles

Self-OrganizationSmall teams manage their own workload and organize themselves around clear goals and constraints

PrioritizationDo the next right thing

RhythmAllows teams to avoid daily noise and focus on delivery

CollaborationLeaders and customers work with the Team, rather than directing them http://agile.conscires.com/

Transparency

Everything about a project is visible to everyone

Commitment

Be willing to commit to a goal

Courage

Have the courage to commit, to act, to be open and to expect respect

Focus

Focus all of your efforts and skills on doing the work that you have committed to doing

Respect

Respect and trust the different people who comprise a teamhttp://agile.conscires.com/

Scrum OverviewSprint Cycle

Scrum OverviewRole: Product Owner

Thought Leader and Visionary

Drives the Product Vision

Prioritizes the Goals - User Stories

Maintains the Product Backlog with the team

Accepts the Working Product (on behalf of the customer)

http://agile.conscires.com/

Scrum OverviewRole: ScrumMaster

Servant Leader

Facilitates the Process

Supports the Team

Removes Organizational Impediments

Socializes Scrum to Management

Enable close collaboration across all roles and functions


Scrum OverviewRole: Team

Cross-Functional

4-8 Members

Self-Organizing

Focused on Commitments


Why do sprint reviews?


Visibility Feedback

DiscussionCourse

Correction

Who’s coming?


Executives & Stakeholders

Other Teams

Customers & Business

Partners

What are they interested in seeing?

Demos! …of stuff that’s done and potentially release-able.

But first, set the context for your sprint

The Sprint Review Deck

First things first.

The Team.

What if my team didn’t finish

anything this sprint?

That’s ok. You still have a slot at the sprint review to give visibility to what the team has worked on this sprint.

But, sorry, no demo.

Keep the powerpoint stuff to a bare minimum please

5-10 minutes, tops.

Demo Time

Who’s doing the demo?

Product Owner

QA Engineer

ScrumMaster

Sys Admin

Network Engineer

DBA

UE Designer

Technical Writer

Any Team Member

Developer

BSA

How can I make my demo most effective?

Set the stage

Reference your customer

Tell a story so they understand why this functionality / service / infrastructure is important

Speak loudly

Speak slowly

Tell them what you are doing before you do it

Don’t click as fast as you would using the product

Don't use speed keys

listen.listen.listen.

&engage

Practice your demo (at least once)

Know your stuff – whatever it is

Setup in advance and have all of

your data available

Remote desktop to another box for

demo

Stay on-time – respect your

audience

Storytelling is crucial.

Now that the demos are over…

show us your prioritized list of stories for the next sprint.

Don’t be afraid

Inspect & Adapt

And don’t forget……..

Now let’s move into Retrospective…

What is a Retrospective?

• “A meeting held at the end of a Sprint to learn from the experience and to changes for the next Sprint”

Why Retrospective?

Retrospectives provide: Feedback to the “development process” An opportunity to talk about difficult issues that are impeding

team performance A chance to record what is working/not working that can possibly be shared with others Good team building An insight into potential team problems that can be acted on

Prime directive

“Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand”

Norman Kerth

When to hold Retrospectives?

Who is in the retrospective?

For all team members

Everyone is equal

Facilitated by Scrum Master

Product Owner is not necessary

Management should not attend

Ensure it has a structure

1. Set the Stage

2. Gather Data

3. Generate Insights

4. Decide what to do

5. Close the Retrospective

Set the Stage

Define the ground rules

–Will try not to interrupt each other –Will accept everyone's opinion without

judgment –Will talk from our own perspective, not

from anyone else's –Will turn off our mobile phones

goes through the agenda

define the goals

Gather Data

• Things that happened and how we responded

• People see things very differently

• Key events timeline• What did we commit to delivering?• Stories delivered• Test cases passed• Defects raised

Generate Insights

What were the patterns?

Why were things the way they were?

Decide what to do

• What do we want to do in our next iteration to meet our goal?

• Be realistic

• Pick no more than 3 things

• Use Dot voting• Sprint plan• Implementation backlog

Closure

End in positive way

Appreciation

Celebrate

From the facilitator point of view...

• Preparation

• Leading the retrospective

• Closure

• Follow-up

Preparation

Place

Participants

Agenda/Goals

Toolbox

Conducting the retrospective

Check in (warm-up)

Collecting feedback

Facilitation techniques

Lead people, time, yourself

Leading the retrospective

Time Start and finish on time Timebox activities Have breaks

People Personalities (quiet, overbeating, passive, aggressive)Introverts vs. extroverts

You Facilitator vs. team member Let others talk

Closure

Always identify actions as outcomes of the retrospective

Follow up

Share retrospective results

Make comments and actions visible

Add user stories, tasks to sprint/product backlog

Check the status regularly

Review on next retrospective

Smells

Reporting to management

Offline retrospective (by email)

Only a few participants

Everybody is happy

Blame game

Smells

Nobody talks about elephant

Looking for silver bullets

Retrospective in the team room

Too short retrospective meeting

Facilitator doesn’t facilitate

Special thanks & Content Recognition

Scott Greene at salesforce.com

ADM – Adaptive Development Methodology

How do you learn Scrum – By How do you learn Scrum – By Doing?Doing?

Apply few practices at a Apply few practices at a timetime

Understand the values Understand the values and foundationsand foundations

Inspect and AdaptInspect and AdaptExperience the Joy of Experience the Joy of

Doing ScrumDoing Scrumhttp://agile.conscires.com/

How do you learn Scrum ? How do you learn Scrum ? Experiential Training Experiential Training


Pay-it-forward / Pay-it-forward / Donation only trainingsDonation only trainings

1 day Agile & Scrum Training1 day Agile & Scrum Training

- August 12th – IrvineAugust 12th – Irvine

- August 26th – SFO & AtlantaAugust 26th – SFO & Atlanta

- Sep 30th – Boston & San DiegoSep 30th – Boston & San Diego

- Oct 20th - PhoenixOct 20th - Phoenix

- October 21st - DenverOctober 21st - Denver

- Nov 4th - SeattleNov 4th - Seattle

- Nov 7th - PortlandNov 7th - Portlandhttp://agile.conscires.com/

User groups User groups /Communities/Communities

APLN – Agile Project Leadership NetworkAPLN – Agile Project Leadership Network

Scrum Alliance – Scrum User GroupsScrum Alliance – Scrum User Groups

Online User GroupsOnline User GroupsScrum AllianceScrum Alliance


Scrum Certifications Scrum Certifications


Q & AQ & A


Donation only 1 day TrainingsDonation only 1 day Trainings Irvine ( Bachan Anand)– August 12Irvine ( Bachan Anand)– August 12thth

http://agile.conscires.com/1-day-agile-scrum-training-http://agile.conscires.com/1-day-agile-scrum-training-irvine-07/irvine-07/

SFO ( Tobias Mayer)– August 26SFO ( Tobias Mayer)– August 26th th

http://agile.conscires.com/1-day-agile-scrum-training-http://agile.conscires.com/1-day-agile-scrum-training-sfo-01/sfo-01/

Atlanta ( Manoj Vadakan)– August 26Atlanta ( Manoj Vadakan)– August 26th th

http://agile.conscires.com/1-day-agile-scrum-training-http://agile.conscires.com/1-day-agile-scrum-training-atlanta-01/atlanta-01/

Boston ( Manoj Vadakan) – September 30th Boston ( Manoj Vadakan) – September 30th http://agile.conscires.com/1-day-agile-scrum-training-http://agile.conscires.com/1-day-agile-scrum-training-

boston-04/boston-04/ San Diego (Bachan Anand ) – Sep 30th San Diego (Bachan Anand ) – Sep 30th

http://agile.conscires.com/scrum-1-day-training-http://agile.conscires.com/scrum-1-day-training-sandiego-02/sandiego-02/ http://agile.conscires.com/

Thank you !Thank you !

More Resources atMore Resources at http://agile.conscires.com/suggested-http://agile.conscires.com/suggested-

reading-list-and-resources/reading-list-and-resources/

Contact InfoContact InfoBachan AnandBachan Anand

[email protected]@conscires.com

949-232-8900949-232-8900

http://www.linkedin.com/in/bachanhttp://www.linkedin.com/in/bachan


Agile Retrospective & review

Business

Transcript of Agile Retrospective & review