Discovery Model— An Approach for Agile at Scale

Download Discovery Model—An Approach for Agile at Scale

Post on 18-Jan-2017




1 download

Embed Size (px)


<ul><li><p>1 2015 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD</p><p>Discovery ModelAn Approach for Agile at Scale</p><p>Paulo Barbieri</p><p>ADP</p><p>Agile Center of Excellence</p><p>AMT33S</p><p>Agile Management</p><p>@therealbarbieri</p><p>#CAWorld</p></li><li><p>2 2015 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD</p><p>For Informational Purposes Only </p><p> 2015 CA. All rights reserved. All trademarks referenced herein belong to their respective companies.</p><p>The content provided in this CA World 2015 presentation is intended for informational purposes only and does not form any type of warranty. The information provided by a CA partner and/or CA customer has not been reviewed for accuracy by CA. </p><p>Terms of this Presentation</p></li><li><p>3 2015 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD</p><p>Abstract</p><p>When we started our transition to an agile model, many things consultants told us did not make sense. Such as it is a major culture shift, you will need a scaled framework and it is easy to learn hard to master.</p><p>During this session you will learn when ADP reached those hurdles and what we are doing to overcome them.</p><p>Paulo Barbieri</p><p>ADP</p><p>Sr Director of Agility Transformation</p></li><li><p>4 2015 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD</p><p>Agenda</p><p>CONTEXT</p><p>HOW DID WE KNOW WE NEEDED TO SCALE?</p><p>Q&amp;A</p><p>THE DISCOVER MODEL</p><p>THE DISCOVERY PROCESS</p><p>LESSONS LEARNED</p><p>1</p><p>2</p><p>3</p><p>4</p><p>5</p><p>6</p></li><li><p>5 2015 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD</p><p>Small Business Major Accounts National Accounts Multi National Added Value Services</p><p>Comprehensive HRBPO Services</p><p>Open ADP-Supported Marketplace</p><p>Clients /</p><p>&gt; 90,000</p><p>Average Client Size</p><p>~200 employees</p><p>Clients /</p><p>&gt; 500,000</p><p>Average Client Size</p><p>~10 employees</p><p>Clients /</p><p>&gt; 500</p><p>Average Client Size</p><p>~4k employees</p><p>Clients /</p><p>&gt; 1,100</p><p>Countries Served</p><p>~104</p><p>Clients /</p><p>&gt; 600,000</p><p>Average Client Size</p><p>~25</p><p>ContextThe ADP Business Organization</p></li><li><p>6 2015 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD</p><p>Why did we need an agile model?Pain Points that Triggered the Change</p><p>Cultural:</p><p>Teams not empowered</p><p>Different interests within team</p><p>Leader directing the work</p><p>Lack of accountability</p><p>Work Organization: </p><p>Too many dependencies</p><p>Alignment between strategy and execution</p><p>Local optimization costing to the overall process</p><p>Technical:</p><p>Hard to replicate wins</p><p>Economies of scale</p><p>Resource availability</p></li><li><p>7 2015 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD</p><p>Scrum</p><p>Team</p><p>Small Core TeamDiscovery Team</p><p>Executive Sponsor</p><p>Scrum Teams are small core teams with a </p><p>range of skills sets hacker, hustler, visionary, </p><p>average team size of 7, product developer and </p><p>designer.</p><p>Discovery Team is made up of product leader, </p><p>Dev leader, UX researcher and/or architect. </p><p>They provide the next epics of work for the Scrum Teams and the product strategy.</p><p>Executive Sponsor: The VP IT/Product and </p><p>GM ensures teams stay aligned and true to </p><p>their vision and strategy. Can assist with tough </p><p>decisions or a tie break and removing barriers </p><p>across the organization. </p><p>Core Team should only require help from the Executive Sponsor ~1 QRT</p><p>Stake Holders</p><p>Product Discovery ModelSelf Organizing and Empowered Teams</p></li><li><p>8 2015 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD</p><p>Sample of Development Organization with Local Shared Services and CoE Support</p><p>Squ</p><p>ad</p><p>s </p><p>L. S</p><p>ha</p><p>red</p><p> Se</p><p>rvD</p><p>isco</p><p>ve</p><p>ry T</p><p>ea</p><p>m </p><p>DevOps Arch/Dev PMO</p><p>Squad Chief </p><p>CoEs</p><p>Agility</p><p>DevOps</p><p>EPM</p><p>UX/Design **</p><p>Architecture</p><p>Testing **</p><p>** Every Squad should federate to these CoEs (testing and UX/Design)</p><p>Senior Product Owner</p><p>Development Leader UX Leader/Architect</p><p>t</p><p>t</p><p>t</p><p>t</p><p>t</p><p>t</p><p>t</p><p>u</p><p>u</p><p>u</p><p>u</p><p>u</p><p>u</p><p>u</p><p>u</p><p>u</p><p>u</p><p>u</p><p>u</p><p>t</p><p>t</p><p>t</p><p>t</p><p>t</p><p>t</p><p>t</p><p>t</p><p>t</p><p>t</p><p>t</p><p>t t</p><p>t</p><p>t</p><p>t t t</p><p>t</p><p>t</p><p>t</p><p>t</p><p>t</p><p>t</p><p>t</p><p>u</p><p>u</p><p>u</p><p>u</p><p>u u u</p><p>u</p><p>u</p><p>u</p><p>u</p><p>u</p><p>u</p><p>u</p><p>u</p><p>u</p></li><li><p>9 2015 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD</p><p>Portfolio Planning Across the Fiscal Year</p><p>Yearly Planning of Initiatives (Budgeting)</p><p>Roadmap Planning: Continuous Planning on a Cadence</p><p>Release Planning: Quarterly Planning of Features</p><p>Roadmap Review FY PlanningFY Planning</p><p>Q1</p><p>Features</p><p>Construction Sprints Q2</p><p>Features</p><p>Construction Sprints Q3</p><p>Features</p><p>Construction Sprints Q4</p><p>Features</p><p>Construction Sprints</p><p>Roadmap Review Roadmap Review</p></li><li><p>10 2015 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD</p><p>Plan on a cadence. Deliver on demand.</p><p>Plan on a Cadence The sprint cycle does not change due to the planning cycle.</p><p> Only the content or the goals of the sprints change.</p><p>Deploy on Demand</p><p>FY16 Qtr 1 FY16 Qtr 2 FY16 Qtr 4FY16 Qtr 3</p><p>Minor DeploymentMajor Deployment Major Deployment</p><p>J A S O N D J F M A M J</p><p>Release</p><p>Planning</p><p>Release</p><p>Planning</p><p>Release</p><p>Planning</p><p>Release</p><p>Planning</p><p>Milestone </p></li><li><p>11 2015 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD</p><p>Continuous Planning in One Picture</p><p>3 weekSprint</p><p>Release PlanningPortfolio Backlog Release Backlog</p><p>Dependency Estimation(monthly)</p><p>PMO + Discovery Team + Dependent BUs</p><p>SCRUM Team+ SPO</p><p>Backlog Refinement</p><p>StakeholderAlignment(monthly)</p><p>ReleaseQuarterly</p><p>Discovery Team+ Stakeholders</p><p>3 weekSprint</p><p>3 weekSprint</p><p>SCRUM Team+ SPO</p><p>Backlog Refinement</p><p>3 weekSprint</p><p>Portfolio Planning</p><p>Discovery Team</p><p>Portfolio Planning</p><p>Discovery Team</p><p>Portfolio Planning</p><p>Discovery Team</p><p>Portfolio Planning</p><p>Discovery Team</p></li><li><p>12 2015 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD</p><p>SummaryDiscovery Model Learnings</p><p>Key Topics</p><p>How to know you need a scaled model?</p><p>What is the right model for you?</p><p>Where to stop being prescriptive and let the team find the best process?</p><p>Findings</p><p>The symptoms will be clear when you see them.</p><p>SAFe is a good initial model but not necessarily the end state.</p><p>Adopt a model and adjust. </p><p>Experiences</p><p>Improve predictability to 90 percent and responsiveness to under four days.</p><p>Teams and leaders are accountable for outcomes.</p><p>Focus next on DevOps.</p></li><li><p>13 2015 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD</p><p>Q &amp; A</p></li><li><p>14 2015 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD</p><p>Visual AGILExicon</p><p> Slides in this presentation contain items from the Visual AGILExicon, which is a trademark of Innolution, LLC and Kenneth S. Rubin.</p><p> The Visual AGILExicon is used and described in the book: Essential Scrum: A Practical Guide to the Most Popular Agile Process.</p><p> You can learn more about the Visual AGILExicon and permitted uses at:</p><p>Connect with Innolution:</p><p></p><p></p></li><li><p>15 2015 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD</p><p>For More Information</p><p>To learn more, please visit:</p><p></p><p>CA World 15</p><p></p></li></ul>