Your SlideShare is downloading. ×
0
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Agile in Style 2013 Preso by Agilish Ganesh Chandrasekaran

367

Published on

Agile Coaching using the slides in this deck. Happy learning/reading/viewing.

Agile Coaching using the slides in this deck. Happy learning/reading/viewing.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
367
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
13
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Agile in Style Course Material for CSM by Ganesh Chandrasekaran, BE, SCJP, CCD, CWD, PMP,CGBL, CSM, CGTG, CC Certified ScrumMaster Vice President Public Relations of Cupertino Toastmasters
  • 2. One Minute Thanks • “ The energy of the mind is the essence of life. ” • - The Philosophy of Aristotle • http://en.wikipedia.org/wiki/Aristotle Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc.
  • 3. How I started this? • 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 Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc.
  • 4. Agile World • Agile Projects • Agile Labs • Agile Experiments • Agile Strategies • Agile Organizations • Agile Families • Agile Schools Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc. • Agile Sports • Agile Games • Agile Sales • Agile Marketing • Agile Vacation • Agile PLM • Agile Leaders
  • 5. What is Agile? • Dictionary - Able to move quickly and easily • Steve  Jobs truly embraced • agility • throughout his life Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc.
  • 6. • “ We practice mastering ourselves in the mom ” • - Lyssa Adkins • http://www.agilecoachinginstitute.com/ What is Agile? Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc.
  • 7. • “ Success is not final, failure is not fatal: it is ” • - Winston Churchill • http://www.winstonchurchill.org/ Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc.
  • 8. Agile Frameworks Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc. - Survey is from Version One 2011 on overall Agile Projects Scrum Scrum +XP Hybrid Don’t Know
  • 9. Agile Projects Success Source: 2011 CHAOS report from the Standish Group. Analysis 2002-2010
  • 10. ROI on Agility StagesStages Team w/o testsTeam w/o tests Team with testsTeam with tests Implementation 7 days 14 days Integration 7 days 2 days Testing and bug fixing Testing, 3 daysFixing, 3 daysTesting, 3 daysFixing, 2 daysTesting, 1 dayTotal: 12 days Testing, 3 daysFixing, 1 dayTesting, 1 dayFixing, 1 dayTesting, 1 dayTotal: 8 days Overall release 26 days 24 days Bugs in PROD 71 11 (85% decrease) Source: William West all materials are copyright of iTech Argus Inc.
  • 11. Topics to be covered Overview of Scrum Sprints Product Backlog The Team Tracking Progress Meetings Release Planning Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc.
  • 12. Overview of Scrum
  • 13. Source: Online Sources
  • 14. Scrum Process Inventors • Scrum formalized at OOPSLA 1995 Source: Wikipedia Dr. Jeff Sutherland Ken Schwaber
  • 15. 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.
  • 16. Agile/Scrum Overview • A cross-functional team • self organized to develop, • improve continuously, and • deliver working software every sprint. • Product Owner Owns the “What to build” decisions • ScrumMaster Owns the “Scrum process” decisions • Team Owns the “How to build” decisions Source: William West & Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc.
  • 17. The Agile Manifesto Process and ToolsProcess and Tools Individuals and Interactions Individuals and Interactions over Following a PlanFollowing a PlanResponding to ChangeResponding to Change over Comprehensive Documentation Comprehensive Documentation Working SoftwareWorking Software over Contract NegotiationContract Negotiation Customer Collaboration Customer Collaboration over Source: www.agilemanifesto.org
  • 18. Rugby Game http://www.espnscrum.com/ Source: Online Sources
  • 19. What is Agile/Scrum? • Scrum is an agile framework for completing complex projects. Scrum originally was formalized for software development projects, but works well for any complex, innovative scope of work. The possibilities are endless. The Scrum framework is deceptively simple. Source: http://www.scrumalliance.org/learn_about_scrum
  • 20. What is Agile/Scrum? Source: http://www.scrumalliance.org/learn_about_scrum 1. A product owner creates/updates product backlog. 2. Sprint planning, the team picks top priority stories. 3. Team creates a sprint backlog. 4. The team works on a sprint, usually two to four weeks. 5. Team meets every day to assess its progress. 6. The ScrumMaster keeps the team focused on its goal. 7. Sprint review to showcase the product. 8. The sprint ends with a retrospective. 9. Next sprint begins, with Step 1.
  • 21. What is Agile/Scrum? Source:http://swansegarconsulting.com/
  • 22. What is Agile/Scrum? Source: http://www.mitchlacey.com/resources/scrum-framework-flow-diagram
  • 23. What is Agile/Scrum? Source: Unknown
  • 24. Sprint
  • 25. A Sample Sprint MonMon TueTue WedWed ThuThu FriFri MonMon TueTue WedWed ThuThu FriFri 9am9am 10am10am 11am11am 12pm12pm 1pm1pm 2pm2pm 3pm3pm 4pm4pm 5pm5pm SprintSprint ReviewReview Retro-Retro- spectivespectiveSprintPlanningSprintPlanning BacklogBacklog groominggrooming Daily Sync MeetingDaily Sync Meeting Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc.
  • 26. 5 Levels of Planning Source: http://www.rallydev.com/ Level Frequency Who What 1 Vision 1 or 2 years once Product Owner, Executives Vision Statement 2 Product Roadmap 1 or 2 years once Product Owner, Executives Product Evolution / Schedule 3 Release 1 or 2 years once (Varies as per needs) Team, Product Owner, ScrumMaster, Stakeholders Features (aka “User Stories”) 4 Iteration Every Iteration Team & Product Owner Features (aka “User Stories”) + Tasks 5 Daily Daily Team Tasks, To Do, BurnDown
  • 27. 5 Levels of Planning Source: wikipedia, all materials are copyright of iTech Argus Inc.
  • 28. Sprint Doneness Potentially shippable product High Quality Tested Complete Team decides the Doneness What it does, it does very well Show sample Doneness document Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc.
  • 29. Doneness Document Date Task FALSE 31-Dec-12 All code is checked in SVN TRUE 30-Dec-12 Performed code level checks as per code review checklist TRUE 30-Dec-12 Tested the component using multiple browsers TRUE 30-Dec-12 All known issues updated in the Product backlog TRUE 30-Dec-12 Test Caching of all components FALSE 31-Dec-12 All error messages/warning appearing in the log file resolved FALSE 31-Dec-12 All log instances are pointing to the correct logger with the appropriate log level FALSE 31-Dec-12 Tested components with real data TRUE 30-Dec-12 Performed boundary condition checks – null values, very long strings, empty values, negative values etc FALSE 31-Dec-12 Code should be properly commented FALSE 31-Dec-12 Design doc should be updated as per implementation changes FALSE 31-Dec-12 Change history in the code should be updated TRUE 30-Dec-12 Presentation (HTML) code should be well-commented and indented as per Company standards FALSE 31-Dec-12 Designed & coded as per established standards FALSE 31-Dec-12 Functional testing - all applicable use cases should be documented and tested TRUE 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 testing is no possible will exceptions be made FALSE 31-Dec-12 Code reviewed by development lead FALSE 31-Dec-12 Documented as needed for the components Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc.
  • 30. Definition of Done For the business For development Feature richness Code / design review Usability Testing (manual / automated) Performance Unit tests Timing System tests Scalability Refactoring Reliability Integration Cross-cutting concerns Documentation Regression failures Source: William West all materials are copyright of iTech Argus Inc.
  • 31. Architecture in Agile Architecture is built over time More time on Architecture initially Gradual decrease following sprints User valued stories less initially Gradual increase following sprints Source: Mountain Goat Software
  • 32. Sprint Commitment The team commits to stories. The business commits to leave priorities alone during the sprint. Sprint ends on same day every time. Drop scope if needed, but don’t extend. Source: Mountain Goat Software
  • 33. Product Backlog
  • 34. • “ If it's not on the product backlog it doesn't e ” • - Jeff Sutherland • http://www.scruminc.com/ • http://scrum.jeffsutherland.com/
  • 35. Story Writing As a <user type>, I <want/need/can/etc.> some goal, [so that <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
  • 36. Acceptance Criteria Adding 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
  • 37. Acceptance Criteria Scenario 1: Account is in credit Given the account is in credit And the card is valid And the dispenser contains cash When the customer requests cash Then ensure the account is debited And ensure cash is dispensed And ensure the card is returned Source: http://dannorth.net/
  • 38. Backlog Grooming Review the stories in backlog Re-prioritize due to changes in current demands Remove unwanted stories Split epics to stories Product backlog healthy & up to date Source: Mountain Goat Software
  • 39. Product Backlog Source: Online Sources
  • 40. Product Backlog Source: Online Sources
  • 41. The Team
  • 42. • “ A done is not done until the product owner ” • - Ganesh Chandrasekaran
  • 43. Product Owner RAR Source: Mountain Goat Software 1 Defines the features of the product 2 Prioritizes the product backlog 3 Makes scope/schedule tradeoff decisions 4 Responsible for the profitability of the product 5 Adjusts priorities as more is learned 6 Accepts or rejects work results 7 Product vision and strategies
  • 44. • “ A ScrumMaster has to Focus-Follow-Force t ” • - Ganesh Chandrasekaran
  • 45. • “ A servant leader - self-aware, listens, flatte ’ t control, unleashes energy and intelligence ” ScrumMaster RAR
  • 46. ScrumMaster RAR Source: Online Source 1 Be a team player 2 Removes impediments from the team 3 Information Radiator 4 Support the Product Owner 5 Facilitate creativity and empowerment 6 Improve practices and tools as needed 7 Communicate, communicate, communicate
  • 47. Scrum Master Source: Online Sources
  • 48. • “ Talent wins games, but teamwork and intel ” • - Michael Jordan • http://en.wikipedia.org/wiki/Michael_Jordan
  • 49. The Team Source: Mountain Goat Software 1 Members should be full-time 2 Self-organizing 3 Self-discipline 4 Self-awareness 5 Typically 5-9 people 6 Egos, gossip & attitudes are put aside 7 Common goal is Sprint GOAL
  • 50. The Team 8 Rather all of one thing at a time 9 Does a little of everything all the time 1 0 Decide doneness as a team 1 1 Late to daily meetings have a rule 1 2 Respond emails before leaving home 1 3 Trust each other but verify 1 Resolve conflicts in effective way Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc.
  • 51. The Team 1 Software Developers (UI/UX, Mid Tier, Back End) 2 Technical Architect(s) 3 QA Engineer(s) 4 Business Analyst(s) 5 Technical Writer 6 DBA 7 Web Analytics Engineer Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc.
  • 52. Tenets of Tae Kwon Do Courtesy - to help each other Integrity - Team being whole & undivided Perseverance - Sprint Goal Self-Control - Team is self-organized Indomitable Spirit - Motivate Team Success Victory - Yes We Did IT!!! Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc. “Tae Kwon Do and Scrum are both about doing the right thing in a situation rather than mastering a list of rules” - Mike Cohn
  • 53. Team Building Source: Five Dysfunctions of a Team and http://www.agilecoachinginstitute.com/student-stories/
  • 54. Meetings
  • 55. • “ Planning is a must have, timeboxing it keep ” • - Ganesh Chandrasekaran
  • 56. Sprint Planning • Who: Team, ScrumMaster & Product Owner • Agenda: Discuss top priority product backlog items Team selects which items to do • Why: Know what will be worked upon Discuss backlog items enough to do them Source: Mountain Goat Software
  • 57. Sprint Planning contd. How full should a sprint be? Unplanned time Plannable time Corporate overhead Estimate & Analyze Tasks estimated 1-8 hours High-level design is considered Time boxed to 90 mins meeting time Source: Mountain Goat Software
  • 58. Sprint in Detail Sprint 1 ActivitiesSprint 1 Activities SprintPlanningSprintPlanning Day2Eng.TasksDay2Eng.Tasks Day3Eng.TasksDay3Eng.Tasks Day4Eng.TasksDay4Eng.Tasks Day5Eng.TasksDay5Eng.Tasks Day6Eng.TasksDay6Eng.Tasks Day7Eng.TasksDay7Eng.Tasks Day8Eng.TasksDay8Eng.Tasks Day9Eng.TasksDay9Eng.Tasks DemoPrepareDemoPrepare SprintReviewSprintReview RetrospectiveRetrospective SprintCompleteSprintComplete Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc.
  • 59. Sprint Planning Source: Online Sources
  • 60. Sprint Planning Source: Online Sources
  • 61. Exercise #1 TEAM A Top 2 items for me 1. ITEM No. 1 2. ITEM No. 2 TEAM A Top 2 items for me 1. ITEM No. 1 2. ITEM No. 2 TEAM B Top 2 items for me 1. ITEM No. 1 2. ITEM No. 2 TEAM B Top 2 items for me 1. ITEM No. 1 2. ITEM No. 2 TEAM C Top 2 items for me 1. ITEM No. 1 2. ITEM No. 2 TEAM C Top 2 items for me 1. ITEM No. 1 2. ITEM No. 2 TEAM D Top 2 items for me 1. ITEM No. 1 2. ITEM No. 2 TEAM D Top 2 items for me 1. ITEM No. 1 2. ITEM No. 2 TEAM C Top 2 items for me 1. ITEM No. 1 2. ITEM No. 2 TEAM C Top 2 items for me 1. ITEM No. 1 2. ITEM No. 2
  • 62. Commitment Driven Pick high-priority story in backlog Decompose it into tasks Estimate each task Team members ask themselves: “Can we commit to this?” If yes repeat with next story Source: Mountain Goat Software
  • 63. Velocity Driven Needs 4-5 sprints velocity chart Use average or previous sprint velocity Grab user stories equal to that velocity Possibly stop there, but some team: Identify tasks for selected stories Some then estimate those tasks Source: Mountain Goat Software
  • 64. Story Points A measure of relative size of feature Based on the total effort involved Key is the relative size of numbers Team does best sizing in 2-3 sprints 1,2,3,5,8,13,20,40,100 Planning Poker once a month Source: Mountain Goat Software
  • 65. Daily Scrum/Sync Up Daily sync choose a time & stick to it 15-minutes and that’s the maximum Not for problem solving Whole world is invited, only team talk To reduce other meetings Source: Mountain Goat Software
  • 66. Daily Scrum/Sync Up What did you do yesterday? What will you do today? What, if anything, is in your way? Each team member max 1-2 mins Prepare 5 mins previous day - 3Qs. Source: Mountain Goat Software
  • 67. Famous Story on Scrum • A Pig and a Chicken are walking down the road. • The Chicken says: "Hey Pig, I was thinking we should open a restaurant!" • Pig replies: "Hm, maybe, what would we call it?" • The Chicken responds: "How about 'ham-n-eggs'?" • The Pig thinks for a moment and says: "No thanks. I'd be committed, but you'd only be involved!" Source: wikipedia
  • 68. • “ There's no way to force someone to be ener ” • - James Shore • http://www.jamesshore.com/
  • 69. Daily Scrum/Sync Standup Source: Online Sources
  • 70. Scrum Task Board Source: Online Sources
  • 71. Scrum Task Board Source: Online Sources
  • 72. Role: QA Engineer Part A: I watched the Bond movie yesterday.The scene where friends take it on bad guys is awesome. I liked that scene very much. I am a Bond Fan. Role: QA Engineer Part A: I watched the Bond movie yesterday.The scene where friends take it on bad guys is awesome. I liked that scene very much. I am a Bond Fan. Role: Tech Architect Part A: I was googling about Automatic Hot Deploy in WebLogic 12C, this is an interesting theme. We should look at exploring this more for our project as well. Role: Tech Architect Part A: I was googling about Automatic Hot Deploy in WebLogic 12C, this is an interesting theme. We should look at exploring this more for our project as well. Role: Developer 1 Front End Part A: I had a flat tire today morning, hence was delayed to work. I called AAA but they are slow in service. Does anyone know better road side services? Role: Developer 1 Front End Part A: I had a flat tire today morning, hence was delayed to work. I called AAA but they are slow in service. Does anyone know better road side services? Role: Developer 2 Middle Tier Part A: I saw the weather channel, tomorrow is going to snow. I am going to work from home. How about you guys? Role: Developer 2 Middle Tier Part A: I saw the weather channel, tomorrow is going to snow. I am going to work from home. How about you guys? Role: Developer 3 Back End Part A: I saw the news channel, looks like Obama is going to create a new fund called Developer Association Fund. We all should discuss on this topic today, how it will impact us? Role: Developer 3 Back End Part A: I saw the news channel, looks like Obama is going to create a new fund called Developer Association Fund. We all should discuss on this topic today, how it will impact us? Exercise #2 Role: Not a Team Member (Chicken) Part A: I see you guys gather everyday same time. What exactly you guys discuss here? Role: Not a Team Member (Chicken) Part A: I see you guys gather everyday same time. What exactly you guys discuss here?
  • 73. Role: QA Engineer I tested the story 123 User Login and completed 2 acceptance criteriaI will test today story# 321 File Upload No impediments Role: QA Engineer I tested the story 123 User Login and completed 2 acceptance criteriaI will test today story# 321 File Upload No impediments Role: Tech Architect I worked on story 234 Handling Large Files in upload designing the performance tuningI will continue today as well. No impediments Role: Tech Architect I worked on story 234 Handling Large Files in upload designing the performance tuningI will continue today as well. No impediments •Role: Developer 1 Front End •I had completed task 8 in story 245 authoring form English Today will take task 3 in story 246 authoring form multiple languages. I have impediment on detail of task 3. Impediment is how many languages to be translated is not in story. Need answer from product owner. •Role: Developer 1 Front End •I had completed task 8 in story 245 authoring form English Today will take task 3 in story 246 authoring form multiple languages. I have impediment on detail of task 3. Impediment is how many languages to be translated is not in story. Need answer from product owner. Role: Developer 2 Middle Tier I had completed task 7 in story 245 authoring form English. Today will take task 2 in story 246 authoring form multiple languages. I have no impediment. Role: Developer 2 Middle Tier I had completed task 7 in story 245 authoring form English. Today will take task 2 in story 246 authoring form multiple languages. I have no impediment. Role: Developer 3 Back End I had completed task 6 in story 245 authoring form English. Today will take task 1 in story 246 authoring form multiple languages. I have no impediment. Role: Developer 3 Back End I had completed task 6 in story 245 authoring form English. Today will take task 1 in story 246 authoring form multiple languages. I have no impediment. Exercise #2 Role: Not a Team Member (Chicken) He/She should just watch the action - No talk. Role: Not a Team Member (Chicken) He/She should just watch the action - No talk.
  • 74. • “ Done is not done, until the Product Owner a ” • - Ganesh Chandrasekaran
  • 75. Sprint Review Team presents the product Demo of new features or architecture 2 hours prep guideline Whole team participates Invite the world Source: Mountain Goat Software
  • 76. Sprint Review Source: Online Sources
  • 77. Sprint Review Source: Online Sources
  • 78. • “You improvise. You adapt. You overcome.” • - Clint Eastwood • http://en.wikipedia.org/wiki/Clint_Eastwood
  • 79. • “Sometimes when you innovate, you make mistakes. It is best to admit them quickly, and get on with improving your other innovations.” • - Steve Jobs • http://en.wikipedia.org/wiki/Steve_Jobs
  • 80. • “Without continual growth and progress, such words as improvement, achievement, and success have no meaning.” • - Benjamin Franklin • http://en.wikipedia.org/wiki/Benjamin_Franklin
  • 81. Sprint Retrospective What worked very well? What went wrong? How can we improve? Did we improve from last Sprint? 30-60 minutes maximum Done after every sprint ScrumMaster, Product Owner & Team Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc.
  • 82. Sprint Retrospective Source: Online Sources
  • 83. Sprint Retro
  • 84. Start - Stop - Continue
  • 85. ROTI - Return On Time Invested
  • 86. Sprint Retrospective Source: Online Sources
  • 87. Agile Estimation
  • 88. Estimation 1 Relative Sizing 2 Story Points 3 Wideband Delphi (WBD Technique) 4 PROBE Technique 5 Planning Poker 6 Ideal Time 7 Affinity Diagram Estimating Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc.
  • 89. Relative Sizing Pick one and estimate Pick second and compare and estimate Question yourself while estimating If any unknowns raise red flag Mismatch then discuss and debate T-shirt sizes S,M,L,XL,XXL Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc.
  • 90. Wideband Delphi A consensus-based technique Moderator finds experts for opinion Moderator gets data from experts Moderator collates, sends for voting Error by 40% accuracy by 80% Done after every sprint ScrumMaster, Product Owner & Team Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc.
  • 91. PROBE Technique Proxy Based Estimating(PROBE) Experience on same type of feature Estimated quickly with accuracy Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc.
  • 92. Story Points A measure of relative size of feature Based on the total effort involved Key is the relative size of numbers Team does best sizing in 3-4 sprints 1,2,3,5,8,13,20,40,100 Planning Poker once a month Source: Mountain Goat Software
  • 93. Planning Poker Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc. BookBook NoNo Pts.Pts. 1 Minute Manager 100 3 Winning Formulas 200 5 The Talent Code 176 5 Succeeding with Agile 450 8 “Good friends, good books, and a sleepy conscience: this is the ideal life.” ― Mark Twain
  • 94. Planning Poker Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc. RoomRoom Run 1Run 1 Run 2Run 2 Kitchen Garage Living Washer M Bed 1 Bed 2 Bed 3
  • 95. House Moving Project
  • 96. Ideal Time Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc. Time to complete no interruptions • Often expressed in days • 8hrs of ideal time could take 3 days • Longer if more distractions “We provide reliable estimates” - James Shore
  • 97. Affinity Diagram Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc. 1. Silent Relative Sizing 2. Editing of wall 3. Place Items into relative buckets 4. Product Owner Challenge 5. Get it into electronic tool
  • 98. Velocity Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc. 1. Sum of story point in an iteration 2. Varies from iteration to iteration 3. Varies between different teams 4. Helps Release Planning 5. 3-4 iterations to stabilize velocity
  • 99. Cycle Time Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc. 1.Story entered into the backlog date 2.Date when team starts the story 3.Date when the story is “done” • Working cycle time = Difference between start and end date of story
  • 100. Tracking Progress
  • 101. Tracking Progress • Task Boards with task current view • Burndown Charts • Release burndown chart • Sprint burndown chart • Velocity chart • Show net progress • Promote transparency • Bad News is Good News (fail early than late) Source: Mountain Goat Software
  • 102. Velocity Chart Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc.
  • 103. Burndown Chart Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc.
  • 104. Combined Chart
  • 105. Release Planning
  • 106. Release Planning • Sprints to complete the total backlog • Use team velocity and total story points • Hardening Sprint as needed • Release Sprint as needed • Mean Time Between Failure(MTBF) test • Stress, performance or usability testing • Compliance testing, documentation touchups Source: Mountain Goat Software
  • 107. Sample Release Plan Phase 1 ReleasePhase 1 Release RegularSprintRegularSprint RegularSprintRegularSprint RegularSprintRegularSprint HardeningSprintHardeningSprint RegularSprintRegularSprint RegularSprintRegularSprint RegularSprintRegularSprint HardeningSprintHardeningSprint RegularSprintRegularSprint RegularSprintRegularSprint ITSprintITSprint UATSprintUATSprint ReleaseSprintReleaseSprint Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc.
  • 108. Succeeding with Agile -Mike Cohn
  • 109. 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
  • 110. Q&A
  • 111. Good Luck Good Health Good Karma Hope this has given an intuitive and informational session Best Regards Ganesh Chandrasekaran ScrumMaster 2.0 Global Agile Coach Agile Leader
  • 112. Sample Projects
  • 113. QuickTemp Thermometer Project Charter Overall Objective • To implement a robust thermometer that will allow for easy use to read temperature quickly and accurately. Strategy • Re-usable strips to measure the temperature • Alternative to ear, nose, mouth temperature readers • Hygienic and child safe for appropriate usage Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc.
  • 114. QuickTemp Thermometer Project Charter Scope • QuickTemp Designer • Health specialist for Quality testing • QuickTemp to be better, faster, and cheaper • Easy to read temperature for children in 5 secs Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc.
  • 115. Critical Success Factors Key Success Elements Critical Success Factor Today Target 1 Ease of use for children Current thermometer not easy to use Ease of use 2 Better, Faster, and Cheaper 10 secs to read temp 5 secs to read temp 3 Accuracy to be close to 95% Not sure of accuracy 95% accuracy Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc.
  • 116. QuickTemp Project 1 Market Analysis 2 Base Model 3 Cost vs Benefit Analysis 4 Safety measures for children 5 Hygienic for re-use 6 Ease of use 7 Pediatric Certified Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc.
  • 117. Vacation Planning Guide • Show creating a backlog • Show how backlog is prioritized • Exercise the Poker game for top 10 stories • Exercise commitment with story cards • Exercise the Daily Scrum Meeting • Show the artifacts displayed in demo Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc.
  • 118. Build an Agile School • Teachers and Principal • Students admission • School policies and rules • School building construction • Monthly sprint cycle for grades • Retrospective for areas to improve Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc.
  • 119. • “Change is good. Changing frequently towards good makes you great.” • - Ganesh Chandrasekaran Source: Ganesh Chandrasekaran all materials are copyright of iTech Argus Inc.

×