Retrospective Analysis

University of Southern California

Center for Systems and Software Engineering

Retrospective Analysis

Supannika KoolmanojwongOctober 21, 2013

1



Outline

• ARB Feedback• Retrospective Analysis• Workshop

2



Overview• Be consistent

– Terminologies: Client vs customer; volunteers vs students vs residents; project vs program

– Scope: Be clear on 577 scope & evolutionary scope (you need to architect for it)

• Spellcheck• Technical hiccup• Do not read from slides• Avoid unreadable diagrams• Did not post ARB slide on the team website = -2 points• Reference to previous year project – Be very careful

on that !!3



Strengths & Weaknesses

• Generally good

4



OCD

• Generally Good• Improvements

– Benefit Chain• Flow : chronological order; left to right• Goal can not be created by itself, need some

initiatives & contribution from stakeholder– Boundary diagram

• Bubbles = external entity to your project– LOS : Measurable, Testable

5



Goals can not be created by itself, need some initiatives & contribution from stakeholder

6



Where to start ??

• Chronological order• Left to right• Or top to bottom

7

USC developers

Maintainer

Living Advantage

Train staff and foster youth to use this system

Capture data daily and update

quarterly

Develop system

Partner with public agencies

Improved information

management process

Enable identification of foster youth

Easier access to benefits and

services

Saving time, space and cost.

Better track of foster youth

Provide Timely important data

Increase awareness of this

system

Effectively use of system

Provide broader services

Assumptions:

1.Foster youth want to have anytime/anywhere electronic access of their vital documents.

2.Public agencies are willing to use foster youth vital documents in association with Living Advantage.

Provide efficient Files and users Management

Faster processing and lower cost

Increase More participation of

agencies and foster youth

Provided Detailed data

processing

Public agencies

Manage every valid case of foster youth

Foster youth

Provide their vital records



8

Bubbles = external entity to your project



9

UNREADABLE

Break into several diagrams



Prototype

• Pick high risks & high value items• Manage flow of the story / scenario

10



Requirements

• Capability requirements– What the system can do

• LOS requirements– How well the system can do

11



Architecture

• Consistency with OC, Requirements, and Prototype

• Too detail in interface and Component diagrams

12



Low value-added; not necessary

13

Login

Logout



LCP

• Need a plan that your team member understand what to next and a plan that convince your client.

• Overestimate of the code size – Coordinate with prototype for more accurate

SLOC• For 577b – who are implementers, testers,

trainer• What to do with COCOMO Analysis?

– Look at Cost Estimation Lecture14



Software Engineering tasks ≠ Documentation

15



We have fixed schedule, so look at the effort (pessimistic)

Check more info in Cost Estimation lecture on how calculate 577 team size

16



FED• Change ROI to reflect on-going costs

(possibly savings)– Coordinate with your clients

• Update your risks• Distinguish one-time from annual costs in

business case• ROI: Benefits start in mid 2014• NDI comparison

– Compare similar product • Google map vs map quest; paypal vs Google wallet• NOT Google map vs iCalendar

17



Compare in order to pick the best product; so compare similar products

18



QM and CM

• Generally good– Doable strategy– Change control board – doable?

• Glad to see some CM strategy– e.g. file name convention

19



Outline

• ARB Feedback• Retrospective Analysis• Workshop

20



Retrospective meeting

• Not a time to point fingers or complain• inspect and adapt, and lead to continual

improvement• Retrospective ≠ Post-mortem

– Not after the project is done/dead– Quicker feedback loop– Not a blame and shame event

21



Retrospective meeting

• Generally– Think about what happened– What to celebrate /remember– What to improve

• Need– Open mind– Appreciation– A great facilitator

22http://agilepainrelief.com/notesfromatooluser/2010/05/agile-retrospectives.html

http://agilepainrelief.com/notesfromatooluser/2010/05/agile-retrospectives.html



Retrospective Analysis Techniques

• Good-Bad-Try• Mad/Sad/Glad• SAMOLO (Same As, More Of, Less Of)• Faces tool• Perfection Game• Describe the Sprint in One-word• Pillars Of Spiderweb Retrospective

23



Good-Bad-Try• Discuss among team members about the

following topics• Good

– Good things/activities/tools/practices that you like and want to continue

• Bad – Bad things/activities/tools/practices that you

don’t like and will not continue • Try

– Concepts/activities/tools/practices that you want to use in the next phase/sprint

24



Retrospective Analysis• Think about the previous iteration

– Smiley Face: What I liked...• Team coordination; progress of work

– Sad Face: What I didn't like.... • Mr.X needs to step up; client has not given me Z

– Light Bulb: What is now clear to me...• Finally, we have a full time !!

– Cloud: What is still cloudy.....• When are we going to get the server ?

25http://theagileschool.blogspot.com/

http://theagileschool.blogspot.com/



Agile Retrospective Board

26http://theagileschool.blogspot.com/

http://theagileschool.blogspot.com/



Daily Retrospective Board• Niko-niko Calendar

(or Smiley Calendar)• Puts a Smiley mark

onto a calendar after the day's work, before leaving the team room.

• member's mental health and motivation viewpoint

27http://drdobbs.com/architecture-and-design/201807863

http://drdobbs.com/architecture-and-design/201807863



Perfection Game

28http://agile.conscires.com/2012/04/09/different-ways-of-doing-sprint-retrospectives/

Each team member rates their previous sprint on a scale of 1 – 10, and explores what they could have done to make the sprint a perfect 10!

http://agile.conscires.com/2012/04/09/different-ways-of-doing-sprint-retrospectives/



Pillars Of Spiderweb Retrospective

29http://www.retrospectivewiki.org/index.php?title=Pillars_Of_Agile_Spiderweb_Retrospective

• Teams rated their abilities in each of the categories, scale of 1-5

• Display the different ratings on a spider graph

• Discuss the result

http://www.retrospectivewiki.org/index.php?title=Pillars_Of_Agile_Spiderweb_Retrospective



Workshop

• Sit with your team members• 20 minutes

– Game 1: Good-Bad-Try– Game 2: Describe the Sprint in One-word– Game 3: Pillars Of Spiderweb Retrospective

• Prepare for presentation (from the given paper)

30

Documents

Retrospective Analysis