SAFe – System Architect and Solution Architect

System Architect and Solution Architect, represents the teams and individuals, which have the technical responsibility for the overall engineering and architectural design of the solution and system. This fractious discipline system takes a system view on key progress. It is participating in the definition of a nonfunctional requirements and higher level functional that analyze the technical trade offs, major subsystem and components.
System Architect and Solution Architect align the Value Stream as well as Agile Release Trains to a corporate technological and architectural idea of the Solution under progress. Participating in defining the subsystem and systems, evaluate alternatives and endorse technology assumptions that support the solution improvement through providing architectural view, communicating and evolving the larger technological solution.
This team arises and Value Stream Level and Programs controls mostly the setting of the Agile Release Train where they work with the Agile Teams and have a practical enablement with respect to subsystems and capability parts under the purview of the Architectural Solution teams that have a practical leadership for developing architectural abilities of the whole solution.
System and Solution Architect usually have the responsibilities such as:
 Supervising and foster the Built in Quantity
 Participating in PI Planning and Pre-Post PI Planning System as well as Inspect and Adapt
 Developing and Planning the architectural way in supporting for the upcoming business Features/capabilities
 Support the technology aspects of Program and Value Stream Kanbans
 Explore, support and define the implementation of value stream and program enablers to progress solution resolved; work openly with agile teams to support explore and implement them.
 Participating in definition, high level design and planning of the solution and explore solution replacements
 Defining their interfaces and subsystems that allocate responsibilities, understand the solution placement as well as communicating the necessities for the interactions with solution setting.
 Work together with the stakeholders, suppliers and customers to establish the high level solution determined which can help the key intent information models and documentation necessities.
 Working with portfolio stakeholders, specifically the Enterprise Architect to analyze, split, realizes and develops the execution of enabler Epics.
Initiatives build a group of people who perform the systems features of solution progress of those teams that usually involve multiple disciplines, mechanical, hydraulic, electrical, as well as other aspects of a complex solution and the software elements. Obviously, it is impossible to reason nearly how to form a multifaceted solutions without containing the parts of software Systems Engineering and Architecture. A significant communication of restraint is necessary. The customary ways for both solutions, it is strongly sink near the point-solution, phase-gate, and Big Up Front Design approaches. It is understood because the stage gate cascade model is the finest model available at that time and these are large systems as well as someone has to identify how one is hypothetical to go about the structure. Therefore, this functions emphasis on the cross discipline relationship, feedback-driven knowledge cycles and leveraging the characteristic erraticism of the advancement product.

— Slimane Zouggari

SAFe – Release Train Engineer and Value Stream Engineer

A release train engineer (RTE), has a responsibility to facilitate the program level, manage risk, and escalates impediments as well as helps drive in program level constant development. While the Value Stream Engineer (VSE), is the one that is guiding and assisting the work of a Release Train engineers as well as the Suppliers, these two kinds of jobs has almost the same background of development or SAFe program managers and function the most effective servant leaders.
The Value Stream Engineer (VSE) and Release Train Engineer (RTE) assist the value stream and release train execution as well as the processes. They intensify the manage risk, help guarantee value delivery, impediments and help drive nonstop development.
The two types of job have responsibilities normally fulfill the following tasks such as:
 Optimizing and managing the flow of the value over the program by means ofthe Information Radiators and Program and Value Stream Kanbans.
 Coach Leaders, scrum masters and teams practices and attitudes
 It inspires the Team Level, value stream level, program level, as well as around engineering and quality practices
 Contagious of improvement in initiative via Adapt and Inspect workshops, it is measure the alertness of the value stream and help recover
 Attending the Solution Demos and System Demos
 Providing contribution on resourcing to statement serious blockages
 They operate and understand within the Budget
 They also helping to manage the dependencies and the risks
 Supporting some related activities and report status to the program agile portfolio management
 Assisting the periodic synchronization meetings, including the ART sync in the Program Level as well as the VS sync in the stream value level
 Facilitating together with economic decision making by helping ability and article assessment by team and roll-up to the stream value level as well as the Portfolio level
 Track impediments and escalate
 Establishing the Program Increments an communicating to annual calendars for iterations
 Helping PI Planning
 Simplify the Post-Pi Planning keenness via nurturing the training of Backlogs and Vision, as well as pre and post PI Planning meetings
However, an outlook change is frequently needed for a new Release Train Engineer and Value Stream Engineer. The managing and direction activities is stand-in as a servant leader. A servant leadership is a management philosophy that denotes an inclusive assessment of the value of a community, work and spirit. In this regard, the Release Train Engineer and Vale Stream Engineer must have the characteristic of a servant leader actions wherein you must support and listen your team in regards to the problem in decision making and identification.
Encouraging and supporting the development of team as well as the personal improvements of individuals. Persuading rather using of authority. Creating a kind of environment that has mutual influence. It is important that you support the commitments of the team and you need to be open and learn to appreciate the openness in other member of the team.
Therefore, Release Train Engineer and Value Stream Engineer has almost the same responsibilities that need to fulfil, but in order to be an effective engineer you need to learn the characteristic of servant leader.

— Slimane Zouggari

Safe – Product management

Product management is very important to all business owners out there through the help of reputable and trustworthy company. Looking for the best service provider is quite hard especially on the internet. In this way, if you want to have a reliable company who will be responsible on product management, SAFE will be the best idea that you could ever have. When you will consider this amazing amenity provider, you will be given a product manager who can do the following services:
1. Understand client’s needs and make effective and efficient solutions. Managing of a product is the customers’ internal voice more specifically for the Agile Release Train or ART. Furthermore, they work on with customers in order for them to have a profound understanding about the things they should have to know. In addition to that, they will be able to communicate all their needs and join in proposed solutions validations.
2. Comprehend and help portfolio work. Every ART is connected to a portfolio in which the product manager has the working obligation to comprehend the so-called Budget parameters that are needed for the fiscal period. They are familiar on how a particular strategic themes influence its direction. They will also serve Epic Owners in order for them to improve Epics business case that can affect their Agile Release Train (ART).
3. Enhance and communicate the vision program and roadmap. Product management will consistently enhance and communicate the goals and objectives of the teams that are tasked on development. Also, they will define all the basic properties of the platform. In this way, you will be assured of getting the service that you truly deserve. In fact, they are partnered with the Solution and System Engineering/ Architect which likewise define and keep the NFRs which mean Nonfunctional Requirements. This will help you ensure that the provided solutions reach the standards.
4. The work flow will be managed and prioritized. Product management facilitates the work flow via the Kanban Program. They make sure that there are ready features that can be found in the backlog more often. This is because they enhance the acceptance feature criteria that are employed to help these features meet its Done Definition.
5. Product manager join PI planning. During the PI planning session, product management delivers the vision that highlights the proposed solution features in addition to the related ongoing Milestones. Also, they usually join as train business owners who are responsible for establishing the value of the business and approving the objectives of the PI.
6. Create a functional and efficient Product Owner and Product Manager team. The key to functional and efficient innovation is the Product Owner and Product Manager team. They also make a bigger contribution to the satisfaction of their job.
Summing up, if you need product management, you can make SAFE as your number one option. They can assure you of receiving an excellent service. Furthermore, you will be given a product manager who has the ability to do the job for you.

— Slimane Zouggari

SAFe – Enablers

Enabler is a kind of technical initiative that has the ability to support development of an organization initiative. It commonly exists to four levels of SAFe: Enabler Epics at Portfolio level, Enabler features at program level, Enabler capabilities at Value Stream Level and Enabler stories at team Level. It can be used to different kinds of activities that need support for the upcoming features of business however, it falls only to three types of categories and it includes:
• Infrastructure- It is use to enhance and build the testing and development of an environment to facilitate faster the high quality testing and development.
• Architecture- It is use to build architectural runway to ensure it will create fast and smooth development.
• Exploration- It is use to build understanding regarding the needs of the customers and understand the prospective solutions in evaluating alternatives.
Through using enabler, you will have the assurance that you can capture the visibility of the needed work and efficiently support the delivery and development of business features for its future. However, you still need to choose which one will work best for your business since there are different types of enablers you can choose from.
Here are the types of enablers you may find in the market:
• Enabler stories-This kind of enabler best fits to Iterations nut do not require voice format since it has criteria of acceptance that requires the support testing.
• Enabler features and capabilities. This kind of enabler commonly occur at Program levels and value Stream in which it can share similar attributes like statement of acceptance and benefits criteria and it usually best for single PI.
• Enabler epics-This is type of enabler that is written through using value statement format that has been defined just for epics.
Since it is created based from the initiative of the business, it can make different Kanban system that needs explorations to validate the solution, develop test, pave runway, and integrate initiatives. Most of these enablers are created by architects or through the system of the engineering at different levels either it is portfolio levels, enterprise architects or system and solution of both engineering and architects at program levels and value stream. Architect that creates enabler can steer it through Kanban System that can provide information that is needed to implement it and guidance that can help to analyze it.
Some of the enablers can emerge locally from needs of agile teams, value streams, agile release trains to improve its existing solutions. It is subjected to the allocation in value stream backlogs and program that will provide assurance to have better solutions. It can be applied for enabler that will differentiate different kinds of enablers.
Enabler can be applied to exploration in order for the development teams flesh out some details of designs and requirements, architectural runway to ensure agile architecture can implement their concepts, and to the infrastructure that will ensure to reduce the risk of integration. This is how the enabler becomes very beneficial is to most of the engineers and architects. .

— Slimane Zouggari

SAFe – Customer

Nowadays, customers are the most important entities in the business world. Since the world is becoming highly competitive, customer will serves as the external and internal part of an organization that continuously increases their demands. Most of them want some options, quick service, better solutions, and more valuable products that will meet all of their needs with great satisfactions.
Integrating the customer as the integral to the Lean –Agile Solution is the best way to have better development since you consider them as part of your value stream. Therefore, they should not be separable from process and should work closely and frequently with the product and solution management and other kinds of stakeholders that will help to shape the economic framework, vision and solution intent. Customers have strong influence to define and prioritize solutions and can actively participate to the process improvement, demos, and planning.
Customers are considered as integral part of the lean agile development that plays vital role for SAFe and at the same time part of value stream. The support for the agile principles and lean are continuously participating to the evolutions, demonstrations, planning and definition of solutions that is very important to the success of every execution.
In some cases, customers are considered as internal while others are external. On the other hand, customers are the largest class to the economic buyers wherein the system builder needs to understand and aggregate the requirements for some general case and fill the broad market that needs the adequate internal proxy to the development.
So no matter what kind of customers you have for your business are, there is a need for you to get engage them in your entire agile development solutions. They are require to participate to the proxy or person by fulfilling the general responsibilities like:
• Participate in UAT, beta testing and other forms of validation for best solutions
• Participate similar to business owner when it comes to PI planning
• Review the financial and technical status of solutions
• Attend system demo that can help to evaluate for the increment solutions
• Communicate with economic logic and help to create validate assumptions to the economic framework
• Participate in workshops and remove the systemic impediments
• Collaborate to manage the time, scope and other constraints regarding solution and product management
• Interact with subject matter and expertise at time of workshops
• Define the milestones, releases and roadmaps
The engagement of the customer as end-user can drives the success of agile. Since the agile development is considered as dependent in high degree of engagement from their customers there are higher stage models are being assume. However, the engagement here is different because serves as the base from the solution builder in which the building is the general solutions and use to sell to numerous customers. It is also specifically build for customers that are base from their specifications.
Having this kind of solutions, it helps to reduce the aspect of win – lose regarding the relationship to the customer and system builder and receives continuous flow for the business.

— Slimane Zouggari

SAFe – Business Owners

SAFe has business owner’s roles, which are being played through three to five groups of stakeholders. These people have shared governance, fiduciary, ROI responsibility, and efficacy for the Agile Release Train delivered value. In every train, the role is being carried out by the people who are suited enough for this kind of job. Aside from that, they have other responsibilities in every stage such as before PI Planning, during PI Planning, Assigning business worth, at adapt and inspect, PI Execution, and other working responsibilities.
Before PI Planning
This period is considered as Business Owners business time because they have a lot of things do such as participating during prior-PI Planning, understanding all the business goals and objectives, helping the stakeholders, Product Management, System Architects, and Train Release Engineer comprehend and understand the set goals, and providing the context of the business to the Milestones, external dependencies, and suppliers. When these people do not make these responsibilities the next step or process will be tremendously affected.
During the PI Planning
The roles of these individuals are very important during this process as they deliver related business context elements, play a major role when it comes to the review of draft plan in which they need to understand its bigger picture and whether or not the plans achieve the recent business goals, circulate the process, communicate the priorities of the business to various teams, keep the stakeholders’ alignment and agreement, and actively join with the review on the management and problem-solving session. With these obligations of the Business Owners from SAFe, these should be properly done so that everything will go accordingly and hassle-free.
Assigning Business Worth
The assignment of business worth especially during planning stage gives the business owners, the team, and the stakeholders a salient face-to-face dialogue. Aside from that, it provides a chance to enhance a personal rapport between the Business Owners and the Agile Teams in which they will be able to gain a deep understanding wherein the mutual commitment is being based. Also, they will better realize the true business goals and their relative worth.
At adapt and inspect
The adapt and inspect workshop can be considered as the larger cadence-based chance wherein the Agile Release Train (ART) will be able to make deeper reflections and to solve a wide variety of predicaments that they will face along their ways. These impediments cannot be solved without the business owners’ involvement. In the workshop, business owners evaluate the actual value of businesses while considering the plan. Furthermore, they make an active participation on problem solving.
PI Execution
Apart from that, their roles do not stop. As a matter of fact, they play a significant obligation during this process such as attending to the system demonstration that will view the development which can provide feedback, attending Iteration planning, attending iteration Retrospective sessions, and others.
Other responsibilities
These include providing a feedback on the Solution Demo, addressing impediments, joining in the Post-PI Planning, assisting trains in adjusting the Agile Release Trains PI plans. With all of these responsibilities of the business owners, they have an important role all throughout the process.

— Slimane Zouggari

SAFe: Value Streams

Value Streams are known as the primary SAFe construct intended for organizing, understanding and delivering value. Every value stream is considered as a long-lived series of the steps which an enterprise would use in order to offer continuous flow of value to the customer. The main goal of the SAFe portfolio would be about financing and nurturing set of solution development activities which either delivers the end user with direct value or whether to support some other business value streams. It is considered as a critical skill to identify and optimize value streams of the Lean-Agile enterprise.
It is a fact that organizing around value would offer substantial benefits into the organization such as faster learning, higher quality, solutions, higher productivity and shorter time of marketing which are all better fit into the intended purpose. SAFe would definitely be of great help for you in terms of organizing around value that would be accomplished first by understanding the value streams and finally organizing the SAFe Agile Release Trains in order to realize them. The art and science of SAFe is realizing the value streams through the ARTs. Apart from that, value streams would lend themselves into systematic analysis as well as improvement through value stream mapping that is utilised in order to identify as well as address the delays and also the non-value added activities therefore helping in terms of accomplishing only the shortest sustainable lead time.
What are the types of Value Streams?
For SAFe, system builders should be aware about the two types of the value streams that are present in a certain enterprise. The first one is the operational value streams which show the steps to be used in order to provide services and goods to the customer both for external and internal. And this is how the said company would make money. The second one is the development value streams that are to show the steps being used in order to develop new products, services capabilities and systems. In most cases, these are the same, once a solution provider would develop the product for sale as well as feeds distribution directly. However, in the said case there is only a value stream being the development as well as operations are considered to be the same. Still, it is critical to understand both types of the value streams since the development value stream would feed the operational value stream.
How to identify value streams?
Within some organizations, it is a simple task to identify value streams. Most are simply the services, products and solutions they develop as well as sell. Once the enterprise gets a bit larger the task would be more complicated as well. Value would flow via applications as well as services and might across numbers of parts of the distributed organization to numbers of external and internal customers of different types. In some of the larger IT shops, value might move across numbers of departments as well as organizations and also across numbers of deployed systems. And in that case, finding the value stream might be an essential analytical as well as business context-related activity which provides basic foundation intended for the Lean-Agile transformation.

SAFe: Strategic Themes

Lots of organizations utilize strategic themes in their strategy map. These themes could help organize those groups of related strategic goals, which work altogether to present a valuable and specific business result.
Let’s Take a Thorough Look of What Strategic Theme Really Is
Strategic themes are itemized, specific objectives, which link a SAFe Portfolio to the changing business strategy of an enterprise. It offer business context mainly for decision making in the portfolio at the same time affect investments in the Value Streams and be able to offer inputs to the following decisions:
– Program Backlog
– Solution
– Portfolio
– Budgets
– Economic Framework
These themes don’t need to restate the evident, as majority of elements of the vision of portfolio are comprehended through context. In addition, portfolios stakeholders are typically understand well what the portfolio is really for, handle, and create their own visions and goals.
What does it offer?
To a certain extent, strategic theme is capable in providing the enterprise along with the differentiators that is going forward coming from the present state to the unknown state. These aid drive competitive differentiation as well as innovation, which is achievable through efficient portfolio solutions.
In addition to that, strategic themes are crafted as a result of a collaborative and structured planning process – one, which includes the executives and fiduciaries of the enterprise and the key stakeholders coming from every portfolio.
Devising Strategic Themes
Creating strategic themes is one practice in strategy formulation; however, it is not the state of SAFe portfolio context. According to the guidance of a certain enterprise, this theme is an output of a collaborative process, which is a kind of process wherein the enterprise portfolio stakeholders are able to work along with portfolio stakeholders to analyze a collection of inputs prior to getting at conclusions.
Following are some common samples of strategic themes:
(1) Create shingle sign-on in the portfolio applications into the internal enterprise apps
(2) Online retailer or lower warehouse costs
(3) Execute operational and product support for securities in FOREX trading (security company)
(4) Demand to a younger demographic or online retailer
(5) Regulate on three (3) software platforms
How Strategic Themes Affect the Portfolio
Vision
Strategic themes are one of those primary inputs into the portfolio vision at the same time plays as elements of Economic Framework, which affects Agile Release Train budgets, Value Streams, individual ART vision, Portfolio Backlog and Roadmap.
 Economic Frameworks – it affects some of the major parameters such as product cost, cycle time or development, risk, product value and development expense
 Value Streams – such theme affect value stream budget that present the spending s well as the personnel allocations needed to build the portfolio vision.
 Vision & Priorities – here, the Product and Solution Management was able to apply such them to affect the roadmap.
 Portfolio Backlog – themes offer decision making filters on the system of Portfolio Kanban thus affecting the portfolio backlog.
Keep in mind that strategic themes are quite essential tool for corresponding strategy to the whole portfolio. It offers a memorable, simple reference frame and at the same time must seep into the thinking of everybody included in Solution delivery.

SAFe: Non-functional requirements

If there’s any one thing that all projects should have to ensure a successful project outcome, that is a comprehensive and sensible collection of non-functional requirements, aside from functional requirements.
NFR or non-functional requirements is responsible for describing how the system runs. Essentially, it identifies how the system should work and that is a constriction on the behavior of the system. Also, you can think of NFR as a quality attribute of a system. It covers all the remaining necessities which are not comprised by the functional requirements. Instead of specifying specific behaviors, they identify criteria that judge the system’s operation.
What are the typical non-functional requirements?
There are many typical NFR included, some of them include:
• Performance
Requirements on resources required, throughput, static volumetric, utilization, benchmark utilizations, response time or whatever thing that is having to do with performance.
• Precision and accuracy
This refers to the precision and accuracy of the data. However, each one is advisable to become beware of the one hundred percent requirements, as they frequently cost great amount of money.
• Modifiability
This is the requirements about the effort needed to make software changes.
• Reliability
Requirements on how frequent the software fails. Often, the measurement is expressed in mean time between failures (MTBF). The description of the failure should be clear. People also get confuse between reliability and availability, which, in the first place should not because they are quite different types of requirements. Make sure to identify the results of software failure, a strategy to detect error, a correction strategy and how to protect from failure.
• Portability
This is the required effort to move the software into various target platforms. Mostly, the measurement is person-months or percent of elements that need altering.
• Usability
The requirements on how challenging it will be to learn and run the system. Often, the requirements are conveyed in learning time or other similar metrics.
• Security
One or more requirements on system protection and its data. The measurements may be expressed in a range of ways such as time, skill level and effort, among others, to get in the system.
• Integrity
Integrity requirements describe the system’s security attributes, which restricts access to data or feature to particular users as well as protect the privacy of data entered in the software.
• Robustness
A robust system is the one responsible for handling error conditions in a graceful way, with no failure. This includes a forbearance of invalid data, unexpected operating conditions and software detects.
There are other typical NFR included, and some of them are capacity, scalability, availability, maintainability, recoverability, serviceability, environmental, manageability, regulatory and interoperability.
With the increasing demand in this system, more and more companies are trying to get the interest and trust of clients, promising them a high quality service and product. But if you really want total assistance, Scaled Agile Framework is the best partner you can depend on with your non-functional requirements.
SAFe is a freely, online revealed expertise base of credible and proven success patterns when it comes to implementing Lean-Agile systems and software development at company scale. It offers extensive guidance for project at the enterprise Program, Value Stream, Portfolio and Team levels.

SAFe: epic abstract

Epic Abstract
Epics are considered as containers intended for important initiatives which would help in guiding value streams through larger aim of a portfolio. In doing so, they would drive more of the economic value for a certain enterprise. They are as well considered to be large and commonly crosscutting at the same time crossing numbers of value streams and also ARTs or the Agile Release Trains. They are also investment intensive as well as far ranging in impact like formulation as well as analysis of impact, cost and opportunity as a serious matter. And Epics as well need lightweight business case as well as financial approval prior to implementation. The two types of epics are enabler epics and business epics and are to appear in the value stream, portfolio and program levels.
Portfolio business epics and Enabler epics are considered as the largest epics that would capture that biggest crosscutting initiative which happen in a portfolio. Business epics are to bring business value directly while enabler epics are utilised in order to evolve the Architectural Runway therefore supporting the upcoming business epics. So, epics are captured initially within the Portfolio Kanban and would move into the system under WIP limits or the work-in-process. And this would help in reassuring that the ones doing the work would have some time needed in order to conduct a responsible analysis.
In connection, Kanban system is about helping manage the expectations intended for reasonable scoping as well as time frames intended for implementing the new ideas of a certain business. The final decision as for the actual implementation of every epic would be subjected into the authority of the PPM or Program Portfolio Management. Once resources are available, those decision makers could now choose from the numbers of business opportunities for there would be numbers of analysed epics within the backlog any time. And the epics that are being approved would proceed to Portfolio Backlog, waiting for the implementation capacity.
Epics are indeed the most important initiatives in a portfolio that’s why they should be analysed carefully prior to the implementation. The owners of epic should also take into responsibility for the said important task at the same time the architects of the enterprise would shepherd the enabler epics which support the technical considerations for the business epics. Those most worthy epics would be passed to analysis once space would become available within that queue. And from there, effort as well as economic impact are defined a lot better, cost estimates are as well established, WSJF prioritization would be refined and also lightweight business case will be developed.
Some of the things included in the analysis would be the following:
• Workshops along with business stakeholders for the purpose of describing and understanding the business benefits of the business epic
• Implementing spikes, exploration and research activities through teams
• Define the success criteria for the epic
• Workshops for architects as well as system engineering right from value stream and program levels and to the agile team allowing them to understand the implementation of the impact and effort in recent solutions and also some other related SMEs could be included
• Develop concrete examples in order to resolve certain ambiguities
And the result of the said analysis phase would be a lightweight business case which captures the results of the analysis such as refined description, estimates of time and cost of implementation, success criteria and also program impact.