Scaling API-first – The story of a global engineering organization
Lean Agile.pptx
1.
2.
3. There are three levels of the
Scaled Agile Framework (SAFe)
requirements model: Team,
Program, and Portfolio.
4. THE REQUIREMENT MODEL FOR AGILE TEAMS
To optimize the software development process, the teams need to organize
around the requirements first.
#PRO TIP: Ensure the balance between the backlog and user stories.
7. PROGRAM LEVEL OF AGILE TEAM
Define what is to be constructed
and organizing teams around a
single objective. Various choices
to communicate vision: vision
document, draft press release,
backlog, etc.
The higher version of software
requirements that can bridge the
gap between the solution and
problem domains. A set of features
forms the vision that delivers value
to end-users and differentiates a
product in the market.
.
Serve as constraints or restrictions
on the system's design across the
different backlogs. Proper
definition and implementation of
NFRs are critical that require
extensive skills from Agile teams.
.
VISION FEATURE NON-FUNCTIONAL
REQUIREMENTS (NFRs)
8. THE MODEL FOR AGILE PORTFOLIO
To set the tone for developing and achieving the objectives in fulfilling all
the requirements necessary, the Portfolio level is necessary.
Product and Release Managers can use these portfolio backlog artifacts to
form their backlog of more detailed program-level initiatives.
9. THE MODEL FOR AGILE PORTFOLIO
Indicate the set of initiatives that
drive the enterprise’s investment
in systems, products,
applications, and services.
Epics are the highest-level
requirements artifacts, lie between
investment themes and features.
They need the definition of an MVP
and approval by Lean Portfolio
Management before execution.
Epics are the highest-level
requirements artifacts, lie between
investment themes and features.
They need the definition of an MVP
and approval by Lean Portfolio
Management before execution.
INVESTMENT THEME
EPIC CAPABILITIES