The lost use cases of Operations

87
The Lost Use Cases of Operations JavaPolis 2007 - BOF

description

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.

Transcript of The lost use cases of Operations

Page 1: The lost use cases of Operations

The Lost Use Cases

of Operations

JavaPolis 2007 - BOF

Page 2: The lost use cases of Operations

Introduction

[email protected]

• Independent Consultant

• Projects & Operations

• Technical & Human Factor

• Try to get the FUN back in working

Page 3: The lost use cases of Operations

The Audience is listening...

Page 4: The lost use cases of Operations
Page 5: The lost use cases of Operations

Fighting your way past operations...

Page 6: The lost use cases of Operations
Page 7: The lost use cases of Operations

You might get ‘Luke’yas they screw up.

Page 8: The lost use cases of Operations
Page 9: The lost use cases of Operations

They WILL try to freeze your project

Page 10: The lost use cases of Operations
Page 11: The lost use cases of Operations

But you now dance to a new tune...

Page 12: The lost use cases of Operations
Page 13: The lost use cases of Operations

Will the battle ever end?

Page 14: The lost use cases of Operations

The JEDI win in the end?

Page 15: The lost use cases of Operations

The JEDI win in the end?

Jedi KnightProject

Page 16: The lost use cases of Operations

The JEDI win in the end?

Jedi KnightProject

Jedi KnightOperation

Page 17: The lost use cases of Operations

Why are we still fighting?

Page 18: The lost use cases of Operations

Project: ScrumCopyrights Softhouse

Page 19: The lost use cases of Operations

Operations: ITIL

Page 20: The lost use cases of Operations

Operations: ITIL

Scrum Forgets operation?

Page 21: The lost use cases of Operations

Operations: ITIL

Scrum Forgets operation?

Page 22: The lost use cases of Operations

One Product Owner ?

Page 23: The lost use cases of Operations

One Product Owner ?

ProjectText

Page 24: The lost use cases of Operations

One Product Owner ?

ProjectText

Page 25: The lost use cases of Operations

One Product Owner ?

ProjectText

Operations

Page 26: The lost use cases of Operations

Definition of DoneCopyrights Jeff Sutherland

Page 27: The lost use cases of Operations

Definition of DoneCopyrights Jeff Sutherland

Page 28: The lost use cases of Operations

Definition of DoneCopyrights Jeff Sutherland

OperationsMissing?

Page 29: The lost use cases of Operations

How is it done?

Page 30: The lost use cases of Operations

How is it done?

Dirt Road

Page 31: The lost use cases of Operations

How is it done?

Dirt Road

Cobble Stone

Page 32: The lost use cases of Operations

How is it done?

Dirt Road

Cobble Stone

Asphalt

Page 33: The lost use cases of Operations

“Project” on Wikipedia

Page 34: The lost use cases of Operations

“Project” on Wikipedia

• Project is a temporary endeavour undertaken to create a product or service

Page 35: The lost use cases of Operations

“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”

Page 36: The lost use cases of Operations

Complete backlog?

Page 37: The lost use cases of Operations

Complete backlog?

Where are the non functional requirements?

Page 38: The lost use cases of Operations

Complete backlog?

Where are the non functional requirements?

•Monitoring

Page 39: The lost use cases of Operations

Complete backlog?

Where are the non functional requirements?

•Monitoring•Disaster Recovery

Page 40: The lost use cases of Operations

Complete backlog?

Where are the non functional requirements?

•Monitoring•Disaster Recovery•Logging

Page 41: The lost use cases of Operations

Complete backlog?

Where are the non functional requirements?

•Monitoring•Disaster Recovery•Logging•Performance

Page 42: The lost use cases of Operations

Sort by Value

Project Operations

Page 43: The lost use cases of Operations

Sort by Value

Project Operations

MoneyWon

Page 44: The lost use cases of Operations

Sort by Value

Project Operations

MoneyWon

MoneyLost

Page 45: The lost use cases of Operations

Commited / Involved

Our project team is building a new application

You’ll run it for next

5 years

No thanks, they only stay here for the project and I

have to clean it up!

Page 46: The lost use cases of Operations

Order it now!

The Lost Use Cases of Operations

Now on

Itunes

Page 47: The lost use cases of Operations

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

Page 48: The lost use cases of Operations

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

Page 49: The lost use cases of Operations

Example 3: Passwords

Page 50: The lost use cases of Operations

Example 3: Passwords

• Application Server

Page 51: The lost use cases of Operations

Example 3: Passwords

• Application Server

• Monitoring Users

Page 52: The lost use cases of Operations

Example 3: Passwords

• Application Server

• Monitoring Users

• Backup User

Page 53: The lost use cases of Operations

Example 3: Passwords

• Application Server

• Monitoring Users

• Backup User

• Database Users

Page 54: The lost use cases of Operations

Example 3: Passwords

• Application Server

• Monitoring Users

• Backup User

• Database Users

• Endusers

Page 55: The lost use cases of Operations

Example 3: Passwords

• Application Server

• Monitoring Users

• Backup User

• Database Users

• Endusers

• Certificates

Page 56: The lost use cases of Operations

Example 3: Passwords

• Application Server

• Monitoring Users

• Backup User

• Database Users

• Endusers

• Certificates

• Power Users

Page 57: The lost use cases of Operations

Example 3: Passwords

• Application Server

• Monitoring Users

• Backup User

• Database Users

• Endusers

• Certificates

• Power Users

• Scripts

Page 58: The lost use cases of Operations

Example 3: Passwords

• Application Server

• Monitoring Users

• Backup User

• Database Users

• Endusers

• Certificates

• Power Users

• Scripts

• Mail User

Page 59: The lost use cases of Operations

Example 3: Passwords

• Application Server

• Monitoring Users

• Backup User

• Database Users

• Endusers

• Certificates

• Power Users

• Scripts

• Mail User

• ....

Page 60: The lost use cases of Operations

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?

Page 61: The lost use cases of Operations

Example 4: LogFiles

• Java Exceptions are usefull for developers

• LogFiles (more then debug, warn, finest)

• Dynamically enable logging

Page 62: The lost use cases of Operations

But off course it’s all

a software design problem!

Page 63: The lost use cases of Operations

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

Page 64: The lost use cases of Operations

“Enterprise” Triangle

Page 65: The lost use cases of Operations

“Enterprise” Triangle

Project

Page 66: The lost use cases of Operations

“Enterprise” Triangle

Project

Page 67: The lost use cases of Operations

“Enterprise” Triangle

Project Operations

Page 68: The lost use cases of Operations

“Enterprise” Triangle

Project Operations

Page 69: The lost use cases of Operations

“Enterprise” Triangle

Project Operations

Page 70: The lost use cases of Operations

Joined Effort

• Backup, Monitoring of your project environment

• One less worry on the infrastructure

• Test environments can be fully sized, representative environment

Page 71: The lost use cases of Operations

Operations needs help

• Project creates tools

• They use tools

• Operations misses f.i.

• Refactoring a Server

• Unit tests for OS

Page 72: The lost use cases of Operations

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

Page 73: The lost use cases of Operations

What can YOU do?

Page 74: The lost use cases of Operations

You care about software

Page 75: The lost use cases of Operations

One Partner is Safer

Page 76: The lost use cases of Operations

Practice Early

Page 77: The lost use cases of Operations

Invest money for the future

Page 78: The lost use cases of Operations

Real Life begins at 40.

Page 79: The lost use cases of Operations

Real Life begins at 40.Software begins at Operations

Page 80: The lost use cases of Operations

Non functional can be important

Page 81: The lost use cases of Operations

Let go, but not without support

Page 82: The lost use cases of Operations

Provide the necessary tools

Page 83: The lost use cases of Operations

In good and bad timesIn Project and Operations

Page 84: The lost use cases of Operations

Grow old together

Page 85: The lost use cases of Operations

Questions, Comments?

Page 86: The lost use cases of Operations

Thanks for coming

Page 87: The lost use cases of Operations

• StarWars/George Lucas

• Darth Vader Accident/Micheal-Boresh

• Definition of Done/ Jeff Sutherland

• Scrum Overview/Softhouse

• Chicken & Pigs/ Clark & Visdos

Copyrights go to