How Can Trust Be Gained Between the Business and Development

Find people who share your values, and you'll conquer the earth together.

—John Ratzenberger

Core Values

The four Cadre Values of alignment, built-in quality, transparency, and plan execution represent the fundamental beliefs that are key to Condom's effectiveness. These guiding principles help dictate beliefs and activeness for everyone who participates in a Safe portfolio.

Details

SAFe is based on four principal bodies of knowledge: Active development, Lean product evolution, systems thinking, and DevOps. That makes SAFe broad, deep and scaleable. But at its core, Safe places the highest value on four things:alignment, congenital-in quality, t ransparency, and program execution. These are illustrated in Effigy 1 and described in the following sections.

Effigy ane. SAFe'southward 4 core values

Alignment

Like cars out of alignment, misaligned companies can develop serious problems. They are difficult to steer, and they don't reply well to changes in direction [1]. Even if it's articulate where everyone thinks they're headed, the vehicle is unlikely to become them there.

Alignment is needed to continue step with fast change, confusing competitive forces, and geographically distributed teams. While empowered,Agile Teams are expert (even corking), just the responsibility for strategy and alignment cannot balance with the combined opinions of the teams, no matter how skilful they are. Instead, alignment must rely on the Enterprise concern objectives. Hither are some of the ways how SAFe supports alignment:

Alignment starts with the strategy and investment decisions at thePortfolio level and is reflected in Strategic Themes, Portfolio Vision, the Portfolio Excess, and the outcomes of Participatory Budgeting. In plow, this informs the Vision, Roadmap, and the backlogs at all levels of Rubber. Continuous Exploration with Customer Centricity and Design Thinking gathers the inputs and perspectives from a diverse group of stakeholders and data sources to ensure that the items in the backlogs comprise economically prioritized and refined piece of work, set up for teams to implement. All piece of work is visible, debated, resolved and transparent.
Alignment is supported by articulate lines of content authority, starting with the portfolio and then resting primarily with the Product and Solution Management roles, and extending to the Product Owner part.
PI Objectives and Iteration Goals are used to communicate expectations and commitments.
Cadence and synchronization are practical to ensure that things stay in alignment, or that they migrate merely within reasonable economic and time boundaries.
Architectures and user experience guidance and governance help ensure that the Solution is technologically sound, robust, and scalable.
Economic prioritization keeps stakeholders engaged in continuous, agreed-to, rolling-moving ridge prioritization, based on the electric current context and evolving facts.

Alignment, however, does not imply or encourage acme-down command and command. Alignment occurs when everyone is working toward a common direction. Indeed, Alignment enables empowerment, autonomy, and Decentralized Controlling, allowing those who implement value to brand better local decisions.

Congenital-in Quality

"Inspection does not improve the quality, nor guarantee quality. Inspection is too late. The quality, expert or bad, is already in the product. Quality cannot be inspected into a production or service; it must be built into it."

—Westward. Edwards Deming

Born Quality ensures that every chemical element and every increase of the solution reflects quality standards throughout the development lifecycle. Quality is not "added later." Building quality in is a prerequisite of Lean and flow—without it, the system will probable operate with big batches of unverified, unvalidated work. Excessive rework and slower velocities are likely results.

Also the bigger the organisation, the more of import endemic quality is, so there can exist no ambiguity about the importance of built-in quality in large-calibration systems. It is mandatory. Congenital-in quality is a major foundational chemical element of SAFe, and since it's impossible to localize the quality discussion to every specific action or artifact that affects quality, the Safety Built-in Quality article organizes quality thinking around 5 specific aspects—Menses, Compages and Design Quality, Code Quality, System Quality and Release Quality, as Figure 2 illustrates.

Figure ii. Five main dimensions of Built-In Quality

The DevOps article provides deeper technical guidance for DevSecOps practices that ensure build-in quality and security are integral to how enterprises develop software-based solutions. In addition, these articles are augmented by three Advanced Topic articles, Agile Testing, Behavior-Driven Development (BDD) and Test-Driven Evolution. Together, this ready of articles provides a adequately comprehensive starting point for achieving built-in quality in large systems.

Transparency

Solution development is hard. Things go incorrect or exercise not piece of work out every bit planned. Without openness, facts are obscure and controlling is based on speculative assumptions and lack of data. No one tin can ready a secret.

To ensure openness—trust is needed. Trust exists when the business and development can confidently rely on another to deed with integrity, particularly in times of difficulty. Without trust no 1 can build loftier-performance teams and programs, nor build (or rebuild) the confidence needed to make and come across reasonable commitments. And without trust, working environments are a lot less fun and motivating.

Building trust takes fourth dimension. Transparency is an enabler of trust, provided through several SAFe practices:

Executives, Lean Portfolio Management, and other stakeholders can run across the Portfolio Kanban and plan backlogs, and they accept a articulate agreement of the PI Objectives for each Agile Release Railroad train or Solution Train.
ARTs have visibility into the team's backlogs, every bit well as other Plan Backlogs.
Teams and programs commit to short-term, visible commitments that they routinely meet.
Inspect and Conform occurs with all relevant stakeholders and creates backlog improvement items from lessons learned.
Teams and Agile Release Trains (ARTs) can see portfolio business and enabler Epics. They have visibility into new initiatives.
Progress is based on objective measures of working solutions. (Principle #5)
Everyone can sympathize the velocity and WIP of the teams and programs; strategy and the ability to execute are visibly aligned.
Programs execute reliably, as noted below.

Lean-Active Leaders also play a critical function in creating an environment that fosters trust and transparency.

Program Execution

Of form, none of the residuum of Safe matters if teams can't execute and continuously deliver value. Therefore, Condom places an intense focus on working systems and business outcomes. History shows us that while many enterprises start the transformation with individual Agile teams, they frequently go frustrated as even those teams struggle to deliver more substantial amounts of solution value, reliably and efficiently.

That is the purpose of the Art, and that is why Prophylactic focuses implementation initially at Essential SAFe. In turn, the ability of Value Streams to deliver value depends on the ability of the ARTs and Solution Trains.

Simply withalignment, transparency, and built-in quality on the team's side, they have a little 'wind at their back.' That enables a focus on execution. And if they struggle—and they will, considering circuitous solution evolution is difficult—they have the cornerstone of the Inspect and Arrange workshops. In that way, they close the loop and execute meliorate and better during each Programme Increase.

Leadership is Required

Successful scaled Lean-Agile evolution and these four core values crave the active support ofLean-Agile Leadership and a Continuous Learning Culture. Leaders couple these core values with SAFe Lean-Active Principles and practices and an orientation toward creating value for customers. In plow, that creates a persistent and meaningful civilisation for the teams and their stakeholders.

This is the way successful teams and programs are doing it, and that'south why they are getting the many benefits—employee engagement, productivity, quality, and time to market—that Lean-Agile enterprises then savour.

Learn More

[1] Labovitz, George H., and Victor Rosansky. The Power of Alignment : How Not bad Companies Stay Centered and Accomplish Extraordinary Things. Wiley, 1997.

[2] Manifesto for Software Development. http://AgileManifesto.org

[3] Oosterwal, Dantar P. The Lean Machine: How Harley-Davidson Drove Top-Line Growth and Profitability with Revolutionary Lean Product Evolution. Amacom, 2010.

Last update: ten February 2021

The information on this page is © 2010-2022 Scaled Agile, Inc. and is protected by Usa and International copyright laws. Neither images nor text tin can be copied from this site without the limited written permission of the copyright holder. Scaled Agile Framework and Rubber are registered trademarks of Scaled Agile, Inc. Please visit Permissions FAQs and contact us for permissions.