Embed Size (px)
Citation preview
SAFe 4.0® for IBM Application
Lifecycle ManagementAmy SilberbauerExecutive IT Specialist, Solution Architect
Enterprise Scaled Agile, DevOps Continuous Business Planning
IBM Watson IoT
8/11/2016
SAFe & IBM DevOps
Continuous Delivery -
SAFely
2
Leading a SAFe transformation requires an organizational focus…
3
People: Establish an organization-wide culture with the right set of skills to embrace lean and agile values – everywhere, across all teams, every day
Process: Apply lean and agile principles in the planning, development, deployment and delivery of value and then monitoring feedback to improve – continuously
Tools: Provide a framework that enables the implementation of lean and agile practices –easily – while also providing traceability and visibility of work across multi-disciplinary teams
IBM DevOpsProviding an enterprise capability for continuous software delivery
Continuous Customer
Feedback & Optimization
Continuous Business Planning
Continuous Release
and Deployment
Collaborative Development
Continuous Testing
Continuous
Monitoring
Speeding
continuous innovationEnabling continuous
delivery of innovations
Providing feedback
for continuous learning
We are here!
4
Synchronizes teams by…
Automating full traceability
Managing with dashboards and reports
Demonstrating compliance
Orchestrating multi-speed IT
Supporting multiple platform / processes / languages
What’s new?
Deployment ready reuse and parallel development
Integration with common SCM tools (Git/Github)
Support for Scaled Agile Framework® (SAFe®) 4.0 (and 3.0)
Now available in the cloud – by subscription or managed service
Collaborative Development
ContinuousBusiness Planning
Quality Management
IBM is a Leader! Gartner Magic Quadrant for Application Development Life Cycle Management (Feb 9, 2015)
“Consider IBM… With good support of waterfall, iterative and agile methodologies, IBM can be a good choice for bimodal organizations looking for a single ADLM solution for all teams.”
Project Analytics
“With IBM’s solution, we already realize that the different roles within the development lifecycle are cooperating much closer ”
Christof Hammel, Product Manager, Automotive ALM at Bosch Automotive
referencing IBM Rational solution for CLM
s
Collaborative Lifecycle Management
5
SAFe V4.0 summary
6
Portfolio
• Strategy formulation and portfolio communication
• Organizing and funding Value Streams
• Managing the flow of larger initiatives
• Governance and cross-Value Stream orchestration
Value Stream
• Solution Intent & Management
• Engineering and Architecture
• Customer and Supplier relationships
• Program (ART) coordination
• Unified Vision & Roadmap
Program
• Teams of Agile Teams that build solution capabilities and subsystems
• Common mission
• Architectural & User Experience governance
• Evidence of progress and delivery of value
• Organized by solution or subsystem delivery
Team
• Scrum, Kanban, hybrid processes
• Delivery of technology
• Organized by feature or component delivery
FoundationCore Values, Lean-Agile Principles, Center of Competency
SAFe for small and midsize solutions
7
Expand
one level
SAFe for large, complex solutions
8
Collapse
one level
Right-sized for your business
9
Largest businessesMultiple SAFe Portfolios
Larger businessesMultiple Value Streams Multi-ART Value Streams
Smaller businessesSingle-ART Value Streams 4-Level SAFe is optional
Value Streams
10
• Value Streams always exist, but additional governance may not be necessary
• For Systems development that scales for large, mission-critical solutions
• Typically for solution delivery that involves hundreds or thousands of resources
Value Stream Level (optional)
• Defines Solution Intent and Solution Context
• Delivers Capabilities that describe the larger behaviors of a solution
Solution Delivery
• Defines a Program Increment timeline synchronized across the ARTs and Suppliers that deliver Features for Capabilities
Orchestrated Delivery Across ARTs
• Embodies solution intent and delivery of capabilities on a long-lived timeline
Vision & Roadmap
Programs (Agile Release Trains)
11
Scope/Size• 5-12 agile teams
• 50-125 resources
Common Vision & Roadmap
• In 4-level SAFe, vision and roadmap are synchronized with the Value Stream
“Train” Concepts
• Resources are dedicated
• Set schedule
• Everything goes on the train
• Dates are fixed; quality is fixed; scope is variable
Organizing Value Streams around ARTsCommon patterns
12
• Multiple, small Value Streams can be realized by a single ART
• Example: Product or Product Line Value Streams
Small Value Streams (Exception)
• May be realized by a single ART
• ART = Value Stream
• Example: Application or System
Large Value Streams (Typical)
• May require multiple ARTs
• Example: Large Solution, Supplier Scenario
Very Large Value Streams
Best practices for defining ARTs
13
•Optimized for speed of value delivery
•Requires governance to avoid technical decay
Capability ARTs
•Optimized for architectural robustness, shared components
•Dependency management is critical
Subsystem ARTs
Best Practices: Most Value Streams are a combination of
these
Should focus on single, primary product or
solution
Feature and component teams that contribute
to the ART and have high degree of
interdependency should plan and work
together
Consider locale: organize ARTs around co-
located teams
Consolidate based on source of funding
Funnel
•Ideas from any stakeholder
•New business opportunities
•Business initiatives
•Architectural issues
•Cost reduction initiatives
Review
•Value Statement defined
•Initial WSJF triage
Analysis
•Solution trade-offs and analysis
•Customer feedback
•Refined WSJF
•Lightweight Business Case
•Go/No-Go decision
Backlog
•Approved Portfolio Epics
•Continuous re-prioritization (WSJF)
Implementation
•Epics Owners, Solution Management, Product Management decompose Epics into Capabilities, Program Epics, Features
•Transition of ownership to Value Stream, Program (“pull”)
Portfolio Kanban
14
Portfolio Epic
WIP-Limited WIP-Limited
Value Stream – Program Kanban
15
FunnelReview
WIP-Limited
Analysis
WIP-Limited
Value Stream Epics & Program Epics
FunnelAnalysis
WIP-LimitedBacklog Implementation Done
Capabilities & Features
8/11/2016
IBM’s SAFe Support
10,000-foot view
16
One-stop-shopping
17
IBM’s Support for SAFe 4.0• Overview Presentation• Link to IBM – SAI webinar• Domain Models• The “Beta” Templates• SAFe 4.0 Reports• Documentation: How to use the “beta” templates in CLM Configuring SAFe V4.0 in CLM
New!
http://jazz.net/safe
SAFe Support Timeline
18
CLM 6.0
•RTC SAFe 3.0 Program template
•JRS reports
CLM 6.0.1
•CLM SAFe 3.0 Portfolio templates
•Updated/new JRS reports
CLM SAFe 4.0 “Beta” Support
•Configuration Guidelines
•Published on jazz.net
CLM 6.0.2
•CLM Lifecycle Project Area for SAFe 3.0
CLM 6.0.3
•SAFe 4.0 Support (GA)
June 2015
December 2015
March 2016
April 2016
January 2016SAi publishes
SAFe 4.0
July 2014Scaled Agile Inc(SAi) publishes
SAFe 3.0
July 2016Enhancements to SAFe 4.0 “beta”
templates
4Q2016
Tooling configuration
Artifacts and attributes
Key concepts: Economic
ranking, lean thinking,
value-based delivery
Plans to support key
activities: Roadmap,
Kanban, WSJF Ranked List
Agile Team-based Planning
Reports
Built-in process guidance
SAFe 4.0 support Get your SAFe Portfolio up and running in an hour!
19
Enabling key SAFe concepts in tooling
20
Lean & Agile principles
Apply leaning thinking across the portfolio – at ALL levels! – to eliminate waste and respect work-in-process (WIP) limits
Provided through Kanban planning at each SAFe level
Economic thinking
Avoid the “loudest voice, biggest stick” syndrome
Rank and prioritize based on “biggest bang for the buck” – greatest value at lowest cost
Provided through calculated WSJF and WSJF-ranked backlogs for planning at all SAFe levels
Value-based delivery
Capture the notion of value, track it, report on it – improve it!
Provided through PI Objective at Value Stream, Program and Team levels with reports to track value delivery and trends
Process guidance
Help your team learn by doing
Process guidance embedded in the tooling through work item templates for common SAFe activities and methodology support
RTC Project Areas
CLM
Lifecycle Project AreaPortfolio
Program 1
Team 1A Team 1B
Program 2
Team 2A Team 2B Team 2C
RTC Project Areas
CLM
Lifecycle Project Area
Portfolio
Program 1
Team 1A Team 1B
Program 3
Team 2A Team 2B Team 2C
Collapse
one level
Value
Stream 2
Value
Stream 1
Support for 3- or 4-level SAFe topology
21
Program 2
Process templates enable you to set up a SAFe tooling
infrastructure that supports best practices out of the box!
Support for multiple processes, speeds, …
RTC Project Areas
CLM
Lifecycle Project Area
Portfolio
Program 1 Program 3
Team 2A Team 2B
Outsourced
Team
(Proxy)
Team 1A Team 1B
Multi-speed IT, mixture of agile and waterfall teamsOutsourced teams
Collapse
one level
Value Stream 2Value Stream 1
Program 2
RTC Project
Areas
(Third Party Tools)
Flexible configuration options allow you to choose
what works for you!
22
23
Evolving to a SAFe EnvironmentA typical pattern that starts with Change Management
CLM (RTC + RDNG + RQM)
Complete support for SAFe, all levelsCross-domain support for requirements, change and
quality management
RTC
Partial SAFe Portfolio/Value StreamLightweight requirements management (no formal
requirements or solutioning artifacts)
RTC
Complete support for SAFe Programs and TeamsLightweight requirements management (via RTC
work items)
Typical Adoption Paths: Two Patterns
24
SAFe Portfolio (with or without Value Streams)
•How does IT investment support business strategy?
•What is on our delivery roadmap?
•Where do we have delivery risk?
SAFe Program (with or without Teams)
•How do we orchestrate delivery of features across teams?
•How can we support agile and waterfall teams that need to collaborate?
•What are the dependencies across teams?
Meet in the Middle
Establish an “orchestration” layer
at the Program or Portfolio Level
Scale from the bottom up or
manage delivery from the top
down
8/11/2016
Eating our own dog food…
How we use SAFe to
deliver ALM tooling
25
How we “eat our own dog food”
26
Demonstration of ALM Portfolio, which uses CLM SAFe
4.0 tooling to orchestrate the planning and delivery of the
CLM and CE tooling:
RTC
RDNG
RQM
Rhapsody
Rhapsody/DM
RELM
Jazz Foundation
Jazz Reporting Service
Funnel
•Ideas from any stakeholder
•New business opportunities
•Business initiatives
•Architectural issues
•Cost reduction initiatives
Review
•Value Statement defined
•Initial WSJF triage
Analysis
•Solution trade-offs and analysis
•Customer feedback•Refined WSJF
•Lightweight Business Case
•Go/No-Go decision
•Value Stream Epics are created and placed in the Funnel
Backlog
•Approved Portfolio Epics
•Continuous re-prioritization (WSJF)
Implementation
•Value Stream Epics are “pulled” for Analysis by the Solution team
•In Analysis, Capabilities (both development and non-Development) are created in the Funnel
•Capacity planning occurs on Capabilities
ALM Portfolio Kanban
Portfolio Epic
WIP-Limited WIP-Limited
Input: Portfolio Epics
Output:
• Lightweight Business Case
• Value Stream Epics
• Capabilities Value Stream Backlog
27
The PI Planning Process – Value Stream Epics
Funnel
Epic Owner (Portfolio) creates initial Value Stream Epics with Value Statement
Review
Solution (Offering Mgmt) Team performs initial triage, sets WSJF
Analysis
Solution Manager/Architect refines into Capabilities to identify iterative development plan
Ready (for Approval)
Epic and Capabilities are Proposed on Value Stream Roadmap
Approved
Capabilities are Ready for Approval with allocated capacity resulting in a “green” PI plan
Moving Epics through the Kanban
Reviewing -> Analyzing -> Approved -> Ready ->
Capabilities created in the Funnel
28
Funnel
•Capability created by Solution (Offering) Manager/Architect
Analysis
•Solution (Offering) team performs capacity planning
Ready (for Approval)
• Initial capacity (estimated effort) assigned, proposed plan is green from capacity perspective
Approved
•Planned For is set on Capability
•Committed to next PI
Implementing
•Tracks link is created to Program-level work
The PI Planning Process – Capabilities
Moving Capabilities through the Kanban
Analyzing -> Approved -> Ready -> Implementing ->
29
Strategic
Theme
Portfolio EpicScope: Cross-Value Stream, Multi-year
Value Stream EpicScope: Cross-Program, > 1 Program
Increment
CapabilityScope: Cross-Program, Program Increment
Program EpicScope: Cross-Team, > 1 Program Increment
Feature (Capability) (Plan Item, …)Scope: Cross-Team, Program Increment
Story (Use Case)Scope: Sprint
Task (Technology)Scope: < Sprint
ALM Portfolio: Offering Management drives value delivery in collaboration with engineering
Portfolio Strategy and Initiatives“What” will differentiate us – aligned with business strategy“Why” will it do thatDefinition of solution/project that realizes the value delivery and ROI propositionEconomic thinking!!!
Technology Delivery“How” will we deliver capabilities Technology decisions live here
Refinement of “what” and “how”Refinement of Capabilities into FeaturesDemonstrable value at each iterationAssessment of value planned/actual at each PI boundary
Analysis (Solutioning)Detailed definition of Solution Intent and ContextFormal requirements “live” here (if necessary): System, User, Non-Functional RequirementsUse Cases: Scenarios, Roles, Wireframes
Breakd
ow
n in
to lo
wer levels o
f granu
larity –Po
rtfolio
> Valu
e Stream > P
rogram
> Team
Ref
inem
en
t an
d r
e-p
rio
riti
zati
on
is a
co
llab
ora
tive
eff
ort
b
etw
ee
n O
ffe
rin
g M
anag
em
en
t an
d E
ngi
ne
eri
ng
Off
eri
ng
Man
age
me
nt
Engi
ne
eri
ng
Program Increment =
Release
8/11/2016
Tooling Details
Under the hood…
31
Structure, artifacts, attributes…
32
ALM SAFe Domain Model - High Level
33
Kanban work flows for Epics, Capabilities, Features
FunnelReview
•WIP-Limited
Analysis
•WIP-Limited
Value Stream Epics/Program Epics
FunnelAnalysis
• WIP-Limited Backlog Implementing Done
Capabilities/Features34
Solution ElaborationTraceability from requirements management to change and quality management
Elaborate solutions
in a Value Stream
during Portfolio and
Value Stream Epic
Analysis• Links to change and
quality management
artifacts
• System, Non-
Functional and User
Requirements
• Modeling &
Architecture
• Design, Usage
Models, Scenarios
35
Link to change management work
items in RTC
Link to quality management
artifacts in RQM
Kanban Planning
SAFe KanbanSystem State
Groups
WIP Limits enforced
Program Epics with WSJF
Kanban process enforced through:
• WIP Limits: Warning shown in red, Error prevents violation
• Workflow: Inability to move Epics in violation of the process
• Calculated WSJF that automatically sorts
36
WSJF Ranked Backlog
Cost of Delay
User/Business Value
+
Time Criticality
+
Risk Reduction/Opportunity
Enablement
Investment Job Size
Set WSJF Component Values - WSJF automatically recalculates and list of
Features is resorted
37
Estimate the Story Points during
planning
Work Alignment
Strategic Themes
Features
Target Iteration Team-Level
work items
38
Progress Reports (Epic, Capability, Feature)
39
Quick visualization of Completed vs Planned work
items – Progress Reports
Dependencies
“Soft” Dependencies –
Blocked for a reason
“Hard” dependencies
between work items
Blocking Program
Blocked Program
40
Status
Features
Team work by status
Target iteration for Team work
41
Value Delivery
Overall achieved value for each
iteration
What was demonstrated?
What was the feature?
42
8/11/2016
Changes since March 2016
What’s new?
43
Guidance for adopting SAFe in your existing environment
44
Configuring the SAFe Methodology in CLM• Flow diagram• Post-project
initialization configuration docs
• And more…
Delta Updates (since 3-18-2016)
45
Definition of Done• Checklist tab on Capability, Feature, and Story
• Checklist Item Status enum and checklist attributes
• Query to display status on “Definition of Done”
Consolidated Roadmap Timeline
• “Umbrella” roadmap iteration that includes Backlog + Value Stream or Program iterations
Story Points (Effort) Estimating & Aggregation
• Numeric Story Points attribute on Story (hidden and calculated)
• Actual Story Points attribute on Feature, Capability, Epics (integer)
• Enables calculation/roll up of points in reports
Process Guidance• New and updated work item templates for the most typical SAFe activities for
all SAFe levels with links to process guidance
New/Updated Work Item Types/Attributes
(RTC)
• Risk, Defect, Retrospective (Portfolio)
• “How Found” attribute on Defect
• “Proposed” attribute for planning
• Decimal WSJF for additional precision
New/Updated Portfolio Artifacts (RDNG)
• Value Stream (updated), Program (new): Includes attributes to capture investment (capacity, dollars)
“Definition of Done”
46
A query widget on a
dashboard alerts you to
the status – and
violations! -- of your
“definition of done”
Consolidated Roadmap Timeline
47
View all work planned
for an iteration on the
roadmap or sitting on
the Backlog in one
place…
Story Points – Estimation/Aggregation
48
(Aggregated) Story Point Estimate
Graph shows count of aggregated work items, table shows Story Points
Estimated vs Actual Story Points
49
How is your team doing in estimating
Story Points?
Work Item Templates
50
Automatically
create tasks for
key SAFe
activities, linked
to process
guidance
automatically
8/11/2016
Next Steps & Resources
Looking ahead…
51
Work in progress…
52
New & Updated Plan Views
•Kanban views with additional attributes (Proposed, Estimated Story Points, Work Type)
•Backlog views – ranked list of Epics, Capabilities, Feature ready for implementation
•Roadmap views with Proposed, Work and Enabler Types, PI Objective
•Planning views to enable WSJF planning in a tree view
Automatic Story Point
Aggregation (Exploration)
•Roll up of Story Points from a Story to Feature, Capability and Epics
•Estimated Story Points rolled up when Story is created
•Actual Story Points rolled up when Story is completed
Reports
•Epic, Capability, Feature Progress
•Quality/Defect Status•Velocity, Burnup/Burndown
•Cumulative Flow
SAFe Capacity Planning
•Integration between CLM and IBM Program Work Center (IPWC)
SAFe Sandbox
•“Try before you buy” environment with sample data
SAFe YouTube Channel
53
Based on RTC 6.0, but
generally applicable
SAFe Webcast Calendar
54
Most recent SAFe 4.0 topics at the top…
Getting started resources for Scaled Agile Framework
Where can I learn more?
SAFe Landing Page: http://jazz.net/safe
SAFe Reporting
SAFe 4.0 Landing Page
Configuring the SAFe® Methodology in CLM
Blogs: Introducing SAFe in CLM V6.0.1Need SAFe 4.0 Support? Look no further… Keep your organization on track with CLM and SAFe® 4.0
One customer’s story: http://www.scaledagileframework.com/pole-emploi/
55
8/11/2016
Thank You
56
