Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

All sprints are guilty unless proven innocent - Deepak Chopra


Published on

AGILE GURUGRAM 2017 | Day 2 | Talk | 11.30 - 12.15

Published in: Education
  • Be the first to comment

  • Be the first to like this

All sprints are guilty unless proven innocent - Deepak Chopra

  2. 2. ALL SPRINTS ARE GUILTY UNLESS PROVEN INNOCENT Presented By: Deepak Chopra Vice President - GENPACT
  3. 3. Remember these… 12 commandments … highest priority is to satisfy the customer through early and continuous delivery of valuable software. ……Agile processes harness change for the customer's competitive advantage. Deliver working software frequently, ….preference to the shorter timescale. Business people and developers must work together daily throughout the project. AGILE GURUGRAM 2017 3 AGILE GURUGRAM 2017
  4. 4. Remember these… 12 commandments Build projects around motivated individuals .… trust them to get the job done.. Working software is the primary measure of progress. The most efficient and effective method … is face-to-face conversation. ….sponsors, developers, and users should be able to maintain a constant pace indefinitely.AGILE GURUGRAM 2017 4 AGILE GURUGRAM 2017
  5. 5. Remember these… 12 commandments Continuous attention to technical excellence …enhances agility Simplicity--the art of maximizing the amount of work not done--is essential.. …. emerge from self-organizing teams. At regular intervals, … and adjusts its behaviour accordingly. AGILE GURUGRAM 2017 5 AGILE GURUGRAM 2017
  6. 6. Reality is… AGILE GURUGRAM 2017 6 • How many of us follow ALL consistently in every Sprint.. • How many times we end up TAILORING due to.. • Pyramid Mix – cost built up • Geographically Distributed Teams • Attrition challenges • Lack of heroes… and many more • Customers often insist on CSM.. Do we have same ask for CPO? • We know no one is certifying on agile .. How do we judge “self judging” effectively AGILE GURUGRAM 2017
  7. 7. Judgment Day (Time) For Any Sprint AGILE GURUGRAM 2017 7 Sprint Review (Demo) Sprint Retrospective Product Process So how does one prove innocence ?? AGILE GURUGRAM 2017
  8. 8. Judgment : Sprint Review - Product AGILE GURUGRAM 2017 8 • Detail acceptance criteria in Sprint Backlog also.. for included User Stories and use for within-sprint testing before Sprint Review • Agree on Definition of DONE that includes ‘continuous testing’ and code promotion basis pre-defined steps - Less emphasis on volume but more on ‘workability’ - DevOps Focus on: “Valuable” – “Working Software” dimension Key Best Practices that help: Quality Control • Use MoSCoW prioritization in Product & Sprint Backlog - Sync both – drive ‘Valuable’ during Sprint Planning • Automate and incrementally build regression test case in each Sprint – include the same in Definition of DONE • Discuss ‘needs’ vs. ‘requirements’ during sprint planning and story writing workshop AGILE GURUGRAM 2017
  9. 9. Judgment : Sprint Retrospective- Process AGILE GURUGRAM 2017 9 • Define customized lifecycle model before SPRINT 0 and keep improving in each SPRINT – Boundaries of tailoring defined upfront • Have ‘PEER - SCRUM MASTER’ come in from time to time Focus on: “Re-Tuning” – “Tailoring” dimension Key Best Practices that help: Quality Assurance • Define software engineering practices within Definition of DONE – assurance is more effective than control • Use automated tools to maintain consistency in customized workflow – scrum ban boards, continuous integration • Embed Lean and Six Sigma thinking in team’s working – 5 wastes AGILE GURUGRAM 2017
  10. 10. Symptoms of truly ‘Guilty’ Sprints AGILE GURUGRAM 2017 10 over-burnt teams consistent sprint rejections velocity is not improving decisions are being taken by proxy processes are not changing too many meetings are happening and not finishing in time self managing but not self leading – need constant directions AGILE GURUGRAM 2017
  11. 11. Quick Tips & Tricks AGILE GURUGRAM 2017 11 • Establish organization suitable defined agile lifecycle model and comprehensive ‘Tailoring Guidelines’ for usage across projects • Don’t tailor just because you can… tailor because there is a need or constraint Don’t tailor SPRINTS so much that you are not able to take benefit of anything!! AGILE GURUGRAM 2017
  13. 13. Verdict AGILE GURUGRAM 2017 13 • When we retain focus on value generation than adoption … the chances of true business success through agile become higher All SPRINTS are guilty of not being true AGILE… but with right focus on key outcomes & inputs INNOCENCE can be proved!! Its hard to DO AGILE… ……but its even harder to BE AGILE Lets not worry if we are guilty of not being true agile or not … lets worry of not getting value generated by following ..whatever agile flavor we define AGILE GURUGRAM 2017
  14. 14. Email: Linkedin: