2. Scaling Agile in the Enterprise
...with Atlassian tools
SANDER BRIENEN
•
AVISI
•
@AVISI_ATLASSIAN
•
S.J.P.BRIENEN@AVISI.NL

3. Outline

4. Scaling agile
to the enterprise
How it began

8. February 2001:
“
Define an alternative to a
documentation driven,
heavyweight software
development process
SOURCE: AGILEMANIFESTO.ORG
”

9. Agile Principles
SOURCE: AGILEMANIFESTO.ORG

10. Agile Principles
SOURCE: AGILEMANIFESTO.ORG

11. Agile Principles
SOURCE: AGILEMANIFESTO.ORG

12. But what happens
at scale?

13. Some figures
2,000 300
employees
IT people
10
agile teams
Project management Business alignment
Operations department
Architecture department
Test department

14. Enterprise Challenges
• Process and documentation culture
• Underestimation of planning effort in agile
• Complicated infrastructure

15. 3 step approach
1. Setup a team to implement Agile
2. As IT Management, set the example
3. Solve impediments to agile, continuously

16. Implementing Agile
• Takes time
• Requires change
• Needs persistence

17. Changing the enterprise
PEOPLE
PROCESS
TOOLS

18. Scaled Agile Framework
by Dean Leffingwell
http://
scaledagileframework.com

19. Scaled Agile Framework
by Dean Leffingwell
http://
scaledagileframework.com

20. P O R E P F CO L I O
T I S
realized by
1
1..*
P F EO T U R EA M
R A G R S
realized by
1
1..*
STE RIES
T O A M

21. T E P IM E S
HE CS
realized by
1
1..*
F E E P IU R E S
AT CS
realized by
1
1..*
STORIES

23. Tools

24. Enterprise Challenges
P R O C ES S A ND D O C U MENT A T IO N C U LT U R E
U ND ER ES T IMA T IO N O F P LA NNING EF F O R T IN A GILE
C O MP LIC A TED INF RA S TRU C TU RE

25. Challenge #1
P R O C ES S A ND D O C U MENT A T IO N C U LT U R E
U ND ER ES T IMA T IO N O F P LA NNING EF F O R T IN A GILE
C O MP LIC A TED INF RA S TRU C TU RE
Central, easy to access, documentation
is key

26. In-context diagrams

27. Link documentation to JIRA

28. Create content with blueprints

29. Risk management with Blueprints

30. Challenge #2
P R O C ES S A ND D O C U MENT A T IO N C U LT U R E
U ND ER ES T IMA T IO N O F P LA NNING EF F O R T IN A GILE
C O MP LIC A TED INF RA S TRU C TU RE
Agile is all planning
about just-in-time

31. Project structure in JIRA
Portfolio
planning
Portfolio
Program
Backlog
Application A
THEMES
Backlog
Application B
EPICS
+
STORIES

32. Team level
• Define/Build/Test
• Agile Teams
• Developers
• Testers
• Product owners

33. Team level
• Issue types:
• User Story
• Bug
• Refactor task
• Design task

34. Team level
• Important Fields:
• Story Point
• Rank
• Measure:
• Velocity

35. Sprint planning in JIRA Agile

36. Program level
• Program managers
• Project managers
• Release Management
• Quality Assurance

37. Program level
• Issue Types:
• Business Epic
• Architectural Epic
• Bug
• Task
• Important Fields:
• Business value

38. Cost vs Business Value
Agile
FIXED
Features
Time
Time
Budget
Features
FLEXIBLE
Traditional
Budget

39. Use Kanban to track progress

40. Manage the release train

41. Portfolio level
• Portfolio Management
• Enterprise architects
• Portfolio managers

42. Portfolio level
• Issue types:
• Business Theme
• Architectural Theme
• Important fields:
• Business value

43. Use Kanban to track progress

44. Create a long-term roadmap

45. Use FOLIO to manage budget

46. Track KPI’s on wallboards

47. Challenge #3
P R O C ES S A ND D O C U MENT A T IO N C U LT U R E
U ND ER ES T IMA T IO N O F P LA NNING EF F O R T IN A GILE
C O MP LIC A TED INF RA S TRU C TU RE
One Backlog to Kill them All

48. over
70
applications
Front-office
Back-office
Enterprise service bus
Service oriented architecture
SAP
Document
management
Mobile
XML Gateway
Web

49. Portfolio
planning
Portfolio
THEMES
Program
EPICS
+
STORIES
Backlog
Application A
Team
Backlog
Application B
TASKS
Planboard
Feature Team X
Planboard
Component Team
Y
Planboard
Component Team
Z

50. Traceability

51. To sum it up
Does agile scale?

52. Success factors
Setup Agile Implementation Team
Create 3 levels of planning and
JIRA project for portfolio planning and
roadmap
JIRA project structure that follows architecture
Scrum boards per team to manage backlogs

53. “Big Design Up Front”
vs.
“Just Enough Specification”

54. Single Release
vs.
Continuous Delivery

55. No Change
vs.
Embrace Change

56. vs.

57. Thank you!
SANDER BRIENEN
•
AVISI
•
@AVISI_ATLASSIAN
•
S.J.P.BRIENEN@AVISI.NL

58. Rate this Talk
Scaling Agile in the Enterprise
Text code below to 22333
or visit http://bit.ly/15C9dzf
MEH = 2U
NO T BA D = 2V
P R ET T Y GO O D = 2W
A WES O ME = 2X
To join this session, send text 136888 to