Agile in Style               Course Material for CSM                           byGanesh Chandrasekaran, BE, SCJP, CWD, PMP...
How I started this?        இழபதறக எதவம் இலைல நமத ைகயிேல    ெபறவதறக உலகம் உணட தணியம் ெபொழதிேல     கலஙகி நினற நடநதெதனன ஒனறம்...
Topics to be coveredOverview of ScrumSprintsProduct BacklogThe TeamTracking ProgressMeetingsRelease Planning              ...
Overview of Scrum
Source: Online Sources
Agile where it started  “ The... ‘relay race’ approach to product  development...may conflict with the goals of  maximum s...
SCRUM PROCESS• Dr. Jeff Sutherland and Ken Schwaber  Inventors• Scrum as a formal process at OOPSLA  95.• OOPSLA (Object-O...
Rugby Game   Source: Online Sources
What is Agile/SCRUM?Scrum is an agile framework for completingcomplex projects. Scrum originally wasformalized for softwar...
1. A product owner creates/updates product   What is Agile/SCRUM?   backlog.Sprint planning, the team picks   top priority...
What is Agile/SCRUM?         Source: http://www.mitchlacey.com/resources/scrum-framework-flow-diagram
What is Agile/SCRUM?                       Source: Unknown
Sprint
A Sample Sprint       Mon   Tue   Wed   Thu     Fri    Mon   Tue    Wed        Thu          Fri                           ...
Sprint DonenessPotentially shippable productHigh QualityTestedCompleteTeam decides the DonenessWhat it does, it does very ...
Doneness Document         Date                                                     TaskFALS 31-Dec-12   All code is checke...
Architecture in AgileArchitecture is built over timeMore time on Architecture initiallyGradual decrease following sprintsU...
Sprint CommitmentThe team commits to stories.The business commits to leave prioritiesalone during the sprint.Sprint ends o...
Product Backlog
Story WritingAs a <user type>, I<want/need/can/etc.> some goal, [sothat <reason>].As a boy, I would like to grow up faster...
Acceptance CriteriaAdding test conditions for the story.   Can drive in all roads.   Can have music during ride.   Can go ...
Backlog GroomingReview the stories in backlogRe-prioritize due to changes in currentdemandsRemove unwanted storiesSplit ep...
Product Backlog      Source: Online Sources
Product Backlog      Source: Online Sources
The Team
Product Owner RARDefines the features of the productPrioritizes the product backlogMakes scope/schedule tradeoff decisions...
ScrumMaster RARHelps functional and productive teamClose co-operation with cross-functionalteamsAn expert in Scrum helps t...
ScrumMaster RARValues & practices of process & teamRemoves impediments from the teamChange agent for the organizationImpro...
Scrum Master    Source: Online Sources
The TeamMembers should be full-timeTeams are self-organizingTypically 5-9 peopleEgos & attitudes are put asideCommon goal ...
The TeamRather all of one thing at a timeDoes a little of everything all the timeDecide doneness as a teamLate to daily me...
The TeamSoftware Developers (UI/UX, Mid Tier, Back End)Technical Architect(s)QA Engineer(s)Business Analyst(s)ScrumMasterP...
THE TEAM
Real Life IncidentTae Kwon Do and Scrum are both about doing the right thing in a situation rather than masteringa list of...
5 tenets -Tae Kwon DoCourtesy - to help team membersIntegrity - Team being whole & undividedPerseverance - Sprint GoalSelf...
Sample Projects
Vacation Planning SiteShow creating a backlogShow how backlog is prioritizedExercise the Poker game for top 10storiesExerc...
Education WebSiteSite LoginStudents admissionCourses with videos and textQuestionnaire end of each 30 minutessessionExerci...
Online Mobile App SiteIntegrating Mobile AppsApps Ratings from usersTop 20 AppsExercise elaborating EpicsExercise Acceptan...
Meetings
Sprint PlanningWho:       Team, ScrumMaster & Product OwnerAgenda:       Discuss top priority product backlog items       ...
Sprint Planning contd.How full should a sprint be?   Unplanned time   Plannable time   Corporate overheadEstimate & Analyz...
Sprint Planning      Source: Online Sources
Sprint Planning      Source: Online Sources
Commitment DrivenPick high-priority story in backlogDecompose it into tasksEstimate each taskTeam members ask themselves: ...
Velocity DrivenNeeds 4-5 sprints velocity chartUse average or previous sprint velocityGrab user stories equal to that velo...
Story PointsA measure of relative size of featureBased on the total effort involvedKey is the relative size of numbersTeam...
Daily Scrum/Sync UpDaily sync choose a time & stick to it15-minutes and that’s the maximumNot for problem solvingWhole wor...
Daily Scrum/Sync UpWhat did you do yesterday?What will you do today?What, if anything, is in your way?Each team member max...
Daily Scrum/Sync Standup          Source: Online Sources
Scrum Task Board      Source: Online Sources
Scrum Task Board      Source: Online Sources
Sprint ReviewTeam presents the productDemo of new features or architecture2 hours prep guidelineWhole team participatesInv...
Sprint Review     Source: Online Sources
Sprint Review     Source: Online Sources
Sprint RetrospectiveWhat worked very well?What went wrong?How can we improve?Did we improve from last Sprint?30-60 minutes...
Sprint Retrospective        Source: Online Sources
Sprint Retrospective        Source: Online Sources
Tracking Progress
Tracking ProgressTask Boards with task current viewBurndown Charts   Release burndown chart   Sprint burndown chartVelocit...
Sample Charts
Release Planning
Release PlanningSprints to complete the total backlogUse team velocity and total story pointsHardening Sprint as neededRel...
Release Sprint                                         Release Sprint                                          UAT Sprint ...
Each of you can fly high
Succeeding with Agile    -Mike Cohn    -Mike Cohn
Succeeding with Agile        Change is not top-down or bottom-up.        The end state is unpredictable.        Scrum is p...
Q&A
Thank YouHope this has given an intuitive and informational session                      Best Regards           Ganesh Cha...
Upcoming SlideShare
Loading in …5
×

Agile in style ganesh c 12-26-12 ct buddies

1,014 views

Published on

Please find the slide deck used in the 12-31-12 presentation at Chandramohan home. Thanks for the feedback and happy reading.

Published in: Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,014
On SlideShare
0
From Embeds
0
Number of Embeds
12
Actions
Shares
0
Downloads
28
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Agile in style ganesh c 12-26-12 ct buddies

  1. 1. Agile in Style Course Material for CSM byGanesh Chandrasekaran, BE, SCJP, CWD, PMP,CGBL, CSM Certified ScrumMaster December 31, 2012
  2. 2. How I started this? இழபதறக எதவம் இலைல நமத ைகயிேல ெபறவதறக உலகம் உணட தணியம் ெபொழதிேல கலஙகி நினற நடநதெதனன ஒனறம் இலைலேய இைடவிடொத மயறசி எனறம் ெபொயததிலைலேய - Movie: Saatai / Lyrics: Yugabharathi Giving a person one fish and you feed him for a day.Teaching a person how to fish, then you feed him for a lifetime. - Chinese Proverb
  3. 3. Topics to be coveredOverview of ScrumSprintsProduct BacklogThe TeamTracking ProgressMeetingsRelease Planning Source: Ganesh Chandrasekaran
  4. 4. Overview of Scrum
  5. 5. Source: Online Sources
  6. 6. Agile where it started “ The... ‘relay race’ approach to product development...may conflict with the goals of maximum speed and flexibility. Instead a holistic or ‘rugby’ approach - where a team tries to go the distance as a unit, passing the ball back and forth-may better serve today’s competitive requirements.”Source: Hirotaka Takeuchi and Ikujiro Nonaka, “The New New Product Development Game,” Harvard Business Review, January 1986.
  7. 7. SCRUM PROCESS• Dr. Jeff Sutherland and Ken Schwaber Inventors• Scrum as a formal process at OOPSLA 95.• OOPSLA (Object-Oriented Programming , Systems, Languages & Applications) is an annual ACM research conference Source: Wikipedia
  8. 8. Rugby Game Source: Online Sources
  9. 9. What is Agile/SCRUM?Scrum is an agile framework for completingcomplex projects. Scrum originally wasformalized for software developmentprojects, but works well for any complex,innovative scope of work. The possibilitiesare endless. The Scrum framework isdeceptively simple. Source: http://www.scrumalliance.org/learn_about_scrum
  10. 10. 1. A product owner creates/updates product What is Agile/SCRUM? backlog.Sprint planning, the team picks top priority stories.2. Team creates a sprint backlog.The team works on a sprint, usually two to four weeks.3. Team meets every day to assess its progress.The ScrumMaster keeps the team focused on its goal.Sprint review to showcase the product.The sprint ends with a retrospective.Next sprint begins, Source: http://www.scrumalliance.org/learn_about_scrum with Step 1.
  11. 11. What is Agile/SCRUM? Source: http://www.mitchlacey.com/resources/scrum-framework-flow-diagram
  12. 12. What is Agile/SCRUM? Source: Unknown
  13. 13. Sprint
  14. 14. A Sample Sprint Mon Tue Wed Thu Fri Mon Tue Wed Thu Fri Review9am Review Daily Sync Meeting Sprint Sprint10am11am spective spective Retro- Retro-12pm1pm Sprint Planning Sprint Planning2pm grooming grooming Backlog Backlog3pm4pm5pm Source: Mountain Goat Software
  15. 15. Sprint DonenessPotentially shippable productHigh QualityTestedCompleteTeam decides the DonenessWhat it does, it does very wellShow sample Doneness document Source: Mountain Goat Software
  16. 16. Doneness Document Date TaskFALS 31-Dec-12 All code is checked in SVNETRUE 30-Dec-12 Performed code level checks as per code review checklistTRUE 30-Dec-12 Tested the component using multiple browsersTRUE 30-Dec-12 All known issues updated in the Product backlogTRUE 30-Dec-12 Test Caching of all componentsFALS 31-Dec-12 All error messages/warning appearing in the log file resolvedEFALS 31-Dec-12 All log instances are pointing to the correct logger with the appropriate log levelEFALS 31-Dec-12 Tested components with real dataETRUE 30-Dec-12 Performed boundary condition checks – null values, very long strings, empty values, negative values etcFALS 31-Dec-12 Code should be properly commentedEFALS 31-Dec-12 Design doc should be updated as per implementation changesEFALS 31-Dec-12 Change history in the code should be updatedETRUE 30-Dec-12 Presentation (HTML) code should be well-commented and indented as per Company standardsFALS 31-Dec-12 Designed & coded as per established standardsEFALS 31-Dec-12 Functional testing - all applicable use cases should be documented and testedETRUE 30-Dec-12 Automated testing - unit tests should be written, run and passing for all features - unit test coverage for a component should exceed 80% code coverage - only in rare cases where unit
  17. 17. Architecture in AgileArchitecture is built over timeMore time on Architecture initiallyGradual decrease following sprintsUser valued stories less initiallyGradual increase following sprints Source: Mountain Goat Software
  18. 18. Sprint CommitmentThe team commits to stories.The business commits to leave prioritiesalone during the sprint.Sprint ends on same day every time.Drop scope if needed, but don’t extend. Source: Mountain Goat Software
  19. 19. Product Backlog
  20. 20. Story WritingAs a <user type>, I<want/need/can/etc.> some goal, [sothat <reason>].As a boy, I would like to grow up faster,so that I can drive a fast car.Stories are written by anyone.Stories can be added anytime. Source: Mountain Goat Software
  21. 21. Acceptance CriteriaAdding test conditions for the story. Can drive in all roads. Can have music during ride. Can go 0-60mph in 3secs.Helps developer to code for needs.Helps tester to create test scripts.Test Driven Development to be followed. Source: Mountain Goat Software
  22. 22. Backlog GroomingReview the stories in backlogRe-prioritize due to changes in currentdemandsRemove unwanted storiesSplit epics to storiesProduct backlog healthy & up to date Source: Mountain Goat Software
  23. 23. Product Backlog Source: Online Sources
  24. 24. Product Backlog Source: Online Sources
  25. 25. The Team
  26. 26. Product Owner RARDefines the features of the productPrioritizes the product backlogMakes scope/schedule tradeoff decisionsResponsible for the profitability of the productAdjusts priorities as more is learnedAccepts or rejects work results Source: Mountain Goat Software
  27. 27. ScrumMaster RARHelps functional and productive teamClose co-operation with cross-functionalteamsAn expert in Scrum helps the team use itA leader - self-aware, listens, flattenshierarchy, helps colleagues improve,coaches doesn’t control, unleashes energyand intelligence of others. Source: Mountain Goat Software
  28. 28. ScrumMaster RARValues & practices of process & teamRemoves impediments from the teamChange agent for the organizationImproves productivity as possibleIf it’s legal and moral, do it Source: Mountain Goat Software
  29. 29. Scrum Master Source: Online Sources
  30. 30. The TeamMembers should be full-timeTeams are self-organizingTypically 5-9 peopleEgos & attitudes are put asideCommon goal is Sprint GOAL Source: Mountain Goat Software
  31. 31. The TeamRather all of one thing at a timeDoes a little of everything all the timeDecide doneness as a teamLate to daily meetings have a ruleRespond emails before leaving home Source: Mountain Goat Software
  32. 32. The TeamSoftware Developers (UI/UX, Mid Tier, Back End)Technical Architect(s)QA Engineer(s)Business Analyst(s)ScrumMasterProduct OwnerTechnical WriterProject Manager Source: Ganesh Chandrasekaran
  33. 33. THE TEAM
  34. 34. Real Life IncidentTae Kwon Do and Scrum are both about doing the right thing in a situation rather than masteringa list of rules Source: Ganesh Chandrasekaran
  35. 35. 5 tenets -Tae Kwon DoCourtesy - to help team membersIntegrity - Team being whole & undividedPerseverance - Sprint GoalSelf-Control - Team is self-organizedIndomitable Spirit - Keep the teammotivated for Sprint Success / TeamSuccess / Department Success Source: Ganesh Chandrasekaran
  36. 36. Sample Projects
  37. 37. Vacation Planning SiteShow creating a backlogShow how backlog is prioritizedExercise the Poker game for top 10storiesExercise commitment with story cardsExercise the Daily Scrum MeetingShow the artifacts displayed in demo Source: Ganesh Chandrasekaran
  38. 38. Education WebSiteSite LoginStudents admissionCourses with videos and textQuestionnaire end of each 30 minutessessionExercise compare and size the above 4Exercise what is more critical to work first Source: Ganesh Chandrasekaran
  39. 39. Online Mobile App SiteIntegrating Mobile AppsApps Ratings from usersTop 20 AppsExercise elaborating EpicsExercise Acceptance Criteria neededfor stories Source: Ganesh Chandrasekaran
  40. 40. Meetings
  41. 41. Sprint PlanningWho: Team, ScrumMaster & Product OwnerAgenda: Discuss top priority product backlog items Team selects which items to doWhy: Know what will be worked upon Discuss backlog items enough to do them Source: Mountain Goat Software
  42. 42. Sprint Planning contd.How full should a sprint be? Unplanned time Plannable time Corporate overheadEstimate & Analyze Tasks estimated 1-16 hours High-level design is considered Time boxed to 4 hours meeting time Source: Mountain Goat Software
  43. 43. Sprint Planning Source: Online Sources
  44. 44. Sprint Planning Source: Online Sources
  45. 45. Commitment DrivenPick high-priority story in backlogDecompose it into tasksEstimate each taskTeam members ask themselves: “Canwe commit to this?”If yes repeat with next story Source: Mountain Goat Software
  46. 46. Velocity DrivenNeeds 4-5 sprints velocity chartUse average or previous sprint velocityGrab user stories equal to that velocityPossibly stop there, but some team: Identify tasks for selected stories Some then estimate those tasks Source: Mountain Goat Software
  47. 47. Story PointsA measure of relative size of featureBased on the total effort involvedKey is the relative size of numbersTeam does best sizing in 2-3 sprints1,2,3,5,8,13,20,40,100Planning Poker once a month Source: Mountain Goat Software
  48. 48. Daily Scrum/Sync UpDaily sync choose a time & stick to it15-minutes and that’s the maximumNot for problem solvingWhole world is invited, only team talkTo reduce other meetings Source: Mountain Goat Software
  49. 49. Daily Scrum/Sync UpWhat did you do yesterday?What will you do today?What, if anything, is in your way?Each team member max 1-2 minsPrepare 5 mins previous day - 3Qs. Source: Mountain Goat Software
  50. 50. Daily Scrum/Sync Standup Source: Online Sources
  51. 51. Scrum Task Board Source: Online Sources
  52. 52. Scrum Task Board Source: Online Sources
  53. 53. Sprint ReviewTeam presents the productDemo of new features or architecture2 hours prep guidelineWhole team participatesInvite the world Source: Mountain Goat Software
  54. 54. Sprint Review Source: Online Sources
  55. 55. Sprint Review Source: Online Sources
  56. 56. Sprint RetrospectiveWhat worked very well?What went wrong?How can we improve?Did we improve from last Sprint?30-60 minutes maximumDone after every sprintScrumMaster, Product Owner & Team Source: Ganesh Chandrasekaran
  57. 57. Sprint Retrospective Source: Online Sources
  58. 58. Sprint Retrospective Source: Online Sources
  59. 59. Tracking Progress
  60. 60. Tracking ProgressTask Boards with task current viewBurndown Charts Release burndown chart Sprint burndown chartVelocity chartShow net progressPromote transparencyBad News is Good News (fail early than late) Source: Mountain Goat Software
  61. 61. Sample Charts
  62. 62. Release Planning
  63. 63. Release PlanningSprints to complete the total backlogUse team velocity and total story pointsHardening Sprint as neededRelease Sprint as neededMean Time Between Failure(MTBF) testStress, performance or usability testingCompliance testing, documentation touchups Source: Mountain Goat Software
  64. 64. Release Sprint Release Sprint UAT Sprint UAT Sprint IT Sprint IT SprintSample Release Plan Regular Sprint Regular Sprint Phase 1 Release Regular Sprint Regular Sprint Hardening Sprint Hardening Sprint Regular Sprint Regular Sprint Regular Sprint Regular Sprint Regular Sprint Regular Sprint Hardening Sprint Hardening Sprint Regular Sprint Regular Sprint Regular Sprint Regular Sprint Regular Sprint Regular Sprint
  65. 65. Each of you can fly high
  66. 66. Succeeding with Agile -Mike Cohn -Mike Cohn
  67. 67. Succeeding with Agile Change is not top-down or bottom-up. The end state is unpredictable. Scrum is pervasive. Scrum is dramatically different. Change is coming more quickly. Best practices are dangerous.Cohn, Mike (2009-10-20). Succeeding with Agile: Software Development Using Scrum (p. 5). Pearson Education (USA). Kindle Edition. Source: Mountain Goat Software
  68. 68. Q&A
  69. 69. Thank YouHope this has given an intuitive and informational session Best Regards Ganesh Chandrasekaran ScrumMaster at Apple Inc.

×