Download - The lost use cases of Operations

The Lost Use Cases

of Operations

JavaPolis 2007 - BOF

Introduction

• [email protected]

• Independent Consultant

• Projects & Operations

• Technical & Human Factor

• Try to get the FUN back in working

mailto:[email protected]

mailto:[email protected]

The Audience is listening...

Fighting your way past operations...

You might get ‘Luke’yas they screw up.

They WILL try to freeze your project

But you now dance to a new tune...

Will the battle ever end?

The JEDI win in the end?


Jedi KnightProject


Jedi KnightProject

Jedi KnightOperation

Why are we still fighting?

Project: ScrumCopyrights Softhouse

Operations: ITIL

Operations: ITIL

Scrum Forgets operation?

One Product Owner ?

One Product Owner ?

ProjectText

One Product Owner ?

ProjectText

Operations

Definition of DoneCopyrights Jeff Sutherland

Definition of DoneCopyrights Jeff Sutherland

OperationsMissing?

How is it done?

How is it done?

Dirt Road

How is it done?

Dirt Road

Cobble Stone

How is it done?

Dirt Road

Cobble Stone

Asphalt

“Project” on Wikipedia


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


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

Complete backlog?

Complete backlog?

Where are the non functional requirements?

Complete backlog?


•Monitoring

Complete backlog?


•Monitoring•Disaster Recovery

Complete backlog?


•Monitoring•Disaster Recovery•Logging

Complete backlog?


•Monitoring•Disaster Recovery•Logging•Performance

Sort by Value

Project Operations

Sort by Value

Project Operations

MoneyWon

Sort by Value

Project Operations

MoneyWon

MoneyLost

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!

Order it now!

The Lost Use Cases of Operations

Now on

Itunes

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

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

Example 3: Passwords


• Application Server



• Monitoring Users




• Backup User




• Backup User

• Database Users




• Backup User

• Database Users

• Endusers




• Backup User

• Database Users

• Endusers

• Certificates




• Backup User

• Database Users

• Endusers

• Certificates

• Power Users




• Backup User

• Database Users

• Endusers

• Certificates

• Power Users

• Scripts




• Backup User

• Database Users

• Endusers

• Certificates

• Power Users

• Scripts

• Mail User




• Backup User

• Database Users

• Endusers

• Certificates

• Power Users

• Scripts

• Mail User

• ....

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?

Example 4: LogFiles

• Java Exceptions are usefull for developers

• LogFiles (more then debug, warn, finest)

• Dynamically enable logging

But off course it’s all

a software design problem!

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

“Enterprise” Triangle


Project


Project Operations

Joined Effort

• Backup, Monitoring of your project environment

• One less worry on the infrastructure

• Test environments can be fully sized, representative environment

Operations needs help

• Project creates tools

• They use tools

• Operations misses f.i.

• Refactoring a Server

• Unit tests for OS

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

What can YOU do?

You care about software

One Partner is Safer

Practice Early

Invest money for the future

Real Life begins at 40.

Real Life begins at 40.Software begins at Operations

Non functional can be important

Let go, but not without support

Provide the necessary tools

In good and bad timesIn Project and Operations

Grow old together

Questions, Comments?

Thanks for coming

• StarWars/George Lucas

• Darth Vader Accident/Micheal-Boresh

• Definition of Done/ Jeff Sutherland

• Scrum Overview/Softhouse

• Chicken & Pigs/ Clark & Visdos

Copyrights go to

Download - The lost use cases of Operations

Top Related