1. University of Southern California Center for Systems and Software Engineering Retrospective Analysis Supannika Koolmanojwong October 21, 2013 1

2. University of Southern California Center for Systems and Software Engineering Outline ARB Feedback Retrospective Analysis Workshop 2

3. University of Southern California Center for Systems and Software Engineering 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

4. University of Southern California Center for Systems and Software Engineering Strengths & Weaknesses Generally good 4

5. University of Southern California Center for Systems and Software Engineering 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

6. University of Southern California Center for Systems and Software Engineering Goals can not be created by itself, need some initiatives & contribution from stakeholder 6

7. University of Southern California Center for Systems and Software Engineering Where to start ?? Chronological order Left to right Or top to bottom 7

8. University of Southern California Center for Systems and Software Engineering 8 Bubbles = external entity to your project

9. University of Southern California Center for Systems and Software Engineering 9

10. University of Southern California Center for Systems and Software Engineering Prototype Pick high risks & high value items Manage flow of the story / scenario 10

11. University of Southern California Center for Systems and Software Engineering Requirements Capability requirements –What the system can do LOS requirements –How well the system can do 11

12. University of Southern California Center for Systems and Software Engineering Architecture Consistency with OC, Requirements, and Prototype Too detail in interface and Component diagrams 12

13. University of Southern California Center for Systems and Software Engineering Low value-added; not necessary 13

14. University of Southern California Center for Systems and Software Engineering 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 Lecture 14

15. University of Southern California Center for Systems and Software Engineering Software Engineering tasks ≠ Documentation 15

16. University of Southern California Center for Systems and Software Engineering We have fixed schedule, so look at the effort (pessimistic) Check more info in Cost Estimation lecture on how calculate 577 team size 16

17. University of Southern California Center for Systems and Software Engineering 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

18. University of Southern California Center for Systems and Software Engineering Compare in order to pick the best product; so compare similar products 18

19. University of Southern California Center for Systems and Software Engineering QM and CM Generally good –Doable strategy –Change control board – doable? Glad to see some CM strategy –e.g. file name convention 19

20. University of Southern California Center for Systems and Software Engineering Outline ARB Feedback Retrospective Analysis Workshop 20

21. University of Southern California Center for Systems and Software Engineering 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

22. University of Southern California Center for Systems and Software Engineering Retrospective meeting Generally –Think about what happened –What to celebrate /remember –What to improve Need –Open mind –Appreciation –A great facilitator 22 http://agilepainrelief.com/notesfromatooluser/2010/05/agile-retrospectives.html

23. University of Southern California Center for Systems and Software Engineering 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

24. University of Southern California Center for Systems and Software Engineering 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

25. University of Southern California Center for Systems and Software Engineering 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 ? 25 http://theagileschool.blogspot.com/

26. University of Southern California Center for Systems and Software Engineering Agile Retrospective Board 26 http://theagileschool.blogspot.com/

27. University of Southern California Center for Systems and Software Engineering 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 27 http://drdobbs.com/architecture-and-design/201807863

28. University of Southern California Center for Systems and Software Engineering Perfection Game 28 http://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!

29. University of Southern California Center for Systems and Software Engineering Pillars Of Spiderweb Retrospective 29 http://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

30. University of Southern California Center for Systems and Software Engineering 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