Scaling Agile in the Enterprise

3,779 views

Published on

Published in: Technology, Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
3,779
On SlideShare
0
From Embeds
0
Number of Embeds
2,592
Actions
Shares
0
Downloads
92
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Scaling Agile in the Enterprise

  1. 1. Scaling Agile in the Enterprise ...with Atlassian tools SANDER BRIENEN • AVISI • @AVISI_ATLASSIAN • S.J.P.BRIENEN@AVISI.NL
  2. 2. Outline
  3. 3. Scaling agile to the enterprise How it began
  4. 4. February 2001: “ Define an alternative to a documentation driven, heavyweight software development process SOURCE: AGILEMANIFESTO.ORG ”
  5. 5. Agile Principles SOURCE: AGILEMANIFESTO.ORG
  6. 6. Agile Principles SOURCE: AGILEMANIFESTO.ORG
  7. 7. Agile Principles SOURCE: AGILEMANIFESTO.ORG
  8. 8. But what happens at scale?
  9. 9. Some figures 2,000 300 employees IT people 10 agile teams Project management Business alignment Operations department Architecture department Test department
  10. 10. Enterprise Challenges • Process and documentation culture • Underestimation of planning effort in agile • Complicated infrastructure
  11. 11. 3 step approach 1. Setup a team to implement Agile 2. As IT Management, set the example 3. Solve impediments to agile, continuously
  12. 12. Implementing Agile • Takes time • Requires change • Needs persistence
  13. 13. Changing the enterprise PEOPLE PROCESS TOOLS
  14. 14. Scaled Agile Framework by Dean Leffingwell http:// scaledagileframework.com
  15. 15. Scaled Agile Framework by Dean Leffingwell http:// scaledagileframework.com
  16. 16. 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
  17. 17. 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
  18. 18. Tools
  19. 19. 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
  20. 20. 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
  21. 21. In-context diagrams
  22. 22. Link documentation to JIRA
  23. 23. Create content with blueprints
  24. 24. Risk management with Blueprints
  25. 25. 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
  26. 26. Project structure in JIRA Portfolio planning Portfolio Program Backlog Application A THEMES Backlog Application B EPICS + STORIES
  27. 27. Team level • Define/Build/Test • Agile Teams • Developers • Testers • Product owners
  28. 28. Team level • Issue types: • User Story • Bug • Refactor task • Design task
  29. 29. Team level • Important Fields: • Story Point • Rank • Measure: • Velocity
  30. 30. Sprint planning in JIRA Agile
  31. 31. Program level • Program managers • Project managers • Release Management • Quality Assurance
  32. 32. Program level • Issue Types: • Business Epic • Architectural Epic • Bug • Task • Important Fields: • Business value
  33. 33. Cost vs Business Value Agile FIXED Features Time Time Budget Features FLEXIBLE Traditional Budget
  34. 34. Use Kanban to track progress
  35. 35. Manage the release train
  36. 36. Portfolio level • Portfolio Management • Enterprise architects • Portfolio managers
  37. 37. Portfolio level • Issue types: • Business Theme • Architectural Theme • Important fields: • Business value
  38. 38. Use Kanban to track progress
  39. 39. Create a long-term roadmap
  40. 40. Use FOLIO to manage budget
  41. 41. Track KPI’s on wallboards
  42. 42. 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
  43. 43. over 70 applications Front-office Back-office Enterprise service bus Service oriented architecture SAP Document management Mobile XML Gateway Web
  44. 44. 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
  45. 45. Traceability
  46. 46. To sum it up Does agile scale?
  47. 47. 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
  48. 48. “Big Design Up Front” vs. “Just Enough Specification”
  49. 49. Single Release vs. Continuous Delivery
  50. 50. No Change vs. Embrace Change
  51. 51. vs.
  52. 52. Thank you! SANDER BRIENEN • AVISI • @AVISI_ATLASSIAN • S.J.P.BRIENEN@AVISI.NL
  53. 53. 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

×