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.
Agile Induction -Priyank [email_address]
<ul><li>Most of material in this presentation has been </li></ul><ul><li>inspired (please read as “reused”) from a number ...
Objective <ul><li>Overview to Agile </li></ul><ul><ul><li>Manifesto of Agile  </li></ul></ul><ul><ul><li>Agile Values and ...
SDLC Process
I Overview to Agile
Manifesto for Agile © Agile Alliance  http://agilemanifesto.org
Agile Principles © Agile Alliance  http://agilemanifesto.org
Agile Principles    cont.. © Agile Alliance  http://agilemanifesto.org
Agile Methodology  © & Reference http://blog.klover.se/
II Overview to Scrum
Typical Scrum Lifecycle ©  Scot Amber  http://www.ambysoft.com/essays/agileLifecycle.html
Sprint activities & roles Release n User Stories Sprint 1, 2, ..n Update product Backlog Sprint Planning Meeting > Daily S...
Scrum Size: Scrum team is of 8-10 team members while few of the team cab be small in size and have only 3-4 team members
Scrum Team
Extended Release Team Note essential to have a separate Release team as Scrum can integrate
Overall picture  <ul><li>Roles </li></ul><ul><li>Practices  </li></ul><ul><li>Product Owner </li></ul><ul><li>Scrum Master...
Roles <ul><li>Product Owner </li></ul><ul><li>Scrum Master </li></ul><ul><li>Owns Product Backlog </li></ul><ul><li>Define...
Roles cont.. <ul><li>Scrum Team </li></ul><ul><li>Stakeholders  </li></ul><ul><li>Self organized team  </li></ul><ul><li>C...
III Scrum Practices
Scrum Practices we will look at  <ul><li>User Story  </li></ul><ul><li>Sprint Planning  </li></ul><ul><li>Estimation/Plann...
User Story <ul><li>User Story is the basic unit of scope in an Agile Project. It describes the who, what, why of a require...
Estimation <ul><li>Product Estimation/ Roadmap </li></ul><ul><li>Release Estimation  </li></ul><ul><li>Sprint Estimation  ...
Sprint Planning <ul><li>4-6 hours (max) for team to select Product Backlog and set Sprint Goal with Product Owner </li></u...
Planning Poker  <ul><li>Individual stories are presented for estimation. After a period of discussion, each participant ch...
Planning Poker  cont Clarity ? Tester Coder UI Dev Tester Coder Coder 4 8 3 2 4 1 User Story Planning Poker Outliers  Disc...
Daily Stand-Up  <ul><li>Held daily </li></ul><ul><li>15- Minutes (no longer, otherwise it’s not a daily stand up) </li></u...
Development <ul><li>Developer picks & owns the high priority stories from sprint backlog. </li></ul><ul><li>Elucidates/Cla...
Testing During an Iteration  After an Iteration   In  Integration , System Test  & UAT Bug Tracking  Test @ Sprint Test @ ...
Sprint Demo or Review <ul><li>Show for stakeholder about what we did in the current sprint ? </li></ul><ul><li>Team prepar...
Retrospective  <ul><li>During the sprint retro/review the project is assessed against the sprint goal determined during th...
Release  <ul><li>Schedule Go Live  </li></ul><ul><li>Regression Test, Pre Integration Test, Code Freeze Test. </li></ul><u...
IV Metrics, Meetings and Reporting
Burn-Down <ul><li>Burn-down Chart shows the estimated number of hours required to complete the tasks of the Sprint. </li><...
Velocity <ul><li>Velocity is a measure of how much Product Backlog (Sum of Story Points) the team can complete in a given ...
Scrum of Scrum <ul><li>Scrum for managing multiple Scrums  </li></ul><ul><li>10 -20 Minute Meeting  </li></ul><ul><li>Mult...
Weekly Sync <ul><li>Sync is a weekly activity.  </li></ul><ul><li>Each Team presents its progress to Stakeholders based on...
Question ? Retrospective
<ul><li>Contact </li></ul><ul><li>Priyank  </li></ul><ul><li>Phone: +91-8108894236 </li></ul><ul><li>Email & Chat </li></u...
Upcoming SlideShare
Loading in …5
×

Agile scrum induction

3,003 views

Published on

Agile & Scrum Basics for Inducting a new team

Published in: Technology, Business
  • Get Paid For Your Opinions! Earn $5-$10 cash on your first survey. ■■■ http://ishbv.com/goldops777/pdf
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • ★★ How Long Does She Want You to Last? ★★ A recent study proved that the average man lasts just 2-5 minutes in bed (during intercourse). The study also showed that many women need at least 7-10 minutes of intercourse to reach "The Big O" - and, worse still... 30% of women never get there during intercourse. Clearly, most men are NOT fulfilling there women's needs in bed. Now, as I've said many times - how long you can last is no guarantee of being a GREAT LOVER. But, not being able to last 20, 30 minutes or more, is definitely a sign that you're not going to "set your woman's world on fire" between the sheets. Question is: "What can you do to last longer?" Well, one of the best recommendations I can give you today is to read THIS report. In it, you'll discover a detailed guide to an Ancient Taoist Thrusting Technique that can help any man to last much longer in bed. I can vouch 100% for the technique because my husband has been using it for years :) Here's the link to the report ◆◆◆ http://ishbv.com/rockhardx/pdf
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Agile scrum induction

  1. 1. Agile Induction -Priyank [email_address]
  2. 2. <ul><li>Most of material in this presentation has been </li></ul><ul><li>inspired (please read as “reused”) from a number of sources, </li></ul><ul><li>I take it as </li></ul><ul><li>“ Don’t reinvent the wheel” </li></ul><ul><li>and </li></ul><ul><li>“ Spreading the good words around” </li></ul>
  3. 3. Objective <ul><li>Overview to Agile </li></ul><ul><ul><li>Manifesto of Agile </li></ul></ul><ul><ul><li>Agile Values and Principles </li></ul></ul><ul><li>Overview to Scrum </li></ul><ul><ul><li>Scrum Basics </li></ul></ul><ul><ul><li>Scrum Roles & Responsibility </li></ul></ul><ul><li>Scrum Practices </li></ul><ul><ul><li>User Story, Backlog, Test, Develop </li></ul></ul><ul><ul><li>Planning, Estimation, Standup Demo, Retro </li></ul></ul><ul><li>Metrics </li></ul><ul><li>Meetings and Reporting </li></ul>
  4. 4. SDLC Process
  5. 5. I Overview to Agile
  6. 6. Manifesto for Agile © Agile Alliance http://agilemanifesto.org
  7. 7. Agile Principles © Agile Alliance http://agilemanifesto.org
  8. 8. Agile Principles cont.. © Agile Alliance http://agilemanifesto.org
  9. 9. Agile Methodology © & Reference http://blog.klover.se/
  10. 10. II Overview to Scrum
  11. 11. Typical Scrum Lifecycle © Scot Amber http://www.ambysoft.com/essays/agileLifecycle.html
  12. 12. Sprint activities & roles Release n User Stories Sprint 1, 2, ..n Update product Backlog Sprint Planning Meeting > Daily Scrum > Daily Work Product Backlog Product Backlog Burndown Sprint Backlog Sprint Burn down Impediments list Sprint Retrospective Sprint Review Product Increment Sprint Cycle > Daily Cycle > Product Owner Scrum Master Stakeholders Scrum Team End Users © Scot Amber http://www.ambysoft.com/essays/agileLifecycle.html
  13. 13. Scrum Size: Scrum team is of 8-10 team members while few of the team cab be small in size and have only 3-4 team members
  14. 14. Scrum Team
  15. 15. Extended Release Team Note essential to have a separate Release team as Scrum can integrate
  16. 16. Overall picture <ul><li>Roles </li></ul><ul><li>Practices </li></ul><ul><li>Product Owner </li></ul><ul><li>Scrum Master </li></ul><ul><li>Stakeholders </li></ul><ul><ul><li>Customer </li></ul></ul><ul><ul><li>End customer </li></ul></ul><ul><ul><li>Managers </li></ul></ul><ul><li>Scrum Team </li></ul><ul><ul><li>Developer </li></ul></ul><ul><ul><li>Tester </li></ul></ul><ul><ul><li>Business Analyst (occasionally) </li></ul></ul><ul><ul><li>System Integrator </li></ul></ul><ul><ul><li>User Interface Developer </li></ul></ul><ul><li>Mentor or Coach </li></ul><ul><li>Engineering </li></ul><ul><ul><li>TDD, Refactoring, Pair programming </li></ul></ul><ul><ul><li>Release </li></ul></ul><ul><ul><ul><li>Done </li></ul></ul></ul><ul><ul><li>Iterative Development </li></ul></ul><ul><ul><li>Automated testing </li></ul></ul><ul><ul><li>Continues Integration </li></ul></ul><ul><li>Environment and Behavior </li></ul><ul><ul><li>Thinking </li></ul></ul><ul><ul><li>Collaboration </li></ul></ul><ul><ul><li>Self organization </li></ul></ul><ul><li>Project Management </li></ul><ul><ul><li>Planning, Estimation by Poker </li></ul></ul><ul><ul><li>Stand-up, Burn down, Velocity, Retrospective, Demo </li></ul></ul>
  17. 17. Roles <ul><li>Product Owner </li></ul><ul><li>Scrum Master </li></ul><ul><li>Owns Product Backlog </li></ul><ul><li>Defines Features </li></ul><ul><li>Prioritizes Requirement </li></ul><ul><li>Details requirement related questions </li></ul><ul><li>Accept or Reject work product </li></ul><ul><li>ROI </li></ul><ul><li>Release Planning </li></ul><ul><li>Communication with Stakeholders </li></ul><ul><li>Helps the team achieve success using Scrum </li></ul><ul><li>Serving the team </li></ul><ul><ul><li>Facilitate the team’s group interactions to help the team achieve its full potential </li></ul></ul><ul><ul><li>Helps to remove blocks that are surfaced by team members </li></ul></ul><ul><li>Protecting the team </li></ul><ul><ul><li>Protects the team from outside interference or disruption </li></ul></ul><ul><ul><li>Raise uncomfortable issues within the team </li></ul></ul><ul><li>Supporting the team’s use of Scrum </li></ul><ul><ul><li>Organizes and facilitates Scrum-related practices </li></ul></ul><ul><ul><li>Scrum “conscience” of the team over standard Scrum practices </li></ul></ul>
  18. 18. Roles cont.. <ul><li>Scrum Team </li></ul><ul><li>Stakeholders </li></ul><ul><li>Self organized team </li></ul><ul><li>Cross Functional </li></ul><ul><li>Share Commitment </li></ul><ul><li>Possesses all the skills necessary to produce an increment of potentially shippable product </li></ul><ul><li>Requirements </li></ul><ul><li>Reviews </li></ul><ul><li>Feedback </li></ul><ul><li>Approvals </li></ul>
  19. 19. III Scrum Practices
  20. 20. Scrum Practices we will look at <ul><li>User Story </li></ul><ul><li>Sprint Planning </li></ul><ul><li>Estimation/Planning Poker </li></ul><ul><li>Product/Sprint Backlog </li></ul><ul><li>Development /Code </li></ul><ul><li>Testing </li></ul><ul><li>Release </li></ul><ul><li>Demo/Review </li></ul><ul><li>Retrospective </li></ul><ul><li>Burn-down </li></ul><ul><li>Velocity </li></ul><ul><li>Scrum of Scrum </li></ul>
  21. 21. User Story <ul><li>User Story is the basic unit of scope in an Agile Project. It describes the who, what, why of a requirement. </li></ul><ul><li>Epics -Epics are large user stories , typically ones which are too big to implement in a single iteration and therefore they need to be disaggregated into smaller user stories at some point </li></ul><ul><li>Themes- A theme is a collection of related user stories .  Themes are often used to organize stories into releases or to organize them so that various sub teams can work on them. </li></ul><ul><li>Feature - Initial User Stories (Formal) in our DevFactoy release is planned by feature. </li></ul>“ User stories are very slim and high-level requirements artifacts” <ul><ul><li>A good example for writing user story is - </li></ul></ul><ul><ul><ul><ul><ul><li>As a <<User>> </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>I want to <<Goal>> </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>So that <<Value>>s </li></ul></ul></ul></ul></ul>User –a user of product Goal –feature user needs to increase value of Product Value –why feature is important
  22. 22. Estimation <ul><li>Product Estimation/ Roadmap </li></ul><ul><li>Release Estimation </li></ul><ul><li>Sprint Estimation </li></ul>Sprint 1 Sprint 5 Sprint 2 Sprint 3 Sprint 4 1 3 5 Planning Poker Release
  23. 23. Sprint Planning <ul><li>4-6 hours (max) for team to select Product Backlog and set Sprint Goal with Product Owner </li></ul><ul><li>Attended by Product Owner, Scrum team, customers, management in order to define what to build in the next Sprint </li></ul><ul><li>Team selects as much Product Backlog as it believes it can develop during the next Sprint. </li></ul><ul><li>Product Owner and customer devise Sprint Goal (which is the business value that the product increment must deliver regardless of functionality implemented). </li></ul><ul><li>4 hours (max) for team to define Sprint Backlog </li></ul><ul><li>Attended by Product Owner, Scrum team, development management in order to define how to build the product functionality into a product increment in the next Sprint. </li></ul><ul><li>Team defines Sprint Backlog, consisting of all tasks that need to be completed during Sprint. </li></ul><ul><li>Team members sign up for work and estimate their tasks. </li></ul><ul><li>Tasks are 1-16 hours long (XP suggests 1-3 days); if longer, break them down into more granularity. </li></ul>
  24. 24. Planning Poker <ul><li>Individual stories are presented for estimation. After a period of discussion, each participant chooses the numbered card that represents his estimate of how much work is involved in the story under discussion. All estimates are kept private until each participant has chosen a card. At that time, all estimates are revealed and discussion can begin again . </li></ul><ul><li>By steps- </li></ul><ul><li>Product Owner starts by explaining a user story to team </li></ul><ul><li>Every team member thinks/writes about his estimated Story Point for that story. </li></ul><ul><li>Estimated are collectively displayed to everyone </li></ul><ul><ul><li>For example 1,2,4,6,6,4,8,8,12 are the cards/estimates shown by a team </li></ul></ul><ul><li>Outliers can be picked up first for analysis </li></ul><ul><ul><li>Like 1 and 12 would be analyzed first in above example </li></ul></ul><ul><ul><li>Developer/team will provide prospective and insight for tagging them 1 and 12 </li></ul></ul><ul><ul><li>And this discussion can address more insight over what exactly is to be developed </li></ul></ul><ul><ul><li>Estimate can be done on teams agreement on a number. </li></ul></ul><ul><ul><li>As a practice team can pick an estimate for general understanding. </li></ul></ul><ul><ul><li>Rules : Don’t go to details & Park the question for later sprints , Time Box, </li></ul></ul>
  25. 25. Planning Poker cont Clarity ? Tester Coder UI Dev Tester Coder Coder 4 8 3 2 4 1 User Story Planning Poker Outliers Discussion Estimates
  26. 26. Daily Stand-Up <ul><li>Held daily </li></ul><ul><li>15- Minutes (no longer, otherwise it’s not a daily stand up) </li></ul><ul><li>Is not a status for the scrum master or project owner. </li></ul><ul><li>Each team member should respond to three questions only: </li></ul><ul><ul><li>1. What have you done since the last daily scrum regarding this project? </li></ul></ul><ul><ul><li>2. What will you do between now and the next daily scrum meeting regarding this project? </li></ul></ul><ul><ul><li>3. What impedes you from performing your work as effectively as possible? </li></ul></ul>
  27. 27. Development <ul><li>Developer picks & owns the high priority stories from sprint backlog. </li></ul><ul><li>Elucidates/Clarifies the requirements if needed with PO/Stakeholders </li></ul><ul><li>Codes, Unit Test </li></ul><ul><ul><li>TDD, Pair Programming for Coding </li></ul></ul><ul><ul><li>Automated testing, Manual Testing </li></ul></ul><ul><li>Incremental build & Hourly build </li></ul><ul><li>Testing on various Environment. </li></ul><ul><li>Collaboration & Knowledge sharing on wiki </li></ul><ul><li>Coding Standard, Architecture </li></ul><ul><li>Zero Defect Policy </li></ul>Done : • All COS met for user story. • All the test cases executed.                • Defects closed. • Rally is updated. • Selenium testing • Demo prepared. • Peer review of code/Test cases
  28. 28. Testing During an Iteration After an Iteration In Integration , System Test & UAT Bug Tracking Test @ Sprint Test @ Release Test Environment Skill Requirement Automation Manual
  29. 29. Sprint Demo or Review <ul><li>Show for stakeholder about what we did in the current sprint ? </li></ul><ul><li>Team prepare for demo using </li></ul><ul><ul><li>Completed story </li></ul></ul><ul><ul><li>Acceptance criteria </li></ul></ul><ul><ul><li>Backlog </li></ul></ul><ul><ul><li>Open defects </li></ul></ul><ul><li>Benefits </li></ul><ul><ul><li>Its for frequent and early reviews </li></ul></ul><ul><ul><li>Get feedback on design and requirements </li></ul></ul><ul><li>Hints </li></ul><ul><ul><li>Focus on acceptance criteria. </li></ul></ul><ul><ul><li>Start with the demo in mind. </li></ul></ul><ul><ul><li>Prepare. </li></ul></ul><ul><ul><li>Practice. </li></ul></ul><ul><ul><li>Tell a story. </li></ul></ul><ul><ul><li>Keep it short </li></ul></ul>
  30. 30. Retrospective <ul><li>During the sprint retro/review the project is assessed against the sprint goal determined during the Sprint planning meeting. </li></ul><ul><li>Ideally the team has completed each product backlog item brought into the sprint, but it is more important that they achieve the overall goal of the sprint. </li></ul><ul><li>Team discuss opportunity & experiences they feel gone wrong and right during the sprint and most importantly what is client feedback on last delivery/demo . </li></ul>
  31. 31. Release <ul><li>Schedule Go Live </li></ul><ul><li>Regression Test, Pre Integration Test, Code Freeze Test. </li></ul><ul><li>Monitor check-in deadlines, Commit, Monitor Sprints </li></ul><ul><li>Integration </li></ul><ul><li>Benchmark current production release for performance </li></ul><ul><li>Code Freeze </li></ul><ul><li>Go no Go meeting </li></ul>Running Tested Feature <ul><li>Test </li></ul><ul><li>Integrate </li></ul><ul><li>Code Freeze </li></ul><ul><li>Done </li></ul>
  32. 32. IV Metrics, Meetings and Reporting
  33. 33. Burn-Down <ul><li>Burn-down Chart shows the estimated number of hours required to complete the tasks of the Sprint. </li></ul><ul><li>It shows both the status and rate of progress (“velocity”) in a way that is both clear and easy to discuss. </li></ul><ul><li>Posted visibly. </li></ul><ul><li>Similar to earned-value chart if you count the delivered functionality (instead of development effort) over time. </li></ul><ul><li>Blue = Task to do and Green = Accepted Points </li></ul>
  34. 34. Velocity <ul><li>Velocity is a measure of how much Product Backlog (Sum of Story Points) the team can complete in a given amount of time. </li></ul><ul><li>Velocity is unit less measure of progress. It can be measure by Feature delivered in an iteration. Feature are usually initial stories. </li></ul><ul><li>Iteration can be planned using velocity. </li></ul><ul><li>Release planning is based on Velocity </li></ul>
  35. 35. Scrum of Scrum <ul><li>Scrum for managing multiple Scrums </li></ul><ul><li>10 -20 Minute Meeting </li></ul><ul><li>Multiple Scrum meet & discuss progress, process and project. </li></ul><ul><li>Discuss dependency & interfacing info </li></ul><ul><li>Resource pooling </li></ul><ul><li>Issue discussion and resolution </li></ul><ul><li>Dependency </li></ul><ul><li>KT </li></ul><ul><li>Training Plan </li></ul><ul><li>Risk Management </li></ul>
  36. 36. Weekly Sync <ul><li>Sync is a weekly activity. </li></ul><ul><li>Each Team presents its progress to Stakeholders based on set indicators like </li></ul><ul><ul><li>Features planned and delivered </li></ul></ul><ul><ul><li>Open defects </li></ul></ul><ul><ul><li>Defect reported in production </li></ul></ul><ul><ul><li>Preproduction defect </li></ul></ul><ul><ul><li>Utilization </li></ul></ul><ul><ul><li>Billability </li></ul></ul><ul><ul><li>You can think of creating simple excel charts </li></ul></ul>
  37. 37. Question ? Retrospective
  38. 38. <ul><li>Contact </li></ul><ul><li>Priyank </li></ul><ul><li>Phone: +91-8108894236 </li></ul><ul><li>Email & Chat </li></ul><ul><ul><li>[email_address] </li></ul></ul>

×