When agile is not enough



Similar documents
NokiaSiemens and Agile Development by Petri Haapio JAOO 2008

Lean and Agile Development With Scrum (Part 2) Lucio Davide Spano

Executive Guide to SAFe 24 July An Executive s Guide to the Scaled Agile Framework.

Applying Lean on Agile Scrum Development Methodology

Introduction to Agile and Scrum

Agile and lean methods for managing application development process

What is meant by the term, Lean Software Development? November 2014

Getting to Done The Secret Sauce of High Performing Teams

Agile Beyond The Team 1

Kanban vs Scrum Making the most of both

Lean Software Development

Agile Software Development in the Large

The Basics of Scrum An introduction to the framework

Introduction to Scrum for Managers and Executives

The Agile Business Analyst: Eyes for Waste By Ellen Gottesdiener Copyright EBG Consulting, Inc., 2009 EBG Consulting, Inc.:

Introduction to Enterprise Agile Frameworks

Agile and lean methods for managing application development process

Agile Training Portfolio

Agile Project Management and Agile Practices Training; with a Scrum Project that you will do.

Quality Assurance in an Agile Environment

Lean Software Development and Kanban

Building the Lean Agile Enterprise with the Scaled Agile Framework:

AGILE SOFTWARE DEVELOPMENT: INTRODUCTION, CURRENT STATUS & FUTURE Pekka Abrahamsson Jyväskylä

Why Agile Works: Economics, Psychology, and #PrDC16

Automated Acceptance Testing of High Capacity Network Gateway

Agile Project Management

Agile Project. Management FOR DUMME&* by Mark C. Layton WILEY. John Wiley & Sons, Inc.

Agile extreme Development & Project Management Strategy Mentored/Component-based Workshop Series

SESSION 303 Wednesday, March 25, 3:00 PM - 4:00 PM Track: Support Center Optimization

Scaling Agile with the Lessons of Lean Product Development Flow Copyright 2012 Net Objectives, Inc. All Rights Reserved

MTAT Software Engineering

Agile with XP and Scrum

Secrets of a Scrum Master: Agile Practices for the Service Desk

CSPO Learning Objectives Preamble. Scrum Basics

What is Scrum? Scrum Roles. A lean approach to software development. A simple framework. A time-tested process

No one has to change. Survival is optional. - W. Edwards Deming - Continue your Beyond Budgeting Journey with help from Agile, Lean and Scrum

Agile Development to Transform FedEx

Jukka Mannila KEY PERFORFORMANCE INDICATORS IN AGILE SOFTWARE DEVELOPMENT

How To Be Successful At An Agile Software Engineering

Kanban For Software Engineering

Gothenburg 2015 Jan Marek com CA Technologies Introducing Agile development methodologies to Session S601 mainframe development teams

Program & Portfolio! Management using! Kanban! Copyright 2013 Davisbase Consulting. Limited Display License Provided to ASPE

Scaling Lean-Agile Practices Across the Enterprise

Bridging the Gap Between Acceptance Criteria and Definition of Done

Water-Scrum-Fall Agile Reality for Large Organisations. By Manav Mehan Principal Agile consultant

Leading Continuous Improvement in Established Agile Organizations

W hitepapers. Delighting Vodafone Turkey s Customers via Agile Transformation

Lean Agile Scrum Business Value Development and Delivery using Agility. Brenden McGlinchey Software Done Right, Inc.

Leveraging Agile and CMMI for better Business Benefits Presented at HYDSPIN Mid-year Conference Jun-2014

Case Study on Critical Success Factors of Running Scrum *

A Viable Systems Engineering Approach. Presented by: Dick Carlson

Agile Systems Engineering: What is it and What Have We Learned?

The Agile Manifesto is based on 12 principles:

Continuous User Experience Development

SECC Agile Foundation Certificate Examination Handbook

CSSE 372 Software Project Management: More Agile Project Management

Risikominimering I IKT-prosjekter - experiences from the Danish Government

Agile Certification: PMI-ACP

by Craig Larman and Bas Vodde Version 1.2

Lean Silver Certification Blueprint

Waterfall to Agile. DFI Case Study By Nick Van, PMP

Agile & PMI Project Management Mapping MAVERIC S POINT OF VIEW Vol. 7

Course Title: Managing the Agile Product Development Life Cycle

Certified ScrumMaster Workshop

Scrum Is Not Just for Software

Nationwide Application Development Center

Getting Started with Agile Project Management Methods for Elearning

Kanban vs Scrum Making the most of both

Scrum in a Large Project Theory and Practice

agenda AGILE AT SCALE

Rolling Wave Planning: Manage Projects Without Going Under

Agile Testing. What Students Learn

Scrum vs. Kanban vs. Scrumban

Agile Scrum Workshop

Glossary SAFe 4.0 for Lean Software and Systems Engineering

Digital Transformation of the Enterprise for SMAC: Can Scrum help?

Agile Project Management By Mark C. Layton

How NOT to Do Scrum. Patterns and Anti-patterns. Revised July First presented at New York City Scrum User Group June 17, 2010

Chapter 6. Iteration 0: Preparing for the First Iteration

How to measure productivity in software development

Software Development Moves from a Craft to an Engineering Discipline Using the Essence Standard

SCRUM BODY OF KNOWLEDGE (SBOK Guide)

From Performance Management to Leading Performance. Kati Vilkki and Esther Derby

Agile Metrics - What You Need to, Want to, and Can Measure. June 9, 2014

Agile Scrum and PMBOK Compatible or Contrary?

Mitigating Risk with Agile Development. Rich Mironov CMO, Enthiosys

LEAN AGILE POCKET GUIDE

White Paper. Process Improvement

Transcription:

When agile is not enough LESS 2010 Kati Vilkki kati.vilkki@nsn.com 1 Nokia Siemens Networks

When agile is not enough What does lean thinking add to agile? Combining agile and lean Change in mind-set Management roles Leadership practices 2 Nokia Siemens Networks

Nokia Siemens Networks 3 Nokia Siemens Networks

Over 60,000 people in more than 150 countries More than 600 Communications Service Provider customers One of the largest Telecommunications suppliers Every second we touch the lives of millions of individuals 4 Nokia Siemens Networks

What we do Wireless access 2G 3G LTE Transport and fixed broadband Microwave Optical Fixed access Core networks Voice core Subscriber data management Telecom routing Management and charging Network management systems Service management Charging solutions Services Network implementation Care Managed services Consulting and systems integration 5 Nokia Siemens Networks

Global presence North East North America West & South Europe Greater China Latin America India APAC Middle East & Africa R&D in all technology hotspots in the world. Major sites in Finland, Germany, China, India and US. 6 Nokia Siemens Networks

Our agile journey 7 Nokia Siemens Networks

NSN target Increased flexibility and efficiency of product development through Agile development Increased flexibility and ability to implement changes Customer and value oriented development Improved visibility to actual status of development Higher engagement and better motivation through empowered teams Build quality in (continuous integration, test automation, test early, continuous attention to technical excellence) 8 Nokia Siemens Networks

Overview of our agile transformation Products / teams Experimenting Legitimatization Agile as the main street development mode Agile and iterative 10 20 point of no return Agile and Lean 10% in agile 25% in agile Lean and agile 55% in agile All relevant products involved Scope Coaches Support Offered trainings R&D Merger announced R&D, product management 8-10 Nokia Siemens Networks R&D, product management, HR practices, metrics, management processes 2 Local Agile coaches networks Retrospective Coaching for TDD facilitator Cookbook coaches Agile intro TDD Product owner training Agile for managers Self-organizing teams CSM Agile estimating and planning Scrum overview Leading lean and agile product development Kick-off workshop Agile requirements and user stories Simulation workshop TDD & ATDD coaching NSN Agile days in Helsinki NSN Agile days in Bangalore 2005 2006 2007 2008 2009 2010 9 Nokia Siemens Networks

NSN Basic Agile practices Time-boxed short iterations (< 4 weeks) Prioritized product backlog Continuous integration Self-organized, cross-functional feature teams Inspect and adapt in use These practices set the organizational framework for agile development, but are not enough alone 10 Nokia Siemens Networks

Agile is Short iterations where something gets done (maybe) List of features called the product back-log Daily reporting meetings (called daily Scrums) Scrum managers Builds that are red most of the time or green builds that don t mean anything because of too few test cases No (A)-TDD, refactoring, pair-programming No time for learning Product management and development not talking to each other No customer feedback Technical debt accumulating constantly Commitment games 11 Nokia Siemens Networks

Doing agile or Being agile?? 12 Nokia Siemens Networks

Be agile, don t do agile Lean and agile transformation is not just a process change, it changes some of the basic assumptions and thought patterns about product development It is about continuous improvement towards Improved ability to create value for customer Shorter cycles and faster response times Empowered people and self-organized teams Technical excellence and high quality Start now, take small steps and be prepared to question all aspects of your work and organization 13 Nokia Siemens Networks

Agile company Agile practices in every day SW development Lean thinking in improving the whole value chain Management philosophy and organizational practices 14 Nokia Siemens Networks

Understand the thinking behind 15 Nokia Siemens Networks

Lean practices are context dependant Lean manufacturing Repetitive tasks Low variability Homogenous flows Lean product development Non-repetitive tasks High variability Non-homogenous flows So what is lean? Donald G. Reinertsen 16 Nokia Siemens Networks

Lean ideas Focus on creating value for customer Respect the people Order Faster Cash Reduce the cycle-time to improve flow and surface (and remove) waste R e m o v e Stop and fix build quality in Waste Continuous improvement culture System 17 Nokia Siemens Networks

Build quality in 18 Nokia Siemens Networks

Impact of technical debt Size Business R&D problem? Debt Time Technical debt slows development down More and more difficult to make changes High maintenance load Low morale 19 Nokia Siemens Networks

Reducing / avoiding technical debt Make technical debt visible Make impact of technical debt visible Branch as late as possible, merge as early as possible Continuous integration Build architecture which supports adding new features at any time Use good engineering practices Code includes automated tests Reserve time for learning Sustainable pace STOP digging! 20 Nokia Siemens Networks

Limit work to capacity 21 Nokia Siemens Networks

How to be efficient? 100% resource utilization?? OR Limit work to capacity (queuing theory) Limit the amount of work-in-progress (WIP) Focus on flow and cadence 22 Nokia Siemens Networks

BUT We have committed We have to deliver It is not realistic Replace Wishful thinking Belief in magic With Transparency Accepting realities Continuous improvement Your system output is what your system is currently capable of. Increasing system capability requires continuous effort and systematic improvement. 23 Nokia Siemens Networks

Waste 24 Nokia Siemens Networks

Value and waste from customer point of view Value stream mapping Identify waste Overproduction of features or of elements Waiting, delay Handoff, conveyance Extra processing, relearning Partially done work, WIP Task switching, motion between tasks, interrupt-driven multitasking Defects, testing and correcting Underutilizing people s capability (only doing their job) Knowledge and information scatter or loss Wishful thinking 25 Nokia Siemens Networks

Changing leadership culture servant leadership 26 Nokia Siemens Networks

Combining bottom-up and top-down Top down Lean thinking Business objectives Organizational values Change the management culture and behavior Providing resources Bottom up Agile practices chosen and adopted by the teams Self-organization Empowerment It's a big challenge for management to support the change sufficiently and not to over-drive it. 27 Nokia Siemens Networks

Told vs. others How satisfied are you with the impact of agile development within your own work? Dialogue Engage Invite Some other way than told Satisfied Neither satisfied nor dissatisfied Dissatisfied We were told to do it Would you go back to the old way of working? 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% Some other way than told I would not go back I see no difference I would go back We were told to do it 28 Nokia Siemens Networks 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100%

Failure patterns Management by incentives Usage of agile practices, velocity, improvement in velocity, green builds Pushing agile It s an R&D thing, you change No/little investment in learning and coaching Leadership team does not have the time or interest to lead the change Start by defining the agile process 29 Nokia Siemens Networks

Success patterns Agile champion(s) from the organization Setting boundaries, letting teams choose Leadership team and managers showing example Agile transformation team working closely with the leadership team And/or leadership team investing a lot of time Systematically involving every one inviting people to join Agile approach to agile transformation 30 Nokia Siemens Networks

It is all about people 31 Nokia Siemens Networks

Respect for the people Customers Do not trouble your customer Serve and delight your customer Own people Craftsmanship Systematically develop good people then build products No wasteful work Teams and individuals evolve their own practices and improvements Develop teams Collaborators Build partners with stable relationships Modified from Lean Primer by Craig Larman and Bas Vodde 32 Nokia Siemens Networks

Management roles 33 Nokia Siemens Networks

Are managers needed? Creating an engaging vision of the product reason to be passionate about what we do Mentoring and coaching helping people become good in what they do Creating the environment for people to succeed in Leading the culture 34 Nokia Siemens Networks

Organizational practices 35 Nokia Siemens Networks

Organizational practices Target setting and incentives No individual incentives Measure up Performance evaluations Feedback is needed Financial planning and tracking Career paths 36 Nokia Siemens Networks

Finally 37 Nokia Siemens Networks

Fundamental agile and lean ideas Continuous attention to technical excellence Build quality in Respect for the people Systematically build good people and give them the environment to get things done Business people and development working together daily Customer focus Understand what your customer needs and values Work with the customer Continuous improvement culture 38 Nokia Siemens Networks

Individual choices matter As a developer Am I committed to continuously improve our working practices? Am I doing deliberate practice to become a true master? Am I challenging my managers to support me in creating value for the customer? Am I systematically refusing to sacrifice quality and my professional pride? As a manager Am I creating optimal conditions for my team to succeed in creating value for the customer? Am I continuously challenging and changing dysfunctional organizational practices? Am I coaching my people to grow to their full potential? Am I relentlessly removing waste? 39 Nokia Siemens Networks

Thank you! 40 Nokia Siemens Networks