ATC2013-Thiru and Abhishek-How to prevent Agile from becoming Fragile?

  • 473 views
Uploaded on

 

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

Views

Total Views
473
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
0
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
  • Scenario play – Abhishek- CSC, Thiru – Infosys Manager.As Abhishek walks in Thiru asks – Hey abhishek, good to see you here, How are you doing?Abhi- Not very good man, Getting married next month. :PThiru- Okeyyy. abhi we have a project starting next month so can you please help Infosys make this team of 30 resources Agile….fast ?? Abhi- Double whammy !!….I am sure these 2 are common scenarios which many of you have faced. It’s like taking lot of allopathic medicines just to become healthy….fast. Do a slow, all caring healing procedure. If you don’t and just administer too many medicine too quickly…What you are forgetting is that those are going to have side-effects. It’s giving rise to many Agile killing diseases while you are trying to become Agile Fast. It may work fine while you are taking those medicines (While Agile coach is still present in the campus). But as soon as the coach leaves everything will fall around like a pack of cards. I can hear many of you saying we have to meet the customer demand or we will vanish.If not, I guess we will have to find out where we have been and run an emergency intervention, to save that person and to save that initiative of making a team agile.

Transcript

  • 1. How to prevent agile from becoming fragile ? Thirunavukarasu S. and Abhishek Kumar 1
  • 2. About Me • Electrical Engineer + M.B.A. in International Business • Sr. Project Manager in Retail Digital Transformation practice with Infosys • CSM • Accredited with the most Complex Project award by PC Quest Best Implementation Award • Awarded with The best IT implementation award by PC Quest Best Implementation Award http://www.pcquest.com/pcquest/news/178012/pcquest-best-it-implementation-awards-2010 2
  • 3. What is Doing Fragile ? Cost & Time Over Run Lack of workshops Unrealistic schedule/budget Business not involved Team not empowered Capability shortfalls Doing „Fragile‟? Business functionality Feasibility Erroneous Delivery Real-time shortfalls 3
  • 4. How to prevent Agile from becoming Fragile ? How to prevent Agile from becoming Fragile Does Agile become Fragile ? Yes Risk Burndown Chart throughout the life cycle Risk Management not done effectively Adoption of tools and automation best practices during testing, and deployment phases Not extending Agile to testing , and deployment phases Failing to handle interrupts that doesn’t really contribute to new software (Depends on the project & interrupt size) Maintain interrupts in their own prioritized buckets called “ops backlog” 4
  • 5. Versionone: Agile development survey http://www.versionone.com/pdf/7th-Annual-State-of-Agile-Development-Survey.pdf 5
  • 6. Risk Exposure (days) Risk Management: Risk Burndown Chart 16 14 12 10 8 6 4 2 0 1 2 3 4 5 6 7 8 Sprint # Risk Probability of Risk Lack of relevant webServices impacts the development teams ability to validate 1 the credit output There wont be time in the QA process to validate cross compatability of browsers 2 on all OS resolutions Non availability 3rd party services during offshore (IST Timezone) business hours, 3 impact the schedule of the sprint Impact (size of loss in days) 20% 15 3 20% 20 4 40% 20 8 TOTAL 6 Risk Exposure (Days) 15
  • 7. Who does risk management in Agile ? Who:  product owner,  ScrumMaster,  Project manager (Optional), Facilitating risk identification (with the team's help), tracking, and management. When:  Regularly review during road mapping and release planning (identification)  sprint planning (tracking and managing), and  retrospectives (mitigating). Where:  Documented in the project/team backlog as a risk-issue type. 7
  • 8. Common Challenges faced by Agile Team  Distributed development  Communication challenges with geographical distribution  Common time slots for discussion  Overlapping time zone for meetings  Gaps in work, Definition of Done misinterpreted  Lack of appropriate handover  Environment, and its access for sprint demo is not available for first few sprints  Lack of Skills : Scale and Complexity  Poor implementation of ideas  Traceability  Decisions made are not documented for future references 8
  • 9. Adoption of tools and best practices in testing, and deployment phase Automated & Manual Manual Automated & Manual Automated Pre-Deployment Deployment & Post-Deploym across environ ent Configuration ment Deploym ent Automated Automated Tools 9
  • 10. Managing Interrupts: Ops backlog (App gone live) Operate Develop Incident to resolution Idea to working software Can’t reproduce prod incident Monitor Sprint CYCLE TIME REPAIR TIME Instrumentation across app layers 10 • Production debugging • Incident management support • Can’t identify root cause Ops Backlog e.g.:  Tech support that can't be handled by helpdesk  Requests for Root Cause Analysis of weird system behavior  Requests for system data that is not easily available and requires a developer to get  customer customization requests  Production problems that require developer attention  Triage incident & actionable feedback
  • 11. About Me • Mechanical Engineer + M.B.A. in Information technology • Digital Transformation consultant with Infosys • Fanatic reader- I read almost all major blogs written on Agile and Information security….well anything on Apple and Infosys too. • Part of governing council of ISEC. Have been with the team right from inception stages. • Have organized 12+ Agile Tour day long programs like this as part of team ISEC • Also organized India’s first Regional Scrum Gathering at Pune this year as part of team ISEC Linkedin - http://in.linkedin.com/in/abhishekksk/ 11 Twitter- @augusta4u
  • 12. Waste ?? • Why Agile becomes Fragile? Most common reason - People ‘pujo’-fy Agile. • Do rituals1, 2 ,3 and woahh ‘Pujo’ is done? NO • You really would have to believe in the principles of Agile Manifesto. Steps & processes can be different for different projects. • What is Waste?? - In fact, the opposite of ’value’ 12 Image courtesy- http://festivals.iloveindia.com/durgapuja/pics/durga-puja-customs.jpg
  • 13. 7 Wastes in manufacturing- by Shigeo Shingo • Toyota Production System (TPS) Wastes - : 1940s • Inventory: Unfinished goods (also called as "work in progress," or WIP) • Overproduction: Producing more than the demand requires • Extra processing: Additional steps in the process that aren't really needed • Transportation: Shipping the goods from one place to the other • Waiting: Lag between process steps • Motion: Moving around within the process • Defects: Flaws in the deliverables that impact their features/functionality 13
  • 14. 7 wastes of software development- by Mary and Tom Poppendieck • Waste 1: Work not completed as per DoD • Waste 2: Unnecessary features • Waste 3: Bad knowledge-sharing • Waste 4: Hand-offs • Waste 5: Delays • Waste 6: Task Switching • Waste 7: Defects Generally, you will find these wastes during sprint planning or during sprint execution. 14 Image courtesy http://www.amherstma.gov/images/pages/N553/ waste%20reduc.jpg
  • 15. 7 wastes of software development- by Mary and Tom Poppendieck • Waste 1: Work not completed as per DoD • Waste 2: Unnecessary features • Waste 3: Bad knowledge-sharing • Waste 4: Hand-offs • Waste 5: Delays • Waste 6: Task Switching • Waste 7: Defects Generally, you will find these wastes during sprint planning or during sprint execution. 15 Image courtesy http://www.amherstma.gov/images/pages/N553/ waste%20reduc.jpg
  • 16. 7 wastes of software development- by Mary and Tom Poppendieck • Waste 1: Work not completed as per DoD • Waste 2: Unnecessary features • Waste 3: Bad knowledge-sharing • Waste 4: Hand-offs • Waste 5: Delays • Waste 6: Task Switching • Waste 7: Defects Generally, you will find these wastes during sprint planning or during sprint execution. 16 Image courtesy http://www.amherstma.gov/images/pages/N553/ waste%20reduc.jpg
  • 17. 7 wastes of software development- by Mary and Tom Poppendieck • Waste 1: Work not completed as per DoD • Waste 2: Unnecessary features • Waste 3: Bad knowledge-sharing • Waste 4: Hand-offs • Waste 5: Delays • Waste 6: Task Switching • Waste 7: Defects Generally, you will find these wastes during sprint planning or during sprint execution. 17 Image courtesy http://www.amherstma.gov/images/pages/N553/ waste%20reduc.jpg
  • 18. 7 wastes of software development- by Mary and Tom Poppendieck • Waste 1: Work not completed as per DoD • Waste 2: Unnecessary features • Waste 3: Bad knowledge-sharing • Waste 4: Hand-offs • Waste 5: Delays • Waste 6: Task Switching • Waste 7: Defects Generally, you will find these wastes during sprint planning or during sprint execution. 18 Image courtesy http://www.amherstma.gov/images/pages/N553/ waste%20reduc.jpg
  • 19. 7 wastes of software development- by Mary and Tom Poppendieck • Waste 1: Work not completed as per DoD • Waste 2: Unnecessary features • Waste 3: Bad knowledge-sharing • Waste 4: Hand-offs • Waste 5: Delays • Waste 6: Task Switching • Waste 7: Defects Generally, you will find these wastes during sprint planning or during sprint execution. 19 Image courtesy http://www.amherstma.gov/images/pages/N553/ waste%20reduc.jpg
  • 20. 7 wastes of software development- by Mary and Tom Poppendieck • Waste 1: Work not completed as per DoD • Waste 2: Unnecessary features • Waste 3: Bad knowledge-sharing • Waste 4: Hand-offs • Waste 5: Delays • Waste 6: Task Switching • Waste 7: Defects Generally, you will find these wastes during sprint planning or during sprint execution. 20 Image courtesy http://www.amherstma.gov/images/pages/N553/ waste%20reduc.jpg
  • 21. Reference • Scrum Alliance blogs • "Implementing Lean Software Development - From Concept To Cash“ by Poppendieck (http://www.amazon.com/Implementing-Lean-Software-DevelopmentConcept/dp/0321437381) • Microsoft TechEd 2012 • http://lisacrispin.com • http://www.versionone.com/pdf/7th-Annual-State-of-Agile-DevelopmentSurvey.pdf 21