#Essential #SAFe is a configuration of #SAFe that includes the bare necessities for implementing the #SAFe framework into an organization, with the most minimal elements needed to be successful. If you’ve seen the video on this channel where I go over each configuration of #SAFe and a more in-depth look at the components of the framework. In this video, I’m going to show you what goes into the Essential #SAFe configuration.

Essential #SAFe starts with the support of Business Owners. These are a small group of stakeholders who have the primary business and technical responsibility for a return on investment. They are key stakeholders on the #Agile Release Train who evaluate fitness for use. They ultimately steer the #ART where it needs to be to successfully accomplish its goal. The #ART is then supported by the #RTE, Product Management, and a System Architect/Engineer, who work together to ensure the #ART functions as intended. Under the #ART team, you have the bread and butter of the #solution development; The essentials of Essential #SAFe are built around principles, such as Customer Centricity and Design thinking, as well as systems to develop software through Program Backlogs, Team Backlogs, #ScrumXP, and other developed systems like the Continuous Delivery Pipeline.

Customer Centricity is built on the knowledge of Customers being the ultimate beneficiaries of the value of the business solutions that are created and maintained by the portfolio value streams. Customer Centricity is a mindset and way of doing business that expressly focuses on creating positive experiences for the customer, a deeply-integrated mindset that thinks about how the software will be integrated with the end user’s needs, rather than how they can use it as an afterthought. This in turn generates higher profits and better employee engagement, as developers are more likely to enjoy developing a product that they know the end-user is going to like.

Design Thinking is a customer-centric development process that creates desirable products that are profitable and supported over their lifecycle, as opposed to a haphazardly designed product that is almost impossible to work on after being shipped.

Program backlogs are holding areas for upcoming features, addressing user needs, and delivering business benefits for a single #ART. Product Management has responsibility for the Program Backlog, ensuring the items result from research and collaboration with stakeholders, part of the Continuous Exploration process, part of the Continuous Delivery pipeline, which we’ll get into in a moment.

Team Backlogs contain user and enabler Stories that originate from the Program Backlog, as well as stories that arise from development within the team. The Product Owner is responsible for the allocation and balance of the Team Backlog in a way that benefits both the team and the #ART.

#ScrumXP is a lightweight process designed to deliver value for self-organized teams within #SAFe. It takes effective, powerful #Scrum practices and combines them with Extreme Programming practices. #ScrumXP details two essential characteristics of Team and Technical Agility, where #Scrum provides guidance for team #agility and XP for technical practices.

#scrumorg #agile #scrummaster #scrum #productowner #scrumalliance #productmanagement #psm #agilecoach #scaledagileframework #devops #scrumtraining #productmanager #itbusinessanalyst #businessanalyst #agileproblems #itbusinessowner #developmentteam #scrumteam #agileprocess #scrummasters #scrumdotorg #agil #certificacaoscrum #retrospectivas #teambuilding #agiledevelopment