1 / 24

Agile Transformation- Projects & Program

Agile Transformation- Projects & Program. Archana Mehta. Spot a Failing project. Costs a lot more than it should Its takes longer than anyone expected The product doesn’t do what it was supposed to Nobody is happy about it. Because… we all speak different languages. Why “Agile”?.

tasha-chase
Télécharger la présentation

Agile Transformation- Projects & Program

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Agile Transformation- Projects & Program Archana Mehta

  2. Spot a Failing project • Costs a lot more than it should • Its takes longer than anyone expected • The product doesn’t do what it was supposed to • Nobody is happy about it

  3. Because… we all speak different languages

  4. Why “Agile”? • Project priorities change • Increasing need for reduced time-to-marketand enabling frequent delivery • Make application releases more predictive • Improve customer involvement • Learning and responding to customer needs is critical in today’s business environment

  5. Waterfall VS Agile Methodology

  6. SCRUM Changes/Requirements from stakeholders or Project Sponsor go as user stories on the backlog and get prioritized by the Chief Product Owner Deliverable -Working Software! Demos and Retrospectives are part of the Continuous Improvement loop Continuous Quality up front in process decreases Risk & Cost!

  7. Scaled AGILE Framework

  8. Scaled Agile Framework™ Big Picture

  9. ADOPTION PLAN

  10. Lay of the Land

  11. Transition Plan

  12. Choose a pilot project • Form teams by product lines or functional areas • Engage a Champion or Agile Coach if team is new to Agile • Inspect, learn and adapt

  13. Set Agile adoption timeline Q1 Q2 Q3 Q4 Project 1 SCRUM SCRUM Scaled Agile Project 2 SCRUM Project 3 …model the same in other projects to get a true Portfolio adoption

  14. Release Plan 2015 Release Release Release Release Release Release 10-12 Wks 10-12 Wks 10-12 Wks 10-12 Wks 10-12 Wks 10-12 Wks Development Sprint 4 Development Sprint 3 Development Sprint 1 Development Sprint 2 Development Sprint 4 Development Sprint 3 Development Sprint 1 Development Sprint 2 Development Sprint 3 Development Sprint 1 Development Sprint 4 Development Sprint 2 Development Sprint 3 Development Sprint 1 Development Sprint 4 Development Sprint 2 Development Sprint 1 Development Sprint 4 Development Sprint 3 Development Sprint 2 Development Sprint 4 Development Sprint 3 Development Sprint 1 Development Sprint 2 HIP Sprint HIP Sprint HIP Sprint HIP Sprint HIP Sprint HIP Sprint Project 1 Project 2 Project 3 Project 4

  15. Product owner cloud CHINA CANADA INDIA SPAIN Chief Product Owner JAPAN TURKEY GERMANY UK MEXICO BRAZIL Scrum Team 2 Scrum Team 4 Scrum Team 5 Scrum Team 1 Scrum Team 3

  16. Identify and Mitigate Risks Risks Mitigation Plan Some projects are time bound with hard dates, transition to a new method may cause disruption for in-flight waterfall projects. Budget considerations for Agile Training Resource constraints, time commitment is heavy. Engagement with Systems teams • Choose a pilot project in the initial phases • Tap into internal community of practitioners and champions • Set the staffing plans for project/program with the demand signals for resource needs • Establish working agreements with the Systems teams

  17. Project Manager

  18. Role of Agile Project Manager • Manage stakeholder communication • Enable rather than control • Ensure project meets its goals and objectives • Removes Roadblocks

  19. Agile Mindset lets you embrace change

  20. Benefits of moving to Agile • Allows us to become more lean and deliver faster on things that matter more to business • Flexibility to respond faster to changing customer needs • Manage interdependencies across the Program • Allows for dealing with ambiguity • Fosters Innovation • “Software applications developed through the agile process have three times the success rate of the traditional waterfall method and a much lower percentage of time and cost overruns”** • **Source- 2011 CHAOS report from the Standish Group

  21. Recommendations • Co-located Scrum teams with a dedicated collaboration room. • Time commitment from the customer, >20 hours a week. 2- 3 full days or half days every week • Cross-Pollination – Bring Mature Agile teams or Champions from other parts of your organization to set up the pilot Project/Program space • Establish working agreements with shared systems teams • Leadership buy-in and alignment across IT function and customer area • Training sessions for the team and mentoring during transition • Progressively increase Agile capability by evolving into Scaled Agile Framework

  22. Feedback and Questions • I would love to hear from you • Contact me at archmehta@hotmail.com

More Related