Agile Beyond The Team 1

Similar documents
Manifesto for Agile Software Development

Agile Development Overview

Agile Project Management with Scrum

Agile Project Management By Mark C. Layton

Software Processes. Agile Methods

26 May 2010 CQAA Lunch & Learn Paul I. Pazderski (CSM/CSP, OD-CM, CSQA) spcinc13@yahoo.com Cell: AGILE THROUGH SCRUM

Agile Overview. 30,000 perspective. Juha Salenius CSPO CSM PMI-ACP PMP SCGMIS Workshop January 23 rd, 2013

Introduction to Agile Software Development. EECS 690 Agile Software Development

History of Agile Methods

Agile Development with C#

werteorientierte Unternehmenskultur

Agile Project Management

Ingegneria del Software Corso di Laurea in Informatica per il Management. Agile software development

Governments information technology

Comparing Scrum And CMMI

Scaling Scrum. Colin Bird & Rachel Davies Scrum Gathering London conchango

Agile on huge banking mainframe legacy systems. Is it possible?


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

USCIS/SPAS: Product Backlog Items and User Stories 4/16/2015. Dr. Patrick McConnell

Introduction to Agile and Scrum

Creating a High Maturity Agile Implementation

This handbook is meant to be a quick-starter guide to Agile Project Management. It is meant for the following people:

Bottlenecks in Agile Software Development Identified Using Theory of Constraints (TOC) Principles

Introduction to Agile Software Development

AGILE - QUICK GUIDE AGILE - PRIMER

Agile Processes and Distributed Projects: Dream or Nightmare?

Risikominimering I IKT-prosjekter - experiences from the Danish Government

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

LEAN AGILE POCKET GUIDE

Aristotle in an Agile World. By Ben Allen

Processes in Software Development. Presented by Lars Yde, M.Sc., at Selected Topics in Software Development, DIKU spring semester 2008

Agile-Waterfall Hybrid Jessica LaGoy, MS, PMP

What does it mean to be Agile. Marek Majchrzak, Andrzej Bednarz Wrocław,

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

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

How To Understand The Limitations Of An Agile Software Development

Adopting Agile Project Management - Corporate Culture Must Match (Apr 15)

How to manage agile development? Rose Pruyne Jack Reed

Developing the Agile Mindset for Organiza7onal Agility. Shannon Ewan Managing

Role of Agile Methodology in Software Development

Agile Software Development. Mohsen Afsharchi

Agile Projects 7. Agile Project Management 21

Agile QA s Revolutionary Impact on Project Management

ITSM Agile Intro Feb 5, 2015

What Does Large Mean? Copyright 2003 by N. Josuttis and J. Eckstein 3. Why is Large an Issue?

Continuous Integration: Improving Software Quality and Reducing Risk. Preetam Palwe Aftek Limited

Agile Execution for and Beyond IT

Agile In a Nutshell. Note - all images removed to fit 2MB limit Actual presentation has much more content. Jonathan Rasmusson

Development. Lecture 3

RISK MANAGMENT ON AN AGILE PROJECT

SCEA 2010 EST06. Estimating Issues Associated with Agile. Bob Hunt. Galorath Incorporated

PMBOK? You Can Have Both! June 10, Presented by:

Agile Project Management: Adapting project behaviors to the software development environment

Agile Project Management and the Real World. Emily Lynema DLF Fall 2010 November 1, 2010

Agile and lean methods for managing application development process

Challenges of Software Security in Agile Software Development

Agile Extension to the BABOK Guide

TSG Quick Reference Guide to Agile Development & Testing Enabling Successful Business Outcomes

An Agile Project Management Model

The Team... 1 The Backlog... 2 The Release... 4 The Sprint... 5 Quick Summary Stakeholders. Business Owner. Product Owner.

Agile Fundamentals, ROI and Engineering Best Practices. Rich Mironov Principal, Mironov Consulting

New Developments in an Agile World: Drafting Software Development Agreements. By: Paul H. Arne 1,2

The Agile Manifesto is based on 12 principles:

UC Santa Barbara. CS189A - Capstone. Christopher Kruegel Department of Computer Science UC Santa Barbara

Mitigating Risk with Agile Development. Rich Mironov CMO, Enthiosys

How can I be agile and still satisfy the auditors?

Agile Scrum Workshop

CSSE 372 Software Project Management: More Agile Project Management

CS435: Introduction to Software Engineering! " Software Engineering: A Practitioner s Approach, 7/e " by Roger S. Pressman

When agile is not enough

Agile and lean methods for managing application development process

Agile Project Management

Jukka Mannila KEY PERFORFORMANCE INDICATORS IN AGILE SOFTWARE DEVELOPMENT

Comparative Study of Agile Methods and Their Comparison with Heavyweight Methods in Indian Organizations

What s Lean Agile & How does it allow teams to progressively improve customer satisfaction & service delivery?

Agile Project Management Jim Highsmith. Chapter 1. The Agile Revolution

An Introduction to Agile Performance Management

Agile Scrum Training. Nice to meet you. Erik Philippus. Erik Philippus (1951)

Agile and PRINCE2 And how they integrate. enterprise.bcs.org

Case Study on Critical Success Factors of Running Scrum *

Agile Software Development in the Large

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

SCRUM BODY OF KNOWLEDGE (SBOK Guide)

Software Development with Agile Methods

Transitioning Your Software Process To Agile Jeffery Payne Chief Executive Officer Coveros, Inc.

From Agile by Design. Full book available for purchase here.

The Basics of Scrum An introduction to the framework

Agile Project Management. What it is and what it isn t

Vragen. Software development model. Software development model. Software development model

Introduction to Agile Software Development Process. Software Development Life Cycles

EXTREME PROGRAMMING AGILE METHOD USED IN PROJECT MANAGEMENT

Neglecting Agile Principles and Practices: A Case Study

Agile and ITIL And how they integrate. enterprise.bcs.org

Agile Notetaker & Scrum Reference. Designed by Axosoft, the creators of OnTime the #1 selling scrum software.

Quality Assurance in an Agile Environment

Introduction to Agile

Agile Software Development with Scrum. Jeff Sutherland Gabrielle Benefield

Taking the first step to agile digital services

Agile Software Development

Transcription:

Agile Beyond The Team 1

Dilbert Agile 2

What Does Your Organization Value? Projects over Teams? Do new teams spools up for new projects? On-Time/On-Budget Delivery over Zero Maintenance Products Deliver now and we will fix it later? Plans or Planning? Can teams dance with inevitable change? Project Managers or Autonomous Teams? Continuous Improvement? Innovation/Craftsmanship? By dedicating time to it 3

Agile Changes Business Priorities Organize Around Teams Rather Than Projects Organize Around Quality And TCO Working Software - primary measure of progress Organize Around Collaboration Co-Locate Cross-Functional Organize for Team Autonomy Self Organizing Self Deterministic Self Referential 4

Agile Changes Business Priorities Create Clearings for Autonomous Teams Stop Needing Control Stop Enforcing Hierarchy Stop Telling Teams How to Deliver Teams Choose Practices Create Clearings for Building Trusted Teams Hire Great People and Trust Them to Deliver Continuous Improvement Retro s Everyone/Everywhere Innovation/Craftsmanship By dedicating time to it 5

Agile Principles and Values Individuals and Interactions over Processes and Tools Working Product over Comprehensive Documentation Customer Collaboration over Contract Negotiation Responding to Change over Following a Plan Collective Autonomy & Minimal Oversight Working Software as the primary measure of progress Bring the Work To The Team Emergent Design Fail Fast & Cheap & Learn Ambient Knowledge Confidence in the codebase Trust Us Courage Speak Truth to Power Systemic Discipline Continuous Improvement Accountability Self-Organization Hire Great People Need People Who Have Been There, Done That Defect Prevention over Defect Detection Team Ownership of Quality Product Owners And They are in the Team Room Emergent Architecture Emergent Design 6

Organizational Culture 7

I Want You To Change! 8

Agile Culture 9

Agile Magic Will Happen Trust US! 10

Agile Changes Business Practices PMO Stop requesting detailed estimates Finance Fund Discovery/Ideation Phase No we don t have a guarantee of payback or ROI Marketing Stop Promising Product/Functionality by dates HR Start Hiring Culture Fit, Not Just Skillset Stop Incentivizing Individual Performance Think Team Executives Stop Controlling 11

The Fly in the Agile Ointment 12

The Fundamental Agile Business Question Why would the business buy into this stuff? It sounds to them like we are asking no demanding them to change. 13

We Must Change Our Approach 14

Speak To Business Concerns Increasing Revenue New Products/Sales Produce Assets Whenever Possible Decreasing Expenses Faster Leaner Lower Cost Producing a Competitive Advantage Innovations Producing a Strategic Asset Platforms

In Business Terms: Assets & Liabilities What is necessary to produce an asset? Liabilities! Liabilities take 4 forms: Time Energy Capital Lost Opportunity Depreciating Assets One off product, old technologies, High maintenance - buggy codebase Appreciating Assets Platform that serves many new customers

Business Speak: Strategic Asset Have you ever cloned code from a successful project to serve a new customer? Multiple Times? How challenging was it to then transition those products to a platform? Platforms can be an asset or a liability Highly automated test suite asset No Test Suites High Maintenance liability The business can buy into an agile developed platform if the story about it includes: Lower TCO, Higher customer responsiveness and Multiple opportunities for additional revenue

We ve All Seen the Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.

Principles Behind The Agile Manifesto We follow these principles: Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Business people and developers must work together daily throughout the project. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Working software is the primary measure of progress. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Continuous attention to technical excellence and good design enhances agility. Simplicity--the art of maximizing the amount of work not done--is essential. The best architectures, requirements, and designs emerge from self-organizing teams. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

Selling Agile How do we sell these Values, Principles & Practices to the business?

What Is The Business Benefit of Each Agile Practice? Pair Programming Big & Visible Charts Lean Estimation Refactoring Small Release Cycles Coding Standards Collective Ownership System Metaphor Whole Team Emergent Design Definition Of Done Co-Location Cross-Functional Planning Game Scrum Daily Standups Test Driven Design Behavior Driven Development Continuous Integration Code and Design Reviews Active Stakeholders Design Patterns CLEAN Code Continuous Value Delivery Test Automation Release Automation Team Backlog 21

What Is Your Story??? What story can you articulate around how any one or all of these practices leads to: Increased Revenue Decreased Expenses Competitive Advantage Strategic Asset 22

Align With Business Goals & Objectives: Increase Revenue Reduce Expense Improved Strategic Capacity Goal Innovation Lean-ification Craftsmanship Objectives Produce Competitive Differentiation Produce New Revenue Streams Improve Throughput Remove Waste New Competitive Practice Adoption Deliver Value From Customer Perspective 23

Align Goals & Objectives With Strategies: Increase Revenue Reduce Expense Improved Strategic Capacity Goal Innovation Lean-ification Craftsmanship Objectives Produce Competitive Differentiation Produce New Revenue Streams Improve Throughput Remove Waste New Competitive Practice Adoption Deliver Value From Customer Perspective Strategies Establish Innovation Initiaitives Establish Continuous Improvement Practices Establish Prioritized Backlog for Products & Initiatives Measure Quality & Value Through Customer Feedback Loops Establish regular IT status cadence and report outs Establish excellence or best practices skill growth strategy Establish World Class Customer Service & Practices Establish World Class Infrastructure & Practices Establish & Meet Quality Standards from Customer Perspective Establish Service Level Agreements 24

Goal Increase Revenue Connect the Dots with Practices: Lean-ification Innovation IT & Business Agile Transformation Goal Model Reduce Expense Improved Strategic Capacity Craftsmanship Increase Revenue IT & Business Agile Transformation Goal Model Reduce Expense Improved Strategic Capacity Objectives Produce Competitive Differentiation Goal Produce New Revenue Streams Innovation Improve Throughput Remove Waste Lean-ification New Competitive Practice Adoption Craftsmanship Deliver Value From Customer Perspective Strategies Establish Innovation Initiaitives Objectives Strategies Establish Continuous Improvement Practices Establish Innovation Initiaitives Produce Establish Prioritized Competitive Backlog for DifferentiationProducts & Initiatives Establish Continuous Improvement Practices Produce New Revenue Streams Establish Prioritized Backlog for Products & Initiatives Measure Quality & Value Through Customer Feedback Loops Improve Throughput Measure Quality & Value Through Customer Feedback Loops Establish regular IT status cadence and report outs Establish regular IT status cadence and report outs Remove Waste Establish excellence or best practices skill growth strategy Establish excellence or best practices skill growth strategy Establish World Class New Competitive Customer Practice Adoption Service & Practices Establish World Class Customer Service & Practices Establish World Class Infrastructure & Practices Establish World Deliver Value From Class Infrastructure Customer & Practices Perspective Establish Service Level Agreements Establish & Meet Establish Quality Standards Service from Customer Level Agreements Perspective Establish & Meet Quality Standards from Customer Perspective Planning & Estimation Status & Information Radiation Cross-Functional Teams Retrospectives Meet Quality Standards Source Code Management Continuous Integration Practices Practices Planning & Estimation Status & Information Radiation Cross-Functional Teams Practices & Skils Surveys & Assessments Practices & Skils Surveys & Assessments Retrospectives Meet Quality Standards Source Code Management Continuous Integration Release & Iteration Planning Prioritized Backlog & Backlog Grooming Release & Iteration Planning Daily Standups Prioritized Backlog & Backlog Grooming Regular Product/ New Functionality Demonstrations Regular Product/ Daily Standups New Functionality Demonstrations Automated Testing at all layers of the Automated Testing test harness at all layers of the test harness Must Have Practice Highly Recommended Practice Highly Innovative Practice Must Have Practice Minimum Practice Highly Recommended Practice 25

What About Agile Beyond Software We all know that a lot of the processes and practices we bring to Agile Software Development are borrowed from the other aspects such as the Lean Manufacturing and Start-Up Movements. What can we take from our new processes and practices and loan to other industries, organizations or groups to better them? Any thoughts? 26