$BILLION AGILE EXECUTING LARGE EPC/EPCM PROJECTS USING SCRUM VALUES AND PRINCIPLES

Similar documents
SCRUM - compact The agile software development methodology

Scrum Team Roles and Functions

AGILE LESSONS FROM THE NEW PMBOK. Presented by Eddie Merla, PMI-ACP, PMP

This course will explore how your projects can easily and successfully make the transition to an effective Agile environment.

AGILE FOR NON-IT PRACTITIONERS

Standard Work and the Lean Enterprise Net Objectives Inc. All Rights Reserved.

AGILE FOR NON-IT PRACTITIONERS

What is Scrum: An Introduction to the Scrum Framework

Presented by Only Agile. What is Agile?

An Introduction to Scrum

Johanna Rothman. Chapter 1 Why Agile and Lean Approaches Work. Copyright 2017

AGILE EXECUTIVE OVERVIEW

BA25-Managing the Agile Product Development Life Cycle

The Seven Deadly Sins of Scrum

Introduction to Agile and Scrum

Maureen Weverka & Kathy Burnham Mutual of Omaha. November 9, Mutual of Omaha Insurance Company. All Rights Reserved.

Improving Agile Execution in the Federal Government

AGILE SOLUTIONS. Agile Basics

getting started with Scrum

GLOBAL CENTRE OF EXCELLENCE (GCE) EXCEL AND LEAD

Agile Essentials Track: Business Services

Can Your Proposal Process Be More Agile?

Copyright Intertech, Inc All Rights Reserved. May 18, 2011

Scrum Alliance Certified Team Coach SM (CTC) Application SAMPLE

Chapter 01 - The Process The Process Application Process ACP Qualifications Scheduling Your Exam Rescheduling/Cancelling Fees

Agile Methodology For Developing & Measuring Learning

Agile Introduction for Leaders

Scrum an Agile Process

AGILE INTERNAL AUDIT (IA)

RIGHTNOW A C E

JOB DESCRIPTION. Senior Project Manager.docx. Job family Project Management Grade 9

Team GRC vs Scrum: Agile outside the softw are development w orld 8/11/2016. Laura Jones, PMP, PMP-RMP, CMQ/OE, CGPM Risk Manager

Management by Consensus

Managing Projects of Chaotic and Unpredictable Behavior

Agile Software Development

WELCOME TO INTRO TO AGILE PROJECT MANAGEMENT AUBREY KAIGLER, PMP, ITIL. Please configure your audio: Meeting Audio Setup Wizard

Agile Scrum Process Checklist

Certified Team Coach (SA-CTC) Application - SAMPLE

Change Agile. Ben Linders, André Heijstek. veranderproject.nl

Finally! A Model for Evaluating Agile Performance: The Agile Performance Holarchy. Darian Poinsetta Senior Executive Agile CxO

The ABC of Agile Business Change. James Yoxall BCS 17 September, 2013

Scrum. Software Engineering and. The Waterfall model. The Waterfall model - some arguments. The Waterfall model - some arguments. Time.

Agile Software Development. Agile Software Development Basics. Principles of the Agile Alliance. Agile Manifesto. Agenda. Agile software development

Agile Acquisition. Peter Modigliani 10 Dec 12. Presented to: Mr. Koen Gijsbers. General Manager NATO Communications and Information Agency

Scrum Intro What s in it for me?

From Growing Pains to Embracing Change

Introduction to Scrum

Scrum & Business Intelligence

Agile Delivery Framework (ADF)

Debunking Agile Myths

PMI Agile Certified Practitioner (PMI-ACP) Duration: 48 Hours

Agile Methodology For Developing & Measuring Learning

Taking Agile Way Beyond Software

How to Reboot Your Agile Team MAURIZIO MANCINI EXEMPIO.COM

Best Practices for Enterprise Agile Transformation

A Guide to Critical Success Factors in Agile Delivery

AGILE methodology- Scrum

Owning An Agile Project: PO Training Day 2

4. Agile Methods. Prof. Dr. Dirk Riehle, M.B.A. Friedrich Alexander-University Erlangen-Nürnberg. Version of

@GRNET. Running Scrum in a conservative, multi-constrained setting Challenges & Risks from the PO perspective

Agile SCRUM in Systems Engineering A Practical Application

Implementing SAFe: A Roadmap

DESJARDINS NEXT DELIVERY APPROACH. New Enterprise in Expansion and Transformation (NeXT) Case Study February 22, 2018

Scrum Alliance. Certified Scrum Professional-Product Owner Learning Objectives. Introduction

Agile Governance. Governance, Risk and Compliance in the Digital Age

Information Technology Project Management, Eighth Edition. Note: See the text itself for full citations.

HELP!!! THE SCRUM MASTER IS THE IMPEDIMENT!

Chapter 3 Agile Software Development

Case Study: How to Eliminate Flaws of Waterfall and Agile Development Processes Using a Hybrid Model

Scrum and Risk. Redefining the Traditional View of Risk, Mark Summers. Copyright 2009 EMC Corporation. All rights reserved.

CM MatchPoint Agile. Christoph Heinrich, CM First Plex Track A / Session 17

Scrum Testing: A Beginner s Guide

Scrum Master / Agile Project Manager An Approach for Personal Competency Development

Case Study: Applying Agile Software Practices to Systems Engineering

Agile & Lean / Kanban

Building Cloud Apps using Agile Methodology & Tools

Agile Beyond Software

Systems Engineering in Large-scale Agile Software Development

De-Mystifying Kanban:

Part 1. Software engineering Facts. CSC 4181 Compiler Construction Software Engineering Lectures. What is software engineering? What is software?

Tuesday, October 25. Announcements

EXIN Agile Scrum Product Owner

The Kanban Guide for Scrum Teams

Designing the Process. A Brief Introduction to Agile Programming

Webinar on Introduction to Scrum and Agile. and. Training for Scrum Fundamentals Certified (SFC ) Certification

THE ADVANTAGES OF AGILE METHODOLOGIES APPLIED IN THE ICT DEVELOPMENT PROJECTS

The Dev Estimate Oil on Canvas. Munch, Edvard. 1887

CASE STUDY INCREASING DRILLING OPERATIONAL PRODUCTIVITY WITH DIGITAL PLATFORMS IN THE OIL & GAS INDUSTRY

High performance software for agile multi-programme management and project management

Processes and Life- Cycles. Kristian Sandahl

LSP METHODOLOGY GUIDE. LSP Group

How to Prepare for and Implement a Project Using Scrum

Agile Beyond Software

Oracle Unified Method (OUM) Using OUM with Agile Techniques. Jan Kettenis Oracle Global Methods Oracle Consulting Netherlands

Introduction to Agile/Extreme Programming

Scrum - Introduction. Petri Heiramo. Agile Coach, CST

Agile at Scale -Beyond SAFe. John B Hudson, B.Sc., PMP, ACP, CSM, SPC

Certified Scrum Master

Ingegneria del Software Corso di Laurea in Informatica per il Management. Scrum. Davide Rossi Dipartimento di Informatica Università di Bologna

How to Accomplish Effectiveness of Six Sigma

Transcription:

EXECUTING LARGE EPC/EPCM PROJECTS USING SCRUM VALUES AND PRINCIPLES

WHAT PROBLEMS NEED SOLVING? Unclear priorities, roles Working in silos Lack of visible progress on what s important and why Lack of accountability to each other Lack of understanding of true state of project

SESSION OUTLINE Background on Gas Plants, EPC/M projects, and WHY Scrum? Applying Scrum to a Large ($1B) EPC Project Scrum Values, Roles, Artefacts, Events Results Applying Scrum to a Large ($3B) EPCM Program Approach to Multiple Organizational Cultures and Concurrent Projects Results Taking it another step

BACKGROUND NATURAL GAS PROCESSING PLANTS AND LARGE EPC/EPCM PROJECTS

WHAT S A GAS PLANT? Processing of Natural Gas Takes feed stock from surrounding wells and removes water, sand, sulphur and other hydrocarbons 400 million cubic feet per day

times ~5 every HOUR

ENGINEERING, PROCUREMENT, & CONSTRUCTION PROJECT Engineering: Deliverables are detailed design and resultant drawings for equipment procurement and construction Procurement: Deliverables are POs resulting in materials on site when they are needed Construction: Deliverable is an operating gas processing plant built safely

COST OF DELAY Delays in Reviews/Approvals things don t get engineered or purchased fast enough therefore they don t arrive on time therefore less time for construction higher risk of delayed ROI

WHAT PROBLEMS NEED SOLVING? Unclear priorities, roles Working in silos Lack of visible progress on what s important and why Lack of accountability to each other Lack of understanding of true state of project

SOUNDS LIKE THE 3 PILLARS OF SCRUM TRANSPARENCY, INSPECTION, AND ADAPTATION

APPLYING SCRUM VALUES/PRINCIPLES TO AN EPC PROJECT BUILDING A $B GAS PLANT

APPLYING SCRUM VALUES scrum.org

STACK RANK PRIORITIZATION OF ISSUES AND MINIMIZING WIP FOCUS

REGULAR FEEDBACK LOOPS ON HOW WE WORK TOGETHER COURAGE

OPENNESS TRANSPARENT ITERATIVE PLANNING AND INSPECTION

WORKING AGREEMENTS RESPECT

COMMITMENT TO GOALS / OUTCOMES NOT PARTICULAR SOLUTIONS COMMITMENT

APPLYING SCRUM ROLES

AN EXISTING ROLE CALLED THE PROJECT MANAGER RESPONSIBLE FOR REGULARLY ESTABLISHING THE PRIORITIES AND CONTEXT FOR THE TEAM PRODUCT OWNER

A NEW ROLE WE CALLED A TEAM FACILITATOR INITIALLY RESPONSIBLE FOR HELPING THE TEAM KEEP AN AGILE MINDSET AND COORDINATING THE TRANSPARENCY OF GOALS, PROGRESS AND IMPEDIMENTS. SCRUM MASTER

A GROUP OF MULTIDISCIPLINARY SPECIALISTS JOINTLY RESPONSIBLE FOR PRODUCING VALUABLE DELIVERABLES TO BE CONSUMED BY THE CONSTRUCTORS DELIVERY TEAM

APPLYING SCRUM ARTEFACTS Product Backlog Sprint Backlog Product Increment

PRODUCT (PROJECT ISSUE) BACKLOG

PRODUCT (PROJECT ISSUE) BACKLOG

SPRINT BACKLOG

PRODUCT INCREMENT

APPLYING SCRUM EVENTS Sprint Sprint Planning Daily Scrum Sprint Review Sprint Retrospective

ITERATION PLANNING

DAILY STAND-UP

ITERATION REVIEW What we accomplished, what has been actualized in the schedule

ITERATION RETROSPECTIVE

RESULTS We were able to gauge progress based on empirical evidence rather than it s on track until it s not We were able to ensure that the team regularly understood what the project priorities were that superseded their respective discipline priorities Transferred techniques to site for Turnover

RESULTS Priority issue cycle time was reduced by a factor of 3. Reduced the overall Project Cycle time by 5-10% The project management team was able to maintain the original project schedule until the plant was sold.

APPLYING SCRUM VALUES/PRINCIPLES TO EPCM BUILDING A PROGRAM OF EPCM GAS PLANTS

RESULTS Plant 1/3 G2S 38 days EARLY Plant 2/3 G2S 86 days EARLY Plant 3/3 G2S 167 days EARLY Program > 10% UNDER budget

Design one build many Concurrent activities Execute vs Oversight

APPROACH TO CULTURE Started as Traditional-based Execution and Scrum-based Oversight NOPE Attempt to shift to a new culture Mission, Vision, Values Patrick Lencioni Transition ownership of Scrum approach to EPC

APPROACH TO COMMUNICATION Scrum of Scrums approach to Program priorities / roadblocks Applying lessons to successive projects in program sprint to sprint 24 hr rule Excel, screen sharing, telephone still not as good as situation room

APPROACH TO WORK PRODUCT Iterative just enough model reviews Breakdown/breakthrough model Seeing the gap between what is predictable and what is desired Challenging the status quo Committing to exceed

THE RESULT OF APPLYING AGILE AND BREAKDOWNS IS THE REALIZATION THAT CHALLENGING THE STATUS QUO AND USING NON- LINEAR THINKING IS REQUIRED FOR SUCCESS. THIS DOESN T SHOW UP IN A GANTT CHART. Team Survey commentary

RESULTS Plant 1/3 G2S 38 days EARLY Plant 2/3 G2S 86 days EARLY Plant 3/3 G2S 167 days EARLY Program > 10% UNDER budget

THE FUTURE OF AGILITY IN EPC/M PROJECTS Source: Leighton Winkler

THE FUTURE IS MINDSET OVER MECHANICS

AN AGILE MINDSET MIGHT ALLOW US TO Automate the schedule progress update process to minimize the time it takes to understand progress [this is akin to continuous integration/testing] Iteratively review and update the schedule logic to ensure it is current and reflects today s reality [this is akin to release planning] Use a floating and fluctuating end date (as scope is usually fixed) to allow the impacts of changes to be seen immediately [this is akin to release planning]

DECLARATION OF INTERDEPENDENCE (PMDOI.ORG) Agile and adaptive approaches for linking people, projects and value We increase return on investment by making continuous flow of value our focus. We deliver reliable results by engaging customers in frequent interactions and shared ownership. We expect uncertainty and manage for it through iterations, anticipation, and adaptation. We unleash creativity and innovation by recognizing that individuals are the ultimate source of value, and creating an environment where they can make a difference. We boost performance through group accountability for results and shared responsibility for team effectiveness.

IN CLOSING Scrum is about feedback loops; ITERATIVELY inspecting and adapting: What we work on How we work together Scrum CAN be applied outside of software with substantial benefit Scrum s success depends on modeling specific values and a growth mindset

MORE QUESTIONS? Simon Orrell, P.Eng. PMP CEC (403) 630-6442 simon@snowdolphin.com www.snowdolphin.com @snowdolphin