Skip to main content

SAFe Agile Principles

 SAFe (Scaled agile framework) is based on ten immutable, underlying Lean-Agile principles. These tenets and economic concepts inspire and inform the roles and practices of SAFe.

1 – Take an economic view:

  • Fundamental understanding of the economics of the building system
  • Strategy for incremental value delivery
  • Risk
  • CoD (Cost of Delay)
  • Costs (manufacturing, operational, and development costs)
  • Operate within the context of an approved budget

2 – Apply systems thinking

  • Understanding complex system
  • Addressing the challenges in the workplace and the marketplace requirement
  • Apply thinking on system under development and the organization that builds the system
3 – Assume variability; preserve options
  • Single design-and-requirements option is wrong choice for the future
  • Future adjustments take too long and can lead to lot of design change.
  • In SAFe Agile, maintain multiple requirements and design options for a longer period in the development cycle
4 – Build incrementally with fast, integrated learning cycles
  • Developing solutions incrementally in a series of short iterations allows for faster customer feedback and mitigates risk.
  • Develop prototypes
  • Develop MVPs (Minimum Viable Product)
  • Based on early, fast feedback, take alternative course of action
5 – Base milestones on objective evaluation of working systems
  • To deliver economic benefit Business owners, developers, and customers have a shared responsibility for the success of the system
  • Integration points provide objective milestones at which to evaluate the solution throughout the development life cycle
  • Regular evaluation of milestone will provide success, profit, on-time delivery of the system
6 – Visualize and limit WIP, reduce batch sizes, and manage queue lengths
  • Overloading teams and programs with more work than they can accomplish is a common and harmful practice. 
  • Limit the amount of work in process (WIP) to get timely delivery from the team
  • To take up new functionality, reduce the batch sizes of the work
7 – Apply cadence, synchronize with cross-domain planning
  • Cadence creates predictability and provides a rhythm for development.
  • Applying development cadence and synchronization, coupled with periodic cross-domain planning.
  • It provides the mechanisms needed to operate effectively in the presence of the inherent development uncertainty.
8 – Unlock the intrinsic motivation of knowledge workers
  • Lean-Agile leaders understand that ideation, innovation, and employee engagement are not generally motivated by individual incentive compensation. 
  • Such individual incentives can create internal competition and destroy the cooperation necessary to achieve the larger aim of the system.
  • Providing autonomy and purpose, minimizing constraints, creating an environment of mutual influence, and better understanding the role of compensation are keys to higher levels of employee engagement. This approach yields better outcomes for individuals, customers, and the enterprise.
9 – Decentralize decision-making
  • Decentralize decision-making.
  • This reduces delays, improves product development flow, enables faster feedback.
  • Take more innovative solutions designed by those closest to the local knowledge
  • Some decisions are strategic, global, and have economies of scale that justify centralized decision-making
  • Both decision-making helps creating a reliable decision-making.
10 – Organize around value
  • Need to respond to the needs of its customers with new and innovative solutions.
  • These solutions require cooperation amongst all the functional areas, with their incumbent dependencies, handoffs, waste and delays.
  • Deliver value more quickly.
  • When market and customer demands change, the enterprise must quickly and seamlessly reorganize around that new value flow.




Labels:

Comments

Post a Comment

Popular posts from this blog

Certified Enterprise Architect Professional (CEAP) - Module 4 - Architecture Precursors

 Architecture Precursors: Precursors to modern Enterprise Architecture (EA) include early frameworks like IBM's Business Systems Planning (BSP), which focused on aligning business strategy with information systems, as well as other Information Systems (IS) architecture methodologies that emerged in the 1970s and 80s, emphasizing the connection between business processes and IT systems, laying the groundwork for the holistic view of an organization that EA represents today; the "Master Plan for Information Systems" by Evans and Hague is also considered a foundational concept in this area. Drivers: internal / external pressure enforce to change the system Aims & Directives: Aims:  Goals Objectives Requirements Directives: Principles (example: Principles can be associated with business, data, applications, infrastructure, or security) Policies (example: Members of the public have minimal access to data) Business Rules (example: A rule directs and restricts a procedure)
Post a Comment
Read more

Scaled Agile Framework (SAFe)

The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns for implementing agile practices at an enterprise scale. The framework is a body of knowledge that includes structured guidance on roles and responsibilities, how to plan and manage the work, and values to uphold. Scrum is a simple, flexible approach to adopting Agile that's great for small teams. SAFe is an enterprise-wide Agile framework designed to help bring Agile beyond the team and into the company as a whole. Scaled Agile has built a comprehensive level that includes all the four layers called the team, program, large solutions, and portfolio level. 4 Layers: Portfolio - Strategy, Vision, Roadmap, Strategy goal, Decision making, Budget, Portfolio level metrics,  Program - Align multiple teams towards a common mission, Bring together all the Agile teams, transparency, collaboration, and synchronisation, Scrum of Scrums, Product Owners to define the overall vision. Large Solutions - ar...
Post a Comment
Read more

4 T's - Technology, Time, Teamwork, Transparency

 1) Technology: Software development technologies are the tools and methods that developers use to design, develop, test, and deploy software applications. These include a wide range of software technologies, such as programming languages, frameworks and libraries, databases, and cloud computing platforms. 2) Time: A timebox is a fixed time period within which a deliverable must be produced in a project management context. It's a time management technique that involves dividing time into individual time periods, each with its own goal, duration, and deadline. Timeboxes are self-contained calendar events that can't be extended once they've started. The fundamental principle of timeboxing is that time in timeboxes can't shift, and once the time runs out, work must stop, even if the task isn't finished.  3) Teamwork: Teamwork in project management is a measure of how well a project's team works together to achieve a goal. It involves collaboration, communication, a...
Post a Comment
Read more