Vision
A description of the future state of the Solution under development. It reflects customer and stakeholder needs, as well as the Feature and
... [Show More] Capabilities proposed to meet those needs.
SAFe Core Values
Alignment, Built-in Quality, Transparency, Program Execution. These represent the fundamental beliefs that are key to SAFe's effectiveness. These guiding principles help dictate behavior and action for everyone who participates in a SAFe portfolio.
Program Increment (PI) Objectives
A summary of the business and technical goals that an Agile Team or train intends to achieve in the upcoming PI.
Iteration Review
A cadence-based event, where each team inspects the increment at the end of every iteration to assess progress, and then adjust its backlog for the next iteration.
Nonfunctional Requirements (NFRs)
Define system attributes such as security, reliability, performance, maintainability, scalability, and usability. They serve as constraints or restrictions on the design of the system across the different backlogs.
Continuous Delivery Pipeline (CDP)
Represents the workflows, activities, and automation needed to shepherd a new piece of functionality from ideation to an on-demand release of value to the end user.
DevOps
A mindset, a culture, and a set of technical practices which provides communication, integration, automation, and close cooperation among all the people needed to plan, develop, test, deploy, release, and maintain a Solution.
Weighted Shortest Job First (WSJF)
A prioritization model used to sequence jobs (e.g., Features, Capabilities, and Epics) to produce the maximum economic benefit. In SAFe, it is estimated as the cost of delay divided by job size.
INVEST model
Describes characteristics of good user stories:
I - Independent (among other stories)
N - Negotiable (a flexible statement of intent, not a contract)
V - Valuable (providing a valuable vertical slice to the customer)
E - Estimable (small and negotiable)
S - Small (fits within an iteration)
T - Testable (understood enough to know how to test it
SAFe for Lean Enterprises
A knowledge base of proven, integrated principles, practices, and competencies for Lean, Agile, and DevOps.
Scaled Agile Framework (SAFe)
A proven, publicly available, framework for applying Lean‐Agile principles and practices at an enterprise scale. SAFe synchronizes alignment , collaboration , and delivery for large numbers of teams.
Product Management
Responsible for defining and supporting the building of desirable, feasible, viable, and sustainable products that meet customer needs over the product-market lifecycle.
Product Owner (PO)
A member of the Agile Team responsible for defining Stories and prioritizing the Team Backlog to streamline the execution of program priorities while maintaining the conceptual and technical integrity of the Features or components for the team.
Solution Management
Responsible for defining and supporting the building of desirable, feasible, viable and sustainable large scale business solutions that meet customer needs over time.
Types of Customers in SAFe
Internal and External Customers
Internal Customers
Customers inside the enterprise
External Customers
Customers outside the enterprise.
Product Management Primary Responsibilities
Meet business goals, Get it built, Get it off the shelf, Leverage support
What must product management maintain alignment with?
Responsible for maintaining alignment with the portfolio canvas, Lean Budgets, and Guardrails.
What are the product management responsibilities in supporting the ARTs to "Get it Built"?
Understand customer needs, Ensure product completeness, Develop and communicate the program vision and roadmap, Manage and prioritize the flow of work, Participate in PI planing, Define releases and program increments, Work with System Architect/Engineering to understand Enabler work, Participate in demos and Inspect and Adapt (I&A) [Show Less]