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.
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.
23 Oct 2017
31 May 2016
27 Apr 2016
19 Feb 2016
17 Feb 2016
08 Feb 2016