The lost use cases of Operations

6,715 views

Published on

A lot of projects are doing Scrum now. Still they hit the wall of operations. Why is this actor so often forgotten?
We found some patterns that seem to amplify and reduce this behaviour. We hope to reduce this virtual wall and to put the fun back into projects.
As this might be different for you organization we are hoping for your interaction as well.

Published in: Technology
2 Comments
6 Likes
Statistics
Notes
No Downloads
Views
Total views
6,715
On SlideShare
0
From Embeds
0
Number of Embeds
52
Actions
Shares
0
Downloads
205
Comments
2
Likes
6
Embeds 0
No embeds

No notes for slide

The lost use cases of Operations

  1. 1. The Lost Use Cases of Operations JavaPolis 2007 - BOF
  2. 2. Introduction • Patrick.Debois@jedi.be • Independent Consultant • Projects & Operations • Technical & Human Factor • Try to get the FUN back in working
  3. 3. The Audience is listening...
  4. 4. Fighting your way past operations...
  5. 5. You might get ‘Luke’y as they screw up.
  6. 6. They WILL try to freeze your project
  7. 7. But you now dance to a new tune...
  8. 8. Will the battle ever end?
  9. 9. The JEDI win in the end?
  10. 10. The JEDI win in the end? Jedi Knight Project
  11. 11. The JEDI win in the end? Jedi Knight Jedi Knight Project Operation
  12. 12. Why are we still fighting?
  13. 13. Copyrights Softhouse Project: Scrum
  14. 14. Operations: ITIL
  15. 15. Scrum Forgets operation? Operations: ITIL
  16. 16. Scrum Forgets operation? Operations: ITIL
  17. 17. One Product Owner ?
  18. 18. ProjectText One Product Owner ?
  19. 19. ProjectText One Product Owner ?
  20. 20. ProjectText Operations One Product Owner ?
  21. 21. Copyrights Jeff Sutherland Definition of Done
  22. 22. Copyrights Jeff Sutherland Definition of Done
  23. 23. Operations Missing? Copyrights Jeff Sutherland Definition of Done
  24. 24. How is it done?
  25. 25. Dirt Road How is it done?
  26. 26. Dirt Road Cobble Stone How is it done?
  27. 27. Dirt Road Asphalt Cobble Stone How is it done?
  28. 28. “Project” on Wikipedia
  29. 29. “Project” on Wikipedia • Project is a temporary endeavour undertaken to create a product or service
  30. 30. “Project” on Wikipedia • Project is a temporary endeavour undertaken to create a product or service • The word Project comes from the Latin word “projectum”, “to throw something forwards”
  31. 31. Complete backlog?
  32. 32. Where are the non functional requirements? Complete backlog?
  33. 33. •Monitoring Where are the non functional requirements? Complete backlog?
  34. 34. •Monitoring •Disaster Recovery Where are the non functional requirements? Complete backlog?
  35. 35. •Monitoring •Disaster Recovery •Logging Where are the non functional requirements? Complete backlog?
  36. 36. •Monitoring •Disaster Recovery •Logging •Performance Where are the non functional requirements? Complete backlog?
  37. 37. Project Operations Sort by Value
  38. 38. Project Operations Money Won Sort by Value
  39. 39. Project Operations Money Money Won Lost Sort by Value
  40. 40. No thanks, they only stay here for the project and I Our project team is building You’ll run have to clean it up! a new application it for next 5 years Commited / Involved
  41. 41. Now on Itunes The Lost Use Cases of Operations Order it now!
  42. 42. Example 1: Monitoring • 1 functionality = 3 implementations • Unit Tests • System Tests • End-To End Monitoring • Component Monitoring is not enough • Reports on usage, trends • One failure should not make OPS blind
  43. 43. Example 2: Disaster • Start/Stop Sequence • Database, Directory Server, Application Server, FileServer ... • Database down, what with connection pooling? Frameworks hide things. • Active/Active vs. Active/Passive • It will fail, how bad will it be? Risk vs. Budget
  44. 44. Example 3: Passwords
  45. 45. Example 3: Passwords • Application Server
  46. 46. Example 3: Passwords • Application Server • Monitoring Users
  47. 47. Example 3: Passwords • Application Server • Monitoring Users • Backup User
  48. 48. Example 3: Passwords • Application Server • Monitoring Users • Backup User • Database Users
  49. 49. Example 3: Passwords • Application Server • Monitoring Users • Backup User • Database Users • Endusers
  50. 50. Example 3: Passwords • Application Server • Monitoring Users • Backup User • Database Users • Endusers • Certificates
  51. 51. Example 3: Passwords • Application Server • Monitoring Users • Backup User • Database Users • Endusers • Certificates • Power Users
  52. 52. Example 3: Passwords • Application Server • Scripts • Monitoring Users • Backup User • Database Users • Endusers • Certificates • Power Users
  53. 53. Example 3: Passwords • Application Server • Scripts • Monitoring Users • Mail User • Backup User • Database Users • Endusers • Certificates • Power Users
  54. 54. Example 3: Passwords • Application Server • Scripts • Monitoring Users • Mail User • Backup User • .... • Database Users • Endusers • Certificates • Power Users
  55. 55. Example 4: Config Files • Right amount of configuration • Operation does not care about threads, class loaders , Connection Pools • They care about FilePath changes, IP Changes, Name changes ... • Do you require downtime?
  56. 56. Example 4: LogFiles • Java Exceptions are usefull for developers • LogFiles (more then debug, warn, finest) • Dynamically enable logging
  57. 57. But off course it’s all a software design problem!
  58. 58. What will it cost you? • 1 day late project vs. 1 day downtime • Week work versus Weekend work • Test Environment vs. Risk of Patches • 10 users in Pilot vs. 10.000 user in Live • Your product owner might rethink priorities
  59. 59. “Enterprise” Triangle
  60. 60. Project “Enterprise” Triangle
  61. 61. Project “Enterprise” Triangle
  62. 62. Project Operations “Enterprise” Triangle
  63. 63. Project Operations “Enterprise” Triangle
  64. 64. Project Operations “Enterprise” Triangle
  65. 65. Joined Effort • Backup, Monitoring of your project environment • One less worry on the infrastructure • Test environments can be fully sized, representative environment
  66. 66. Operations needs help • Project creates tools • They use tools • Operations misses f.i. • Refactoring a Server • Unit tests for OS
  67. 67. Aford a test Deadthstar? • A good test environment will serve for the project • But also in operations • for patches • testing incidents • upgrades • reuse of unit testing
  68. 68. What can YOU do?
  69. 69. You care about software
  70. 70. One Partner is Safer
  71. 71. Practice Early
  72. 72. Invest money for the future
  73. 73. Real Life begins at 40.
  74. 74. Real Life begins at 40. Software begins at Operations
  75. 75. Non functional can be important
  76. 76. Let go, but not without support
  77. 77. Provide the necessary tools
  78. 78. In good and bad times In Project and Operations
  79. 79. Grow old together
  80. 80. Questions, Comments?
  81. 81. Thanks for coming
  82. 82. Copyrights go to • StarWars/George Lucas • Darth Vader Accident/Micheal-Boresh • Definition of Done/ Jeff Sutherland • Scrum Overview/Softhouse • Chicken & Pigs/ Clark & Visdos

×