Demystifying SAFe.

Slides:



Advertisements
Similar presentations
© 2007 BigVisible Solutions, Inc. All Rights Reserved Coaching Solutions Agile Project Start v
Advertisements

©2013 Responding to Change Zach Nies – Chief Technologist.
ECE44x SCRUM Overview slides adapted from Marty Stepp
Agile Project Management with Scrum
SCRUM John Drew. SCRUM - overview Scrum is a project management discipline that has evolved since the early 1990s to deliver software that meets business.
Project Management with TFS 1. What TFS offers for Project Management? Work Item tracking 2 Portfolio backlog Backlog Issue tracking Feature Product Backlog.
©2013 Scaling Agile With SAFe August 13, 2013.
Atlassian Africa South Africa 2015 Jonathan Singh.
Agile Software Engineering Frank Maurer Agile Software Engineering Lab, University of Calgary
Discover how to improve productivity by going DevOps and SAFe.
If Agile had Oscars, which of its principles would qualify as “leading” vs “supporting?” David Greene BEFORE THE TALK:
Introduction to Agile.
Gaining Support for a Sustainable Agile Transformation Dennis Stevens, VP Enterprise Engagements LeadingAgile November 12, 2013.
WHY AGILE IS FAILING IN LARGE ORGANIZATIONS twitter.com/mcottmeyer facebook.com/leadingagile.
Principles of Object Technology Module 1: Principles of Modeling.
Software Engineering- Scrum 徐 瑋 Alen 林芳瑜 Flora 1.
Object Oriented Analysis and Design Introduction.
The Successful Business Analyst’s Role in the Scaled Agile Framework®
MAKING BUSINESS AGILE Andrew Kallman, MBA, PMP, CSP 21 March 2013 NYC Scrum Users Group AGILE PROGRAM MANAGEMENT USING THE UNIFIED VISION FRAMEWORK.
Theories of Agile, Fails of Security Daniel Liber CyberArk.
1 confidential | ©2015 Sabre GLBL Inc. All rights reserved. Implementing Kanban at Different Levels During Agile Adoption Krishnakumar C Principal Agile.
Enterprise Agile #LAKC2015.
OSEHRA Architecture Work Group Meeting January 19 th, 2016 Discussion on Veteran-focused Integration Process (VIP) Jack Taylor, M.D., Chief Medical Information.
Teaching slides Chapter 2. Chapter 2 Software Engineering Methodologies Introduction Why a methodology? Agile methodologies Waterfall model Rational Unified.
© 2013 CA. All rights reserved. ScrumOps – Scaling Scrum Environment for DevOps Serajul Arfeen Naveen Arora July 2014.
Leffingwell et al. © 2015 Scaled Agile, Inc. All Rights Reserved 1 Foundations of the Scaled Agile Framework ® Values, Principles, Practices, Implementation.
Overview + Digital Strategy + Interactive Engineering + Experience Design + Product Incubation + Data Visualization and Discovery + Data Management.
1 © 2016 Scaled Agile, Inc. All Rights Reserved. V4.0.0 © 2016 Scaled Agile, Inc. All Rights Reserved. What’s New in SAFe ® 4.0? An Overview.
1 © 2016 Scaled Agile, Inc. All Rights Reserved. V4.0.0 © 2016 Scaled Agile, Inc. All Rights Reserved. Foundations of the Scaled Agile Framework ® 4.0.
NAPA Agile Story: From Zero to Hero in Two Years Toivo agilehope.blogspot.com #NAPA #SAFe.
Introduction to Agile. Introduction Who is this guy?
Managing Agile Software Development Teams Using Scrum AKA: Wrangling Developers for Fun and Profit!
Lean Agile Community of Practice April Shimitz 11/19/2014.
What’s New in SAFe® 4.0? An Overview
Embedded Systems Software Engineering
Teaching slides Chapter 2
Agile Project Management
The Strategic Role of Information Development in Continuous Delivery
Project Management with VSTS
CSC 355 – Newer Approaches to System Development Life Cycles & Processes, Spring 2017 March 2017 Dr. Dale Parson.
CIM Modeling for E&U - (Short Version)
Fundamentals of Business Analysis
Testing journey in Scaled Agile Framework®
Software Development methodologies
The more Agile you are the more you are In Control………..
A Walkthrough of the Scaled Agile Framework®
Unified Process Source & Courtesy: Jing Zou.
Information Technology Project Management – Fifth Edition
By: By: Agile Scrum Master Online Training.
Requirements and User Stories
Navigating an Agile Transformation
CS 577b: Software Engineering II
Scaled Agile Hot Topics
Scaled Agile Requirements: What, When & How
A Walkthrough of the Scaled Agile Framework®
Introduction to Software Engineering
Agile Development and the Scaled Agile Framework
Tim Hirner - Flagship Speakers January 23, 2014
Sample Agile Assessment Report for XYZ Company
Burn Down charts for Project Management
Decomposition.
Teaching slides Chapter 1.
Introduction If you have got a call for an Agile testing interview, then congratulations are in order. You may be feeling nervous, but it sure to be felt.
Introduction to Agile Blue Ocean Workshops.
SAFe overview.
Scaled Agile Frameworks
Agile Development.
Chapter 4: Software Process Models
International Institute of Business Analysis
Product Development & Planning
Presentation transcript:

Demystifying SAFe

Introductions… How much do you know about agile? What is your role?

What have you heard about SAFe?

”The boys from RUP (Rational Unified Process) are back ”The boys from RUP (Rational Unified Process) are back. Building on the profound failure of RUP, they are now pushing the Scaled Agile Framework (e) as a simple, one-size fits all approach to the agile organization. They are touting their processes and tools this week at Agile 2013 in Nashville. They would be at the RUP conference, but there are none. They would be at a waterfall conference, but they are no longer. So they are at our conference. Strange, but they had nowhere else to go. Try to be polite.”

Roots, past, present and future Field experience at enterprise scale 2011 Now… 3.0 LSE 2.0 4.0 4.5 1.0 Agile development | Lean product development | Systems thinking The Framework is based on a huge body of knowledge – Lean Thinking, Lean Product Development, Systems Engineering and Agile to name a few. The knowledge of the Framework isn’t a one time learning event. It’s an on-going process. The Framework is constantly being updated to stay current. Previously we’d release more frequent updates. Now there is once a year release cycle on the “Big Picture” . Pace of innovation still remaining constant, we are still continually updating with what we learn. We’ve just slowed down the updates of the UI only (is updated annually)

© Scaled Agile Inc 2016 All rights reserved

The Levels © Scaled Agile Inc 2016 All rights reserved

© Scaled Agile Inc 2016 All rights reserved

The People © Scaled Agile Inc 2016 All rights reserved

OVERVIEW: In this slide, you can explain that, at first glance, the Framework may appear complicated. However, you can provide assurance that you will take them through it in a logical manner. SAMPLE SPEAKER NOTES: This is what is referred to as the “SAFe Big Picture”. At first, it may look complicated, but as we will see, it is actually a very straight-forward and logical representation. We will see that roles, artifacts, and activities are clearly defined based on proven principles and practices. Decomposing the SAFe Big Picture into it’s constituent parts, we’ll discover that it’s a simple, powerful and easily understood framework for managing complex software and systems development.   © Scaled Agile Inc 2016 All rights reserved

The Backlogs © Scaled Agile Inc 2016 All rights reserved

OVERVIEW: In this slide, you can explain that, at first glance, the Framework may appear complicated. However, you can provide assurance that you will take them through it in a logical manner. SAMPLE SPEAKER NOTES: This is what is referred to as the “SAFe Big Picture”. At first, it may look complicated, but as we will see, it is actually a very straight-forward and logical representation. We will see that roles, artifacts, and activities are clearly defined based on proven principles and practices. Decomposing the SAFe Big Picture into it’s constituent parts, we’ll discover that it’s a simple, powerful and easily understood framework for managing complex software and systems development.   © Scaled Agile Inc 2016 All rights reserved

Capabilities are broken down into Features. OVERVIEW: Here, you can introduce the Enterprise Backlog Model consisting of the Portfolio, Value Stream, Program, Team, and Sprint backlogs. You can also elaborate on the artifacts and roles which influence the creation and prioritization of the backlog items, such as Strategic Themes, the Vision, and the Roadmap. SAMPLE SPEAKER NOTES: There are four levels of backlogs which comprise the Enterprise Backlog Model: the Portfolio Backlog which contains Epics, Solution Backlog which contains capabilities, the Program Backlog which contains Features, and the Team Backlog which contains Stories The backlogs contain prioritized functionality and enablers. Enablers are the exploration, architecture, and infrastructure needed to support the functionality. Epics are identified and progressively elaborated as they flow through the Portfolio Kanban System. The Kanban System makes the strategic business initiatives visible and brings a structured analysis process driven by economics. There are Kanban Systems at the Value Stream and Program Levels, as well. Epics are broken down into Capabilities. Prioritization is guided by the Vision and Roadmap. We’ll take about prioritization later. Capabilities are broken down into Features. Features are then broken down into Stories which are executed by the Agile teams. However, this isn’t a strict hierarchy. A Capability, Feature, or Story may emerge within the context of the Value Stream, Program, or Team and not have a parent. © Scaled Agile Inc 2016 All rights reserved

The Cadence © Scaled Agile Inc 2016 All rights reserved

OVERVIEW: In this slide, you can explain that, at first glance, the Framework may appear complicated. However, you can provide assurance that you will take them through it in a logical manner. SAMPLE SPEAKER NOTES: This is what is referred to as the “SAFe Big Picture”. At first, it may look complicated, but as we will see, it is actually a very straight-forward and logical representation. We will see that roles, artifacts, and activities are clearly defined based on proven principles and practices. Decomposing the SAFe Big Picture into it’s constituent parts, we’ll discover that it’s a simple, powerful and easily understood framework for managing complex software and systems development.   © Scaled Agile Inc 2016 All rights reserved

Build in Quality © Scaled Agile Inc 2016 All rights reserved

OVERVIEW: In this slide, you can explain that, at first glance, the Framework may appear complicated. However, you can provide assurance that you will take them through it in a logical manner. SAMPLE SPEAKER NOTES: This is what is referred to as the “SAFe Big Picture”. At first, it may look complicated, but as we will see, it is actually a very straight-forward and logical representation. We will see that roles, artifacts, and activities are clearly defined based on proven principles and practices. Decomposing the SAFe Big Picture into it’s constituent parts, we’ll discover that it’s a simple, powerful and easily understood framework for managing complex software and systems development.   © Scaled Agile Inc 2016 All rights reserved

Relentless Improvement © Scaled Agile Inc 2016 All rights reserved

OVERVIEW: In this slide, you can explain that, at first glance, the Framework may appear complicated. However, you can provide assurance that you will take them through it in a logical manner. SAMPLE SPEAKER NOTES: This is what is referred to as the “SAFe Big Picture”. At first, it may look complicated, but as we will see, it is actually a very straight-forward and logical representation. We will see that roles, artifacts, and activities are clearly defined based on proven principles and practices. Decomposing the SAFe Big Picture into it’s constituent parts, we’ll discover that it’s a simple, powerful and easily understood framework for managing complex software and systems development.   © Scaled Agile Inc 2016 All rights reserved

Value Delivery © Scaled Agile Inc 2016 All rights reserved

OVERVIEW: In this slide, you can explain that, at first glance, the Framework may appear complicated. However, you can provide assurance that you will take them through it in a logical manner. SAMPLE SPEAKER NOTES: This is what is referred to as the “SAFe Big Picture”. At first, it may look complicated, but as we will see, it is actually a very straight-forward and logical representation. We will see that roles, artifacts, and activities are clearly defined based on proven principles and practices. Decomposing the SAFe Big Picture into it’s constituent parts, we’ll discover that it’s a simple, powerful and easily understood framework for managing complex software and systems development.   © Scaled Agile Inc 2016 All rights reserved

But wait there’s more!

So what could possibly go wrong?!?

CoP’s meetups conferences job aids forums training fun