What is Agile Development? • The catch-line for Agile Software Development is Deliver Quickly, Deliver Often • Agile Traits: – – – – – – Managing Agile Software Development Laura Ingram Measure everything Self-Organising Teams Deliver Frequently Place to Learn Communication Testing 29 May 2009 Copyright ©2009 Accenture All rights reserved. Accenture, its logo, and High Performance Delivered are trademarks of Accenture. What is Agile Development? BURNDOWN CHART Self-Organizing Teams Measure everything BACKLOG Test everything TIMEBOXING Deliver frequently Plan to learn Bridge Construction SIMPLE DESIGN REFACTORING • Most of product planned in detail in advance Requirements moderately evolving Some usable product delivered early Additional usable product features added frequently Construction of each subcomponent is relatively short in duration Entire product planned in detail in advance Requirements set largely up-front No usable product until construction is complete Construction may take years PAIR PROGRAMMING 3 ©2009 Accenture All rights reserved. Accenture’s Approach to Agile Development Requirements Incremental Completeness Development and Stability Management and stakeholder support Project can be divided in to a large (8+) number of iterations Short-term project (max. 12 months) Sufficiently small, co-ordinated and autonomous team ©2009 Accenture All rights reserved. 4 Selection Criteria People Process Infrastructure Culture Available Skills Timeframe and Effort Deal Shape Development Location Development Strategy All Increments Scoped UpFront No Desire Leveraged Team Any Any Any Plan-Driven Moderately Evolving Scoped UpFront with Some Room to Maneuver Some Desire Leveraged team Any Any Preferably One Site Hybrid All On-Site Agile / Adaptive High-Level and Constantly Evolving 5 Willingness to Experiment Set Largely Up-Front Project Selection Criteria – – – – Product not planned in detail in advance Requirements high-level and constantly evolving Usable product at the end of each iteration Adaptive and evolutionary Frequent Iterations When to Choose Agile Critical success factors: – – – – Evolutionary Biology AUTOMATED BUILD/DEPLOY ©2009 Accenture All rights reserved. • Railroad Construction SHORT RELEASES RETROSPECTIVES USER STORIES STORY WALL CO-LOCATION ON-SITE CUSTOMER DAILY STAND-UPS ACCEPTANCE TESTS Agile / Adaptive Hybrid Plan-Driven CONTINUOUS INTEGRATION Agile Practices Communicate powerfully TEST-DRIVEN DEVELOPMENT RELEASE PLANNING SPRINT / ITERATION SUSTAINABLE PACE VELOCITY METRICS AUTOMATED TESTING How is Agile Different? CROSS-FUNCTIONAL TEAM WHOLE TEAM COLLECTIVE OWNERSHIP 2 ©2009 Accenture All rights reserved. Scoped As Project Progresses ©2009 Accenture All rights reserved. Strong Willingness Flexible Time and Well-skilled completion Materials date and team Only limited effort 6 Case Study Case Study • Current client is undertaking the implementation of changes to an existing system to improve the consistency of data between this and other systems used within the business • S t System Overview: O i Initial actions: • SWAT Team Formation – 1 Member representing each team – Co-ordinating g team leader • Defined process for solving problems • Timeline driven by a drop-dead date (approx. 2 months) A Our system EAI Ongoing actions: • Setup testing environment • Defect tracking • Daily team meetings • Daily status reports to management B • Data is moved between the systems in the form of XML using real-time interfaces. • Mid-build integration problems! 7 ©2009 Accenture All rights reserved. 8 ©2009 Accenture All rights reserved. Case Study #1 – Context • Accenture is partnering with a retail bank implementing a large scale IT solution for Loan Originations • 4000 users Australia wide, 19 Production servers • Multiple Releases over the last 4 years involving client staff, Accenture, contractors and external vendors located overseas • Users on different end-user platforms, different network speeds • Single web browser used (Microsoft Internet Explorer 5.5 +) • New web browser based application replacing old mainframe system Outsourcing and Project Closure Ravi Goundar Development work is performed using an on-shore Accenture team and an off-shore vendor team 29 May 2009 Copyright ©2009 Accenture All rights reserved. Accenture, its logo, and High Performance Delivered are trademarks of Accenture. 10 ©2009 Accenture All rights reserved. Case Study #2 – Context Outsourcing IT outsourcing is the utilization of external organizations for provision of information technology services. • Accenture partnered with a large global insurance company to implement a new self-service web portal solution to provide investment product transactions for the client’s customers and a channel for regular contact with their investment advisor • Self-service solution was targeted for it’s customers across Australia and areas across Asia Pacific Some reasons why y we outsource ¾ To reduce both fixed and recurrent costs ¾ To allow the client organization to focus on its core business ¾ To access skills and technologies ¾ To provide flexibility Design and Development work was performed using an off-shore team engaged by the client ©2009 Accenture All rights reserved. ¾ To increase accountability 11 ©2009 Accenture All rights reserved. 12 Reduce Fixed and Recurrent Costs Focus on Core Business ¾ Infrastructure Outsourcing – Outsourcing of Servers to a third party to reduce operational costs for this equipment. This can also incorporate leasing of equipment as opposed to purchasing ¾ Printing / Statements – Banks need to print customer correspondence ¾ Human Resources – Outsourced this function to people that are better equipped to manage people matters ¾ Resources: Access to lower cost resources in areas such as design, development or help desk resources that can provide similar levels of service ¾ Fi Finance – Outsource O t finances fi such h as time ti reporting, ti accounts t payable bl / receivable and account reconciliation ¾ Implement different resource models: fixed price / unit, time and materials, unit price contract 13 ©2009 Accenture All rights reserved. ¾ Help Desk – Outsource Help Desk functions 14 ©2009 Accenture All rights reserved. Access Skills and Technologies Provide Flexibility ¾ Skills – Need access to highly skilled developers for development work ¾ Resources – Be able to request more resources or reduce number of resources ¾ Technology – Need access to new technology that would be of significant cost if purchased or even leased by an organization e.g. Asset Tracking ¾ Skill sets – Be able to request new resources that have skill sets in a particular product or technology ¾ Working Hours – Be able to request for additional extended work hours if required to support the business 15 ©2009 Accenture All rights reserved. 16 ©2009 Accenture All rights reserved. Increase Accountability Project Closure ¾ Cost Overrun – Manage overtime, work hours Key Project Closure Activities ¾ Management of Issues and Risks – Transfer some issue and risk responsibility to the outsourcing provider ¾ PIR (Post Implementation Review) – Lessons Learned ¾ Performance Appraisals ¾ Service S i L Levels l and dP Penalties lti ¾ Documentation – Support, Project, Financial ¾ Closure of Project Financials ¾ Celebration !!! ©2009 Accenture All rights reserved. 17 ©2009 Accenture All rights reserved. 18