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 5 - Architecture Frameworks

Architecture Frameworks: An Architecture Framework is a theoretical structure that has the purpose of developing, executing, and maintaining an Enterprise Architecture. Advantages of EA framework: Simplify Breaks down areas of the business process Organise business components and create and identify relationships between business Determine the scope Customization in the existing framework Disadvantages of EA framework: Need to follow process Provides only direction and not information It's based on goal and objective Need creativity and proactive thinking Zachman Framework: The Zachman Framework is a widely used model in Enterprise Architecture (EA) that provides a structured way to classify and organize an organization's information infrastructure by defining different perspectives from various stakeholders, allowing for a holistic view of the enterprise and facilitating alignment between business needs and technology solutions; essentially acting as a template to organize arc...
Post a Comment
Read more

Daily Agile Scrum stand-up meeting guidelines

Followers of the Scrum method of project management will typically start their day with a " stand-up meeting ". In short, this is a quick daily meeting (30 minutes or less) where the participants share the answers to the three questions with each other: • What did I accomplish yesterday?  • What will I do today?  • What obstacles are impeding my progress?  Some people are talkative and tend to wander off into Story Telling .  Some people want to engage in Problem Solving immediately after hearing a problem. Meetings that take too long tend to have low energy and participants not directly related to a long discussion will tend to be distracted. These are the minimum number of questions that satisfy the goals of daily stand-ups. Other topics of discussion (e.g., design discussions, gossip, etc.) should be deferred until after the meeting.  Here are few tips for running a smooth daily meeting:  • Everyone should literally stand-up and no one should sit down ...
Post a Comment
Read more

Empiricism (Scrum)

Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Pillars of  Empiricism . Various practices exist to forecast progress, like burn-downs, burn-ups, or cumulative flows. While proven useful, these do not replace the importance of empiricism . In complex environments, what will happen is unknown. Only what has already happened may be used for forward-looking decision making. Each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured: ● For the Product Backlog it is the Product Goal. ● For the Sprint Backlog it is the Sprint Goal. ● For the Increment it is the Definition of Done. These commitments exist to reinforce empiricism . The sum of the Increments is presented at the Sprint Review thus supporting empiricism .
Post a Comment
Read more