Agile Management of Mega-Projects

Slides:



Advertisements
Similar presentations
Im an Agile Test Manager: Do I really exist? A discussion and debate David Evans & Ivan Ericsson SQS Group Limited Test Management Forum London, 24th October.
Advertisements

Delivering Enterprise Projects Using Agile Methods Brent Barton May 23, 2006.
PROC-1 3. Software Process. PROC-2 What’s a process? Set of activities in creating software It involves creativity –hard to automate –Requires human judgment.
SCRUM John Drew. SCRUM - overview Scrum is a project management discipline that has evolved since the early 1990s to deliver software that meets business.
SDLC Nilesh Gangrade Feb 26th, Agenda Project Vs Product Vs Process Project Vs Product Vs Process Project Engagements Project Engagements Client.
Scrum Master & Agile Project Manager: A Tale of Two Different Roles
Introduction to Agile.
Agile Assimilation & Scaling. 2  About me…  How did we start?  Bottom-up  Task Force  Learning  Pilots  First stage analysis + recommendations.
Testing Challenges in an Agile Environment Biraj Nakarja Sogeti UK 28 th October 2009.
Agile Methodologies: Comparative Study and Future Direction 林佳蓁 資工 4B.
CMS 00_ Copyright 2002 Raytheon Company All Rights Reserved CMMI – What a Difference a Sponsor Makes! Ann Turner Raytheon Company
Martin Cryer Software Development. ‹#› Development Processes Traditional e.g. Waterfall Method Agile –Design Build (Quick to Market) –Combines Engineering,
SOFTWARE ENGINEERING MCS-2 LECTURE # 3. SOFTWARE PROCESS  A software development process, also known as a software development life- cycle (SDLC), is.
.com Software Testing Tutorials “Basics for beginners. Fundamentals for everyone.” Welcome to Day 4. We will start at 4:35 PM PST. Software Testing Tutorials.
Chapter 2 Iterative, Evolutionary, and Agile You should use iterative development only on projects that you want to succeed. - Martin Fowler 1CS
Sprint Plans and Burndown Charts David Millard | davidmillard.org.
Dr. Rob Hasker. What if every project used Scrum?  Why might Scrum not be perfect for every project? Hard to get the big picture Early choices may have.
Software Testing Process
10 key principles of agile software development
Intelligence and Information Systems 1 3/17/2004 © 2004 Raytheon Company USC/CSE Executive Workshop on Agile Experiences March 17, 2004 A Raytheon Agile.
Meghe Group of Institutions Department for Technology Enhanced Learning 1.
Dr. Rob Hasker. Should every project use Scrum?  When might Scrum not be an appropriate model?  What are some of its limitations? Hard to get the big.
Introduction to Project management and Principles.
Agile Project. Agile - Project proj·ect präj ˌ ekt noun an individual or collaborative enterprise that is carefully planned and designed to achieve a.
The Security Sprint By Ramnath Cidambi. Agile and DevOps DevOps is a “recent” concept though the building blocks have existed for a while – The understanding.
Barnes & Noble Alonda Morgan. Agile UX Agile.
Project Management Finals Lesson 1 - Principles - Techniques - Tools.
CS223: Software Engineering
DevOps for the IT Pro with Azure and Visual Studio Team Services
Flight Software Conference 2016
Methodologies and Algorithms
WEBINAR Use Portfolio Management To Build Resource Agility
CSC 355 – Newer Approaches to System Development Life Cycles & Processes, Spring 2017 March 2017 Dr. Dale Parson.
Chapter 1: Introduction to Systems Analysis and Design
Game Design, Development, and Technology
Waterfall, Agile & Scaling Agile
Sample Wiki Comments?.
Ernest Cachia Department of Computer Information Systems
Spring 2013 Advising Starts this week.
Владимир Гусаров Директор R&D, Dell Visual Studio ALM MVP ALM Ranger
Agile Software Development Brian Moseley.
Information Technology Project Management – Fifth Edition
SAFe Workshop - Oct 17 Presenter: Ray Brederode
Software Process Models
Agile Fundamentals Logo Here.
CS 577b: Software Engineering II
Client Management Managing Client Expectations
Impact of Agile Methodology on Software Architecture
Process Improvement With Roles and Responsibilities explained
Introduction to Software Engineering
Fast, Agile, Simple Decemebr 2017 Think Simple, Run Faster.
How to Successfully Implement an Agile Project
Focus Areas for Investment
Developing Maximum Value
Agile Philly: Estimating Vs Forecasting Using a Monte Carlo Tool
TAXAND ASIA SENIOR SCHOOL AUG 2018 KUALA LUMPUR MALAYSIA
Agile practices for documentation teams
Real World Scrum with TFS & VSTS / Azure DevOps
SOFTWARE LIFE-CYCLES Beyond the Waterfall.
Chapter 1: Introduction to Systems Analysis and Design
How to deal with requirements in an Agile context?
Planning the Prepare Stage
Chapter 1: Introduction to Systems Analysis and Design
EA in an Agile/DevOps World
System Development Methods
Agile, Scrum and CMMI Methodologies
Open Source Tool Based Automation solution with Continuous Integration and end to end BDD Implementation Arun Krishnan - Automation Manager Maria Afzal-
Integrating Key Business Metrics
What makes a Good Agile Team
Product Development & Planning
Presentation transcript:

Agile Management of Mega-Projects March 2018 Think Simple, Run Faster

Agenda What is Agile and when should we use it What is a mega-project and why it is not agile TMG – Tactical Management Group Recreating Agile conditions Tool for the Job

Agile Edge Conditions Agile Region Hard Civil Infrastructure Construction Military/Aerospace Assembly M&A Legal Semi-conductors Dependency type PCB HR-intense Industrial controls Firm-ware Re-org SW Agile Region IT Soft .com Cheap Error fixing cost Expensive

VUCA Pressure Market Needs Market Expects VUCA “Requirements change faster then we can deliver, and stakeholders expects us to keep up, because they understand there are no hard limits”

Agile Elements for dealing with VUCA Fast “market” feedback (extreme TTM) Short term focus* Design on-the-fly Independent team *In Israel it is the alternative to no planning, rather then long term planning that is too rigid

Mega-Project Expensive: 100s of man-years / $B in tangibles Complicated: Many teams, many sites, many stakeholders Long: Years of work, often with strict deadlines Dependencies between many moving parts Mistakes can be very costly Very waterfall

TMG: Tactical Management Group Mgmt. TMG Work Teams Closely-knitted leadership for the project 360 view: PM, PO, Dev, QA, Arch, UX, IT… Create Agile conditions for work teams (feedback, independence, less docs, focused work)

Get fast to Feedback Requirements Specifications Develop Integrate Test Deploy MVP with Excellent Design Feedback-based incremental iterations

Excellent MVP Design & Execution Value Mgmt. Tangible Design Stake-holder feedback (miniDR) Tactical Arch. Rough Planning Develop MVP with Excellent Design Well-Groomed Backlogs TMG Sprints

Value Management Do! Really Try Delay Don’t Focus Matrix 5 8 1 6 Business Value 3 2 4 7 9 5 Cost, Risk, Effort

Tactical Architecture Minimize dependencies Split to sub-parts: projects, products, services Single site/team as owner Small number of integration milestones

Rough Planning Back-of-the-envelope capacity planning Capture Main dependencies Understand general timeline and budget Track changes

Tangible design & Stakeholder feedback

TMG Tracking: MSM Milestones Risks Budget Stakeholders Changes Action Items

Summary Mega-projects are not naturally Agile We can (sometimes) re-create Agile environment The reward is very high: TTM, focus, control, value TMG is a key success factor A good tool can really help

Thanks, and keep it…