Search

Leading Safe Filter

Introduction to Scaled Agile Framework (SAFe®)

Implementation of software solutions vary based on complexity and magnitude. Not all implementations are simple and straightforward. Software solution implementations of enterprise scale require more rigorous processes and streamlined practices to allow businesses to address challenges posed during such engagements. Businesses are also required to take up such challenging implementations while operating in challenging business environments which forces them to implement solutions in the shortest sustainable lead time. Best practices for scaled agile framework tells you principles which can benefit the organisation As we all know, the change-driven approaches of Agile project management came into being to address the problems in traditional long running plan-driven software projects. But, Agile projects were traditionally more suitable for smaller projects that required six to eight team members. So, the need for a process to deliver large scale projects using Agile methodologies increased over the last few years. The scaled agile framework provided the much needed guidance for the same. Reason for SAFe® The primary motivation for SAFe® was to allow for collaboration, synchronization and coordinated delivery of solutions developed by multiple Agile teams. SAFe® is a framework that can be scaled up or down as per the requirements of the organization. Thus, SAFe® supports small-scale solution implementations which require 50 to 125 team members as well as complex, cross departmental and even cross-organizational solution implementations that require thousands and ten thousands of team members. How does SAFe® work? It is fascinating to understand how SAFe® facilitates scaling of this magnitude? SAFe® framework describes roles, responsibilities, artifacts and activities that are required to develop and deploy software solutions Lean-Agile software implementation principles. SAFe® principles are developed using 3 main bodies of knowledge. They are as depicted in the diagram below.  Agile development embraces change where cross-functional, self-organizing and self-healing teams develop software in an iterative and incremental manner using small bursts called sprints.  “Systems thinking” motivate team members to consider each and every element that are within the context as a whole. For example the business context for which a solution is being developed may involve factors internal to a business such as data, systems, technology, resources (financial and non-financial) as well as factors which are external such as competitors, government and regulatory bodies, suppliers and distributors, financial institutions etc. which may all impose constraints on the solution. One of the key principles in Agile methodologies involves lean principles which is to minimize waste or non-value adding activities and to increase the probability and impact of value-adding activities.  Common questions, which SAFe® addresses   SAFe® was developed to address the following industry wide questions. How can organizations scale agile practices starting from small agile project teams, to larger programs, to business unit or enterprise wide programs or portfolios and even to cross-organizational mega projects? How can teams of scale be organized around continuous delivery of value? How can teams of such magnitude collaborate effectively avoiding delays and bureaucracy evident in such large scale projects if run as traditional projects? How can dependencies between multiple teams be managed? How can an environment that fosters collaboration, continuous improvement and innovation be created and sustained? How can culture be molded to motivate team members to make mistakes and learn from them? How can the team measure success of new working methods followed and how can they make it more efficient? SAFe® provides a well-defined set of values, principles and practices which can be adopted enterprise-wide to better address these questions above. In my upcoming articles I will discuss about different configurations of SAFe® with details on how different roles, systems, practices and values contributes towards continuously delivering value through the agile release train.

Introduction to Scaled Agile Framework (SAFe®)

3916
Introduction to Scaled Agile Framework (SAFe®)

Implementation of software solutions vary based on complexity and magnitude. Not all implementations are simple and straightforward. Software solution implementations of enterprise scale require more rigorous processes and streamlined practices to allow businesses to address challenges posed during such engagements. Businesses are also required to take up such challenging implementations while operating in challenging business environments which forces them to implement solutions in the shortest sustainable lead time. Best practices for scaled agile framework tells you principles which can benefit the organisation

As we all know, the change-driven approaches of Agile project management came into being to address the problems in traditional long running plan-driven software projects. But, Agile projects were traditionally more suitable for smaller projects that required six to eight team members. So, the need for a process to deliver large scale projects using Agile methodologies increased over the last few years. The scaled agile framework provided the much needed guidance for the same.

Reason for SAFe®

The primary motivation for SAFe® was to allow for collaboration, synchronization and coordinated delivery of solutions developed by multiple Agile teams. SAFe® is a framework that can be scaled up or down as per the requirements of the organization. Thus, SAFe® supports small-scale solution implementations which require 50 to 125 team members as well as complex, cross departmental and even cross-organizational solution implementations that require thousands and ten thousands of team members.

How does SAFe® work?

It is fascinating to understand how SAFe® facilitates scaling of this magnitude? SAFe® framework describes roles, responsibilities, artifacts and activities that are required to develop and deploy software solutions Lean-Agile software implementation principles. SAFe® principles are developed using 3 main bodies of knowledge. They are as depicted in the diagram below.

 Agile development embraces change where cross-functional, self-organizing and self-healing teams develop software in an iterative and incremental manner using small bursts called sprints. 

“Systems thinking” motivate team members to consider each and every element that are within the context as a whole. For example the business context for which a solution is being developed may involve factors internal to a business such as data, systems, technology, resources (financial and non-financial) as well as factors which are external such as competitors, government and regulatory bodies, suppliers and distributors, financial institutions etc. which may all impose constraints on the solution.

One of the key principles in Agile methodologies involves lean principles which is to minimize waste or non-value adding activities and to increase the probability and impact of value-adding activities. 

Common questions, which SAFe® addresses
 
SAFe® was developed to address the following industry wide questions.

  • How can organizations scale agile practices starting from small agile project teams, to larger programs, to business unit or enterprise wide programs or portfolios and even to cross-organizational mega projects?
  • How can teams of scale be organized around continuous delivery of value?
  • How can teams of such magnitude collaborate effectively avoiding delays and bureaucracy evident in such large scale projects if run as traditional projects?
  • How can dependencies between multiple teams be managed?
  • How can an environment that fosters collaboration, continuous improvement and innovation be created and sustained?
  • How can culture be molded to motivate team members to make mistakes and learn from them?
  • How can the team measure success of new working methods followed and how can they make it more efficient?

SAFe® provides a well-defined set of values, principles and practices which can be adopted enterprise-wide to better address these questions above.

In my upcoming articles I will discuss about different configurations of SAFe® with details on how different roles, systems, practices and values contributes towards continuously delivering value through the agile release train.

Rumesh

Rumesh Wijetunge

Chief Innovation Officer - Zaizi Limited, Chief Operating Officer - LearntIn (Pvt) Ltd., Director /

Rumesh is an IT business leader with over 12 years of industry experience as a business analyst and project manager. He is currently the CIO of Zaizi Limited, a UK based data management company heading the operations in Sri Lanka, the COO of LearntIn, a global training institute based in Sri Lanka and is also a lecturer / trainer at multiple private universities on management, IT, business analysis and project management subjects. He is the current president of the IIBA Sri Lanka chapter and is one of the most qualified and sought after trainers in Sri Lanka. Refer his LinkedIn profile for more details and to see more articles he has written on linkedin

Join the Discussion

Your email address will not be published. Required fields are marked *

Suggested Blogs

Combination Of Agile & DevOps – The Roots

Agile and DevOps are two notions that originate from the same schools of thought, but whose paths now have digressed. However, a major amount of confusion still remains within the IT services industry with regards to the relationship between the two and has emerging agile & devops trends in 2017. Hence, it is of value to look at the origins of each and to clarify the disparities between them. ‘Tell me what you want, what you really really want!!’ Does the tune ring a bell? Back in the 1990s, the Spice Girls were expressing to the world what they really really wanted, and similarly business owners and corporate leaders were doing pretty much the same, indicating what they wanted to software developers who were working on enabling these organizations through technology. Unfortunately, these business owners were not as lucky as the Spice Girls. More often than not they really didn’t get what they wanted. By the time business requirements were properly understood, validated and finally realized through software products the business requirements more or less had changed.  This was mainly due to the ‘application delivery lag time period’ that sometimes went up to three years. The result of the aforementioned delay from concept to realization meant that a large proportion of projects were stopped before completion. Even then, those that eventually reached the finish line more often than not did not meet the end users’ expectations.  The introduction of Agile – The change-driven management approach The search was on for a more lightweight approach to solution delivery and the result was ‘agile’ – a project management approach with a series of new concepts with regards to collaboration between business owners and the implementation team including UI / UX engineers, developers and even QA engineers. Instead of eliciting, documenting and signing off all the requirements up front and getting it signed off before work began, the focus shifted to delivering value through increments of functional software that would evolve over time. The results indicated that the software implementation team had become more productive, businesses could be more responsive in responding to queries of the implementation team, and user demands could be met more efficiently. However, problems remained. The agile approach didn’t always deliver on the promise of continuous, seamless software development. Blockers continued to exist. So, what is DevOps? The first thing to note is the fact that DevOps is not an individual tool or a suite of solutions but more of a philosophy whose primary purpose is to reduce the distance between the worlds of software development and IT operations. It defines how the original concepts of agile have moved downstream to the level of infrastructure and operations. The DevOps concept sounds relatively straightforward, but in reality it is a little bit more complicated. Software development and IT operations have historically had very different approaches. Software developers appreciate the ability to change things quickly and often they do end up changing things rapidly. In the meantime IT operators focus on stability and on minimizing alteration. This philosophical disparity has often resulted in conflicts. Thus, one of the main challenges of DevOps is to ensure that this conflict decreases before it affects the businesses. Importance of DevOps Principles For this very reason indicated above, it is very important to consider and act up on the core principles of DevOps. They are, Close collaboration and communication between developers, system operators and software testers Continuous integration that requires developers and operators to commit to changes more frequently Continuous delivery to increase the team’s speed and efficiency while enabling early detection of bugs Continuous deployment to ensure new developments can be released without system downtime The DevOps philosophy goes hand-in-hand with the delivery processes described in ITIL Framework in terms of support and IT services management. DevOps can therefore be seen as a way to implement ITIL processes in such a manner that meets the demands placed on systems today.  
3326
Combination Of Agile & DevOps – The Roots

Agile and DevOps are two notions that originate fr... Read More

Metrics that matters for DevOps Success

DevOps is generally introduced for the development teams to speed up the software delivery. DevOps is considered as a step beyond Agile. Many enterprises accepted DevOps as a part of software delivery process from planning, developing, deploying and updating an application, according to reviews. In this competitive world, DevOps allows businesses to speed up with the rapid pace of demands by the customers.Here are the top Ways to Obtaining Business Benefits of DevOps. Customers of today demand quality as well as security based products. DevOps, making the best use of its principles, provides superior quality and lowers the risk. On the contrary, in traditional software development approach, increased speed often results in poor quality and increased vulnerabilities. Why are metrics essential? Most organizations implement DevOps because of the demand for quality, time improvement and the need for defect-free products. Since DevOps has no specified framework, there exist a few standard ways to measure DevOps success. How do you find out how well it can work? How will you come to know whether it is working or not? The answer to this question, and the solution to all the existing problems, is the use of Metrics. Metrics are essential to stay in sync with DevOps. DevOps will be used extensively which therefore requires continuous treatment. But if you are not measuring its outcomes, you cannot understand how to incorporate DevOps in your organization. The focus of DevOps metrics is on deployment, operations, and support (feedback). Let us have a look at the Devops metrics which will lead to improved delivery performances. People: People are the major elements of the DevOps process. People-oriented metrics measure the things like yielding, capacity and response time. People are the hardest element of DevOps. So always start with the phase ‘People’. Process: In some ways, DevOps is considered as a process of  continuous deployment. There are many process-oriented metrics. Development to deployment is a large process-oriented metrics. Process metrics can be the measurement of speed, appropriateness and effectiveness. Technology: Technology metrics also plays a major role in DevOps. It measures the things like uptime (time during which the computer performs operations), network and support, and failure rate. Deployment (or Change) Frequency: DevOps metrics includes continuous deployment. Updated software deployment in every few days can be possible with fast feedback and piecemeal development. In a DevOps environment, deployment frequency can be measured in terms of the response time, the teamwork, the developer capacities, development tools and the overall efficiency. Change Lead Time: Change lead time is the time period between the initialization phase to the deployment phase. In DevOps, it is a measure of development process efficiency, code and the development systems’ complexity, and also of team capabilities. A protracted ‘change lead time’ is an indicator of an inefficient deployment system. Change Failure Rate: One of the main goals of DevOps is to do frequent deployment with less failure rates. Failure rates metrics should be decreased over time, as the experience and the capabilities of the team and developers get increased. If the frequency of failure is very high, it is definitely a red flag, as it gives rise to problems in the overall DevOps process. Mean Time to Recover: Time taken between ‘recovering the failure’ from the ‘failure’ is known as Mean Time to Recover (MTTR). It can be fragmented into three phases- detection, diagnosis and recovery phases. MTTR metrics is the sign of a good teamwork which identifies how effectively the teams handle the changes, and also, how collaboratively they do so. By all means, this metric is becoming a trend for DevOps to remodel organizational processes in a better way.
Metrics that matters for DevOps Success

DevOps is generally introduced for the development... Read More

Agile and DevOps Or Agile vs DevOps: Differences

Agile is the standard in today’s application development world. Development teams are adopting it over the last 10 years, as it has been proved to be more efficient methodology of getting quality software. Agile has improved user experience by frequently rewarding with focussed goals and quick delivery. In addition to this, the broad use of DevOps in Agile methodology has made it a more compelling approach for IT commercials. In this context, it is important to know that Agile is not DevOps, and DevOps is not Agile. It is difficult to achieve success in DevOps, if Agile practices are not followed. While Agile can make sense independent of DevOps, it can be more complete when accompanied by DevOps practices.Here are the emerging Agile and DevOps Trends. Many people have set their minds about Agile, that Agile means Scrum and DevOps means continuous delivery. This simplification creates unnecessary confusion between Agile and DevOps, making people think that they are perfectly compatible. So, let us have a look at the practical connections between Agile and DevOps. Planning for Unplanned work: In the DevOps circle, those using Agile acknowledges that Scrum is used to track the planned work. Tasks like releasing updated system, performing system upgrades etc, can be planned. On the other hand, the operations like performance spikes, system expiry, and standard security, can be unplanned. These types of tasks need immediate response. You cannot wait for the next sprint planning session. For this reason, many organizations embrace DevOps (more than Scrum and Kanban), which helps to track both kinds of work. Before, there were priorities from multiple masters, but now a single set of priorities are in use. Similarly, for a long list of assigned work, the time period is planned to accomplish the work. These lightweight management practices by Scrum make a huge difference for a team. Speed vs Risk: Teams using Agile with or without DevOps have to remember that, to support the rapid change, a sound application structure and a solid foundation are mandatory. Applications must have good underlying framework that must be used constantly by the team members. In the DevOps context, the teams must make sure that the changes which are made to the architecture should not introduce any risk. Also, there should not be any hidden side-effects associated with the changes, because the iterative process consists of regular changes in the architecture. So you should be concerned about the risks associated with each and every change made. Only with this type of work will you get rapid delivery without any risk. Agile and Quality: Both Agile and DevOps help develop an application fast, keeping sound structure and risk-free application.  But neither of them concentrates on the quality of the product. Mostly, IT organizations rely on the ‘fail fast’ principle- “ Early failures cost less to fix”. But with this, only fast deployments can be maintained, not quality. Agile produces applications that fit better with the desired requirements and can adapt quickly to respond to the requirement changes made on time, during the project life. DevOps, along with the automation and early bug removal, contributes to creating better quality. Developers must follow Coding and Architectural best practices to  embed quality in the applications. Agile and DevOps should try reach the next level to become highly effective within the organizations. They must conform to the industry standards using Agile and DevOps practices, to allow the development team to improve quality, make delivery faster and avoid software risks.
1443
Agile and DevOps Or Agile vs DevOps: Differences

Agile is the standard in today’s application dev... Read More

Useful links