Uploaded on

Agile Review and Retrospective

Agile Review and Retrospective

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. Retrospective &ReviewBy: Bachan Anand Dial-in Number: +17759963560 Room #: 699601 and press the # key.
  • 2. 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 Room #: 699601 and press the # key.
  • 3. Foundations of Scrum!   Empiricism !   Detailed up-front planning and defined processes are replaced by just-in-time Inspect and Adapt cycles!   Self-Organization !   Small teams manage their own workload and organize themselves around clear goals and constraints!   Prioritization !   Do the next right thing!   Rhythm !   Allows teams to avoid daily noise and focus on delivery!   Collaboration !   Leaders and customers work with the Team, rather than directing them http://agile.conscires.com/
  • 4. !   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 team / http://agile.conscires.com
  • 5. Scrum Overview
 Sprint Cycle
  • 6. Scrum Overview
 Role: 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/
  • 7. Scrum Overview
 Role: ScrumMaster!   Servant Leader!   Facilitates the Process!   Supports the Team!   Removes Organizational Impediments!   Socializes Scrum to Management!   Enable close collaboration across all roles and functions http://agile.conscires.com/
  • 8. Scrum Overview
 Role: Team!   Cross-Functional !   4-8 Members!   Self-Organizing!   Focused on Commitments http://agile.conscires.com/
  • 9. Why do sprintreviews? Dial-in Number: +17759963560Room #: 699601 and press the # key.
  • 10. Visibility Feedback CourseDiscussion Correction
  • 11. Who’s coming? Dial-in Number: +17759963560 Room #: 699601 and press the # key.
  • 12. Customers & Executives & Other Teams Business Stakeholders Partners
  • 13. What are they interested in seeing?
  • 14. Demos!…of stuff that’s done and potentially release-able. But first, set the context for your sprint
  • 15. The Sprint Review Deck
  • 16. First things first. The Team.
  • 17. What if my team didn’t finishanything this sprint?
  • 18. That’s ok. You still have a slot at the sprint review togive visibility to what the team has worked on thissprint.But, sorry, no demo.
  • 19. Keep the powerpoint stuff to a bare minimum please 5-10 minutes, tops.
  • 20. Demo Time
  • 21. Who’s doing the demo?
  • 22. QA Engineer UE Designer Developer Technical Writer BSAAny Team Member Product Owner ScrumMaster DBA Sys Admin Network Engineer
  • 23. How can I make my demo most effective?
  • 24. Set the stageReference your customerTell a story so they understand why this functionality / service / infrastructure is important
  • 25. Speak loudly Speak slowlyTell them what you are doing before you do it Don’t click as fast as you would using the product Dont use speed keys
  • 26. listen. listen. listen. &engage
  • 27. Practice your demo (at least once) Know your stuff – whatever it isSetup in advance and have all of your data available Remote desktop to another box for demo Stay on-time – respect your audience
  • 28. Storytelling is crucial.
  • 29. Now that the demos are over…show us your prioritized list of stories for the next sprint.
  • 30. Don’t be afraid
  • 31. And don’t forget…….. Inspect & Adapt
  • 32. Now let’s move intoRetrospective…
  • 33. 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”
  • 34. 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
  • 35. 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
  • 36. When to holdRetrospectives?
  • 37. 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
  • 38. Ensure it has a structure1.  Set the Stage2.  Gather Data3.  Generate Insights4.  Decide what to do5.  Close the Retrospective
  • 39. Set the Stage!   Define the ground rules –Will try not to interrupt each other –Will accept everyones opinion without judgment –Will talk from our own perspective, not from anyone elses –Will turn off our mobile phones!   goes through the agenda!   define the goals
  • 40. 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
  • 41. Generate Insights!   What were the patterns? !   Why were things the way they were?
  • 42. 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
  • 43. Closure!   End in positive way !   Appreciation !   Celebrate
  • 44. From the facilitator point of view...•  Preparation•  Leading the retrospective•  Closure•  Follow-up
  • 45. Preparation!   Place!   Participants!   Agenda/Goals!   Toolbox
  • 46. Conducting the retrospective!   Check in (warm-up) !   Collecting feedback !   Facilitation techniques !   Lead people, time, yourself
  • 47. 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
  • 48. Closure!   Always identify actions as outcomes of the retrospective
  • 49. 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
  • 50. Smells!   Reporting to management !   Offline retrospective (by email) !   Only a few participants !   Everybody is happy !   Blame game
  • 51. Smells!   Nobody talks about elephant !   Looking for silver bullets !   Retrospective in the team room !   Too short retrospective meeting !   Facilitator doesn’t facilitate
  • 52. Special thanks & Content Recognition!   Scott Greene at salesforce.com!   ADM – Adaptive Development Methodology
  • 53. http://agile.conscires.com/
  • 54. http://agile.conscires.com/
  • 55. http://agile.conscires.com/
  • 56. http://agile.conscires.com/
  • 57. http://agile.conscires.com/
  • 58. http://agile.conscires.com/
  • 59. http://agile.conscires.com/