1 / 30

Retrospective Analysis

Retrospective Analysis. Supannika Koolmanojwong October 21, 2013. Outline. ARB Feedback Retrospective Analysis Workshop. Overview. Be consistent Terminologies: Client vs customer; volunteers vs students vs residents; project vs program

odele
Download Presentation

Retrospective Analysis

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Retrospective Analysis Supannika Koolmanojwong October 21, 2013

  2. Outline • ARB Feedback • Retrospective Analysis • Workshop

  3. 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 !!

  4. Strengths & Weaknesses • Generally good

  5. 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

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

  7. Where to start ?? • Chronological order • Left to right • Or top to bottom

  8. Bubbles = external entity to your project

  9. UNREADABLE Break into several diagrams

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

  11. Requirements • Capability requirements • What the system can do • LOS requirements • How well the system can do

  12. Architecture • Consistency with OC, Requirements, and Prototype • Too detail in interface and Component diagrams

  13. Low value-added; not necessary Login Logout

  14. 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

  15. Software Engineering tasks ≠ Documentation

  16. We have fixed schedule, so look at the effort (pessimistic) Check more info in Cost Estimation lecture on how calculate 577 team size

  17. 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; paypalvs Google wallet • NOT Google map vsiCalendar

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

  19. QM and CM • Generally good • Doable strategy • Change control board – doable? • Glad to see some CM strategy • e.g. file name convention

  20. Outline • ARB Feedback • Retrospective Analysis • Workshop

  21. 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

  22. Retrospective meeting • Generally • Think about what happened • What to celebrate /remember • What to improve • Need • Open mind • Appreciation • A great facilitator http://agilepainrelief.com/notesfromatooluser/2010/05/agile-retrospectives.html

  23. 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 SpiderwebRetrospective

  24. 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

  25. 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 ? http://theagileschool.blogspot.com/

  26. Agile Retrospective Board http://theagileschool.blogspot.com/

  27. 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 http://drdobbs.com/architecture-and-design/201807863

  28. Perfection Game 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/

  29. Pillars Of 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

  30. 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)

More Related