Escalando Projetos Ágeis com SAFe e Jazz

1. SCALING AGILE
ESCALANDO PROJETOS ÁGEIS COM SAFE E JAZZ
Sandra Sergi Santos
ssergi@br.ibm.com

2. GOOD NEWS.....
2
By 2018 about 75% of IT companies
are using Agile methods of working.
Gartner
Scrum is a well-known agile development
method that provides a simple project
management framework for organizing
teams and their approach to system
development.
Gartner
Scrum Google Trends

3. BAD NEWS.....
3
Organization
[NON-AGILE PART]
Scrum
[AGILE-PART]
Need to Expand
Scaled Agile Framework
Google Trends

4. Development Team
Artifacts
SCRUM FRAMEWORK
Events
4
Source: Scrum Handbook

5. 5
WHY SCALE ?

6. 6
SAFE
Dean Leffingwell

7. The Foundation
7

8. Goal: Speed, Value, Quality
8

9. Lean Principles
9

10. Respect for People
10

11. Kaizen
11

12. Product Development Flow
12

13. The Framework
13

15. The Levels

16. Nothing Beats an Agile Team
16

17. Scale to the Program Level
17

18. Product Management Design Architects Development
EpicsAcceptedfortheBacklog
Scale to the Porfolio Level

19. The People

20. 20
50 to 125 People
SCALING TEAMS

21. The Backlogs

22. The Cadence

23. Code Quality

24. Economic
Priorization

25. Scaled Requirements
25

26. 26
EPICS
FEATURES
STORIES

27. 27
REQUIREMENT TYPES
Investment Theme
Epic
Feature
Story Story
Feature
Story Story
Epic
Feature
Story Story Stories fit in iterations,
implemented by tasks
Features fit in releases
Epics span releases
Budget/Capacity
Allocation Decision

28. 28
REQUIREMENTS SUPPORTS THE PLANS

29. 29
ART – AGILE RELESE TRAIN

30. 30
AGILE RELEASE TRAIN (ART)

31. RELEASE PLANNING
• Two days every 8-12 weeks
• Everyone attends in person if at all possible
• Product Management owns feature priorities
• Development team owns story planning and high-level estimates
• Architects, UX folks work as intermediaries for governance,
interfaces and dependencies
• Result: A committed set of program objectives for the next PI
Cadence-based PI/Release Planning meetings are the “pacemaker”
of the agile enterprise

32. SCALING THE PRODUCT OWNER
Source: Agile Portfolio and Program Management in the Scaled Agile Framework, Dean Leffingwell, Agile Melbourne Meetup, 15/02/12

33. 33
CLM SOLUTION SUPPORTING SAFE
COLLABORATIVE LIFECYCLE MANAGEMENT

34. IBM DevOps built on SAFe
34
SAFe
Market-leading process framework for scaling lean and agile across the
enterprise, providing guidance and best practices to help organizations
realize success
IBM DevOps Framework & Tooling
Supports the continuous delivery model through an open-standards-based
tooling platform to help drive organizational efficiency and effectiveness
Steer
Dev &
Test
Deploy Operate
Apply Lean & Agile Principles across the end-to-end DevOps lifecycle

35. Requirements Management
• Use case diagrams, sketching, UI mockups,
story boards
• Rich-text specifications
• Audit history
CLM CAPABILITIES
Tracking & planning
• Track bugs, defects,
enhancements
• Describe themes, epics,
stories
• Manage basic requirements
and test cases
• Supports agile or traditional
planning and estimating
• Manage backlogs, sprints,
releases
• Discussions preserved
• Agile Planning
Test Management for complex
systems or to meet compliance
mandates
• Comprehensive test suites
• Manual testing scripts
• Test lab management
• Traceability to formal
requirementsSoftware configuration management
• Use built-in component-based version
control, parallel development, change sets
• Or connect to your Git repositories
Continuous integration
• Build scheduling
• Rich build reporting linked to
tasks and source code
• Compare and reproduce builds
• Use built-in engine or popular
engines like Ant, Maven,
Hudson/Jenkins, etc…
Dashboards and reporting
• Instant status with reporting
automatically linked to work
being performed
• Hundreds of configurable
dashboard widgets, plus
external OpenSocial Gadgets,
IBM iWidgets
• Data warehouse for trend
analysis
Teams and process
• Know who is on your team
• Presence and chat in context
• Events and feeds keep you in the loop
• Out-of-the box processes for Agile/SAFe or
traditional, help the team follow best
practices
• Processes customizable on the fly for each
project
Continuou
s
Business
Planning
Collaborativ
e
Developme
nt
Continuou
s Testing
Source
Control
Continuou
s
Integratio
n
Continuous
Monitoring
Teams &
Process

36. Transparency is Mandatory in SAFe
36

37. Program as RTC
Project Area
managing Teams
as Team Areas in
same RTC Project
Area
Portfolio as RTC
Project Area
managing
Programs in
separate RTC
Project Areas
Organizing RTC Areas
Portfolio (RTC Project Area)
Program
(RTC Project Area)
Team
(RTC Team
Area)
…
…
Team
(RTC Team
Area)
…
Program/TeamPortfolio

38. SAFe backlogs = RTC Plans tied to Teams and Iterations
38

39. Team Structure
39

40. RTC Timelines for the Cadence
40

41. RTC SAFe Roles
41

42. Work Item Types
42

43. Work Item – Hierarchy (Rolloup Progress)
43

44. Weighted Shortest Job First – Auto calculated
44
WSJF = User Value + Time Value + Risk
Reduction|Opportunity Value)/Job Size
WSJF calculated for:
• Epics
• Features
• Stories

45. Pre-configured Work Item Workflows
45

46. Kanban Views
46

47. Dashboard Views
47

48. 48
REFERENCES

49. 49
TO STUDY
IBM Jazz.net SAFe Home
https://jazz.net/safe/
The framework
http://www.scaledagileframework.com/