InspectandAdaptLessonsLearnedfromanEnterpriseRoll-.pptVIP

11/16/07 Inspect and Adapt: Lessons Learned from an Enterprise Roll-out of Scrum March 18, 2009 Presented by the US-based Implementation Team Leaders: Cheryl Neeser, CSP Rod Hunter, CSP Abstract Many would agree that strong executive support along with training, coaching and communication are essential components of any Scrum implementation. What other pieces of the puzzle shouldn’t be forgotten to help pave the way to a successful Organizational Change Management program? Two years and $1M later, what critical lessons were learned and what tactics and strategies were applied during Tailspin’s enterprise roll-out of Scrum. This presentation covers the structure and milestones of one enterprise’s Scrum implementation. Highlights include: Strategies and goals-based activities Major components and sub-projects What worked well and what didn’t The obstacles overcome and the ‘boulders’ that still lay in the pathway Advice that we have to offer to those attempting a similar broad agenda What would we do differently if we could do it over again Why Scrum? A strategic corporate-wide reengineering project, was initiated to address issues along the entire “customer line of sight” Focus on aligning with the customer lifecycle and holistically addressing bottlenecks Demand and Resource Portfolio Management Delivery Stability and Quality Post Sales Customer Relationship Management End to End development (E2E) Problems We Were Trying to Solve Absence of customer focus Rapidly changing, incomplete or inadequate business requirements Inadequate integration testing Limited base of business analysts Seriously eroded subject matter expertise Productivity on/off-shore division of labor Coordination communication Development efficiency Was Scrum the Solution? Would a process change enable the organization to realize increases in productivity, quality and project delivery? E2E Program Goals Provide better quali