GET IN TOUCH

RESOURCES AND SUPPORT

Copyright © Net Objectives, Inc. All Rights Reserved

 
 
 
Summary

SPCs who are guiding one or more groups in adopting SAFe face many challenges including how to start, where to start, and where there are points of flexibility. This online workshop exposes SPCs to FLEX, an approach that is designed around the value stream and always provides an holistic solution. At the end of this online workshop, SPCs will have a good understanding of an approach to adoption that is simple and can expand as the company or adoption grows.

Outline

Here is the outline for this workshop.

  1. Understanding the inherent challenge of scaling 

  2. Understanding flow and value streams and how they relate to kanban boards

  3. Identifying your challenges and seeing options on how to solve them

  4. Reducing size of work, shy MVPs are not sufficient and why Minimum Business Increments can simplify portfolio and product management

  5. SAFe as flow

  6. Creating a road map for improvement: one size does not fit all

  7. Creating ARTs and how they can work together without implementing Full SAFe

  8. Improving coordination between teams

  9. Reducing testing lagging programmers

  10. Improving unclear requirements and why Acceptance Test-Driven Development should usually be early and is not a developer only skill

  11. Using FLEX’s portfolio and product management components with Essential SAFe®

  12. Wrap up

Full Description

This workshop is designed to help SPCs who are guiding organizations that are adopting SAFe and that have one or more groups with up to 300 developers in each group.

Here are challenges that many such SPCs encounter.

  • Complexity which forces starting at the program level and lose the opportunity to improve things immediately with effective portfolio and product management

  • Not being able to break work down into small chunks at the product management level or small stories at the team level

  • The lack of the concept of a minimum business increment for established products which contains all of the aspects of what's needed to deliver while being small enough to release quickly

  • Difficulty of creating ARTs due to interdependencies between the ARTs

  • Unclear requirements

  • Testers lagging developers

This workshop exposes SPCs to the FLEX. At the end of this workshop, SPCs will understand what is involved in using FLEX to have simple adoptions that can expand as the company or adoption grows.

How FLEX differs from SAFe

SAFe is designed for a very large organization and must be used by smaller organizations by taking only a part of it. FLEX is designed as a whole and expands as needed. The design for a complete system is much more complicated than what is needed for a smaller one. If you are not a large organization SAFe suggests taking part of it, based on levels of the organization. The challenge with this is that SAFe's higher levels were designed for large organizations and are very complicated while small organizations still need the concepts in them. SAFe's complexity requires starting with a subset of what is needed and then adding concepts that were likely designed for larger organizations than yours. This is true because even large companies are usually collections of small development groups.

FLEX, on the other hand, is designed around the value stream and always provides an holistic solution. By being organized around the value stream, FLEX provides all of the concepts required regardless of the size of the organization or adoption. This enables simple adoptions which can expand as the company or adoption grows.

Basic configuration of FLEX

If the organization wants to start with more development groups or grows into larger groups, they can just add practices where needed.

Here are several important differences between SAFe and FLEX.

  • How to start. SAFe believes in starting at the program level and expand up. FLEX believes it is often more useful to start with product management. SAFe's complicated product management often makes this difficult to do.

  • Flexibility. SAFe training and adoption is pretty much the same regardless of who is being trained or who is adopting it. This is reflected in the requirement that SPC/Ts not change the material or the order in which it is presented. FLEX is designed as a patterns framework which is organized around the value stream and therefore enables great flexibility.

  • Where to start. SAFe's philosophy is to start at the bottom and work up. In any event it's complexity requires this. FLEX believes in an holistic approach.

A simpler, more effective approach

FLEX offers a simpler, more effective front-end at the team level. This enables you to integrate Essential SAFe with product and portfolio management that does not need to be more complicated that you require.

Workshop Objectives:

Here are the learning objectives for this workshop.

  • Identify what it takes for SAFe to work well within their organization.

  • Understand guidance on creating a simple. effective, portfolio and management system

  • Describe solutions to these challenges.

  • Understand how to create a tailored road map for implementing SAFe.

  • Describe SAFe as a flow model.

Disclaimer

This workshop is neither authorized by Scaled Agile Inc., nor provides any certification related to SAFe.

Prerequisites

SPC or SPC/T certification

Max class size

No limit

Length

Variable

Level

Intermediate

Offering

FLEX for SAFe® Scaled Learning Workshop