Stabilize and Operate describes the practices needed to make sure the solution is working well from a functional and non-functional perspective This cookie is set by Addthis. This is a geolocation cookie to understand where the users sharing the information are located. The schedule is fixed – The train departs the station on a known, reliable schedule, as determined by the chosen Program Increment (PI) cadence. If a Feature misses a timed departure and does not get planned into the current PI, it can catch the next one.

System Architect/Engineering is an individual or team that defines the overall architecture of the system. They work at a level of abstraction above the teams and components and define Nonfunctional Requirements (NFRs), major system elements, subsystems, and interfaces. Business Owners are key stakeholders of the ART and have ultimate responsibility for the business outcomes of the train. Similarly, the overview of the a product owner’s potential responsibilities frames the discussion about what really happens.

Table of contents

Product Management is the function responsible for defining desirable, viable, feasible, and sustainable solutions that meet customer needs and supporting development across the product life cycle. Flow through the system is visualized, managed, and measured by the Program Kanban. ARTs Deliver All or Part of a Value Stream After exploration, the organization has the inputs to begin designing a solution, which often involves the following activities: Innovation and Planning (IP) – IP Iterations occur at the end of every PI and provide an estimating guard band (buffer) as well as dedicated time for PI planning, innovation, continuing education, and infrastructure work.

Ultimately, DevOps is a mindset, a culture, and a set of technical practices that provides solution elements to the customer without handoffs or too much external production and operations support. As illustrated in Figure 7, SAFe’s approach to DevOps is grounded in five concepts: Culture, Automation, Lean Flow, Measurement, and Recovery ( CALMR), briefly described below. Figure 7. SAFe’s CALMR approach to DevOps Learn describes the practices needed to decide what should be done with the information gathered and prepare for the next learning loop through the CDP Figure 9. Continuous Exploration, Continuous Integration, and Continuous Deployment are continuous, concurrent, and supported by DevOps capabilitiesEvery product owner faces a complex and unique set of challenges within their team. This provides each individual the opportunity to fill the role with different ambitions, skills, and insights. Your product ownership journey can take a variety of paths, and The Art of Agile Product Ownership is here to be your guide. The PO’s responsibilities can generally be categorized into five primary areas, as shown in Figure 1. Figure 1. Product Owner areas of responsibility