Embed Size (px)
Citation preview
Throwing out the Agile Rulebook
LUISA RANDON • SR AGILE PROJECT MANAGER• AMGEN
Agenda S A F e o r n o t S A F e
P o r t f o l i o M a n a g e m e n t
R e l e a s e P l a n n i n g
T o o l s
SAFe or not SAFe
Scalability
Predictability
Visibility
Scaled Agile Framework™ Big Picture!
Speaking the same LanguageadKeep or discard?
Strategic Themes Themes
Business and Architecture Epics Epics, Initiatives
Business and Architecture Features
Epics
Stories Stories
Agile Teams
Product Owners
Chief Scrum Master(Release Train Engineer)
Scrum Masters
DevOpsArchitects
Product Managers(Group Product Owners)
SAFe but Simple
Portfolio Management Product Roadmap Release Planning Scrum work
Portfolio Management
Product Council Review
Product Managers Create Epics
PMs Cross- prioritize Epics
Product Owners break down Epics into User Stories
User Stories groomed planned into
Sprints
Everybody can create a Portfolio Request
Epics will be visible by Stakeholders and everybody else in the Portfolio Kanban board
Watchers
To Do In Progress Closed
Portfolio Program Board
When stakeholders have smaller requests!
Requestors (Watchers) get notified at every change
Reviewed
Reviewed by PM/PO daily
Story in JIRA and in Requests
Board
Open
Groomed by the Team
Ready
In Progress
In Sprint
Delivered
Closed
JIRA customized for stakeholders to enter small requirements
Release Planning and Scrum Work
Becoming predictable while “Develop on Cadence and Deliver on Demand”
Release Planning Synchronized Sprints
Normalized Story Points
1 3
8 2
5
13
3 Good Reasons to synchronized sprints across teams
Sprints Calendar should be available to everybody
Planning DependenciesTransparenciesRelease Planning
Useful for Large Estimation
Might Help to convert Story Points into Cost
Same value shared across the different teams (1 point = 1 ideal day)
Story Points Normalization
Many Epics across several teams
Story points
Align Business and Development
More than one Sprint at the same time
Release Planning or how to forecast your Product Increment
All teams planning together
TEAM 1
TEAM 2
TEAM 3
TEAM 4
TEAMS
User stories extracted automatically
Tools, next step
Tools, next steps…Portfolio for JIRA
Operations
Better view of higher level business Requirements (Initiatives and big Epics)
Think of Agile as a Tool Box
Give visibility into your entire process
Choose the right tools
Lessons Learned
