The Contractor Body: What You Measure

Similar documents
Introduction to Agile and Scrum

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

The Lean Startup. Eric Ries. Dr Linda Hickman. Department of Management public lecture. Suggested hashtag for Twitter users: #lsestartup

Business Analysis In Agile A Differentiated Narrative

IndigoBlue Governance Framework

Agile Project Management

AGILE BUSINESS MANAGEMENT

To the point. a recipe for creating lean products. Paulo Caroli. This book is for sale at

A Viable Systems Engineering Approach. Presented by: Dick Carlson

Enabling Continuous Delivery by Leveraging the Deployment Pipeline

Capitalizing on Change

Agile Models. Software Engineering Marco Scotto Software Engineering

Why the Traditional Contract for Software Development is Flawed

B.2.2. Project Management Principles

Agile Metrics. It s Not All That Complicated

What s New In ITIL V3?

Scrum vs. Kanban vs. Scrumban

Understanding Agile Project Management

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

Enhanced Portfolio Management in uncertain times

Using Measurement to translate Business Vision into Operational Software Strategies

Financial Planner Competency Profile

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

Continuous Delivery. Martin Fowler, Jez Humble YOW! Brisbane, 5 December Wednesday, December 7, 11

Scaling Agile Is Hard, Here s How You Do It!

When agile is not enough

Course Overview Lean Six Sigma Green Belt

Essential Metrics for Agile Project Management

Hyper-sonic flight. Ness Case Study. Ness Technologies

Principles of IT Governance

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

Ensuring Reliability in Lean New Product Development. John J. Paschkewitz, P.E., CRE

Learning Objectives Lean Six Sigma Black Belt Course

BUSINESS INTELLIGENCE DRIVER FOR BUSINESS TRANSFORMATION IN INSURANCE INDUSTRY Author s Name: Sunitha Chavaly & Satish Vemuri

Applying Lean Concepts in Project Management. Ing. Mauricio Gomez Melendez MAT. PMP.

The Business Case for OEE Systems

Taking the first step to agile digital services

Continuous Delivery. Anatomy of the Deployment Pipeline (Free Chapter) by Jez Humble and David Farley

Lean Metrics How to measure and improve the flow of work. Chris Hefley, CEO of LeanKit. November 5 th, 2014

Rispondere al cambiamento attraverso un approccio agile al PM

The Blending of Traditional and Agile Project Management

SUCCESSFULLY INTEGRATING AGILE WITH EARNED VALUE MANAGEMENT

Unifying the Private Fleet with Purchased Transportation

An Agile Project Management Model

SCRUM. A Tool from the Software World Can Improve Analytical Project Outcomes. By KyMBER WALTMUNSON

EB TechPaper. Managing complexity with agile development. automotive.elektrobit.com

White Paper. Process Improvement

Risk Management. National Occupational Standards February 2014

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

Defining Quality Workbook. <Program/Project/Work Name> Quality Definition

LEAN ACCOUNTING FAD OR FASHION?

Agile Risk Management

The Agile Service Management Guide. By Jayne Gordon Groll

FIELD GUIDE TO LEAN EXPERIMENTS

Agile Project Management. Jan Pool NioCAD University of Stellenbosch 16 April 2008

Performance Management Is performance management really necessary? What techniques are best to use?

International Centre for Complex Project Management

Agile Beyond The Team 1

Managing the Supply Chain of the Future

Practical Agile Requirements Engineering

Lean Software Development

The 10 Elements of a Vested Outsourcing Agreement. Kate Vitasek

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

From Business Intelligence to Predictive Analytics. James Taylor CEO, Decision Management Solutions

Web Applications Development and Software Process Improvement in Small Software Firms: a Review

VI Simposio Internacional sobre Energía y Foro de Innovación y Emprendimiento. Por: Bartolomé Gamundi Cestero

CHANGE MANAGEMENT PLAN WORKBOOK AND TEMPLATE

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

Agile user-centred design

Data Governance Implementation

LEAN SUPPLY CHAIN MANAGEMENT TOPICS IN. Marc J. Schniederjans. Dara G. Schniederjans. Ashlyn M. Schniederjans. :.,.' If I.

Software Center. Customer Data and Ecosystem Driven Development

SCALING AGILE. minutes

Agile Software Development

Data Governance Implementation

DEMAND SMARTER, FASTER, EASIER BUSINESS INTELLIGENCE

Agile Training Portfolio

BCS Foundation Certificate in Agile

How$Spotify$builds$products$

ICAgile Learning Roadmap Agile Testing Track

Troy Magennis Moneyball for Software Projects: Agile Metrics for the Metrically Challenged

Agile Software Development

Module 2: A Strategic Approach to Energy Management

The Emotional Economy at Work

Software Development Methodologies

Transcription:

EFFECTIVE CONTRACT METRICS FOR DELIVERING BUSINESS VALUE Agile Business Conference 10-11 October 2012 Susan Atkinson

A CONTRACT THAT REFLECTS AGILE?

YOU GET WHAT YOU MEASURE Perhaps what you measure is what you get. More likely, what you measure is all you get. What you don t (or can t) measure is lost. H Thomas Johnson (2006)

CONTRACTS DRIVE BEHAVIOUR

THE TRADITIONAL CONTRACT FOR SOFTWARE DEVELOPMENT Output-Based Requirements Activity-based metrics based on sequential development Change control mechanism NOTE: The charging model is secondary So are IP ownership, data protection, liability, indemnities etc.

MAJOR INFLUENCES BEHIND THE TRADITIONAL CONTRACT Sir Isaac Newton 1642-1727 Frederick Taylor 1856-1915 1863-1947 1875-1966 The Industrial Revolution 1750-1850

THE IMPACT OF THE TRADITIONAL CONTRACT Increases the risk of failure: Delivery risk Business value risk Existing business model failure risk Leads to the design of suboptimal software Leads to a poor return on investment

THE TRADITIONAL CONTRACT FOR SOFTWARE DEVELOPMENT Output-Based Requirements Activity-based metrics based on sequential development Change control mechanism

SO WHAT IS THE COMMERCIAL MODEL?..

START WITH WHY

THE COMPLEXITY THEORY The Stacey Matrix Supplemented by the Cynefin framework

MANAGEMENT FOR THE DIFFERENT CONTEXTS SIMPLE COMPLICATED COMPLEX Known Knowns Known Unknowns Unknown Unknowns Stable environment Stable environment Unpredictability and flux Clear relationship between cause and effect Clear relationship between cause and effect BUT not everyone can see it No/little relationship between cause and effect Understand only in retrospect Right answer is self-evident and undisputed Multiple right answers BUT not everyone can see it No right answers Sense, Categorise, Respond Sense, Analyse, Respond Probe, sense, respond Command and Control Consult the experts Trade-off between right answer and making a decision Experimental mode of management Allow patterns to emerge and select the best ones

THE BUSINESS ADVOCATES OF COMPLEXITY THEORY

THE COMPLEXITY THEORY Software Development

SOFTWARE DEVELOPMENT IS COMPLEX The customer discovers what it wants The supplier learns what to build Many things change along the way: Internal changes customer s perception External factors market, regulations, end user expectations

WHAT IS EXPERIMENTAL MANAGEMENT? Hypothesis Target outcome Boundaries Fast feedback Minimum viable product (MVP)

SIMPLE RULES Simple, clear purpose and principles give rise to complex and intelligent behavior. Complex rules and regulations give rise to simple and stupid behavior. Dee Hock, CEO Emeritus VISA International

HOW TO MEASURE ANYTHING Measurement is a quantitatively expressed reduction of uncertainty based on one or more observations. Douglas Hubbard, 2010 It is better to be approximately right than precisely wrong. Warren Buffett

THE CONTRACT - STRUCTURE Results-focused - agnostic to methodology Focuses on the goal and the constraints Modular structure for incremental development Sequencing of work Ability to take into account changes and learning in subsequent work No upfront design

THE CONTRACT METRICS Framework with various options for each SOW Different metrics can be called off into each SOW to suit the circumstances: Output and targets model each SOW for an MVP Throughput and targets model each SOW for a specified number of story points / function points Targets model each SOW for an MVP [The MVP] is the fastest way to get through the Build- Measure-Learn feedback loop with the minimum amount of effort ( The Lean Startup by Eric Ries) Variety of charging mechanisms

THE IMPACT OF THE CONTRACT Reduces the risk of failure: Delivery risk transparency of the process, prioritisation, reduces exposure to change Business value risk focus on targets of the customer Existing business model failure risk no big bang roll out Increases the likelihood of optimal design Design and development are not artificially divorced Regular feedback from the customer Increases the likelihood of a good ROI: Less waste Increased productivity

CONCLUSION Natural selection may explain the survival of the fittest, but it cannot explain the arrival of the fittest Hugo devries, 1905 New contract model for complex contexts required Management styles need to change Different commercial models are required

THANK YOU Susan Atkinson 166 Chiltern Court Baker Street London NW1 5SW Tel: +44 7843 284 543 Email: satkinson@evolve.com