Ops giving speciﬁcations
To avoid this kind of surprises in the future, they invited operations people during the design
This way they could transmit their knowledge of the productions environment
and it was written down in the request for proposals.
Ops wrote down every requirement they could think of
But this Big Design UpFront resulted in and over complicated,
overly designed and over engineered solutions.
The solutions seems to be to integrate operations IN the project phase.
This both in the beginning and during the project.
So both in good and bad times...
Because these people will constantly think about ... logs
Ok, the operations team needs to be agile, and it needs to be integrated in the project.
How would the agile manifesto apply to YOUR work as an operations member
We value the items on the left more then on the right
Individuals and interactions
over processes and tools
ITIL has lot of practices for keeping things running.
It used to be a change moderator, but as development is more agile we need to adapt.
ITIL v3 is has introduced the notion of continuous improvement too.
Operations as a cost centre
Increase in Maturity can bring Value (Gartner scale)
There’s no magic tool
There’s no magic tool that can save you from bad organization. It still requires you to think!
Working software over
Working software over comprehensive Documentation
Working means working in operation (Scope Problem , Dev) / Working Service
Customer Collaboration over Contract Negotiation
Who’s the customer (Internal, External / Different ASP, Normal company, internal
Responding to change
over following a plan
Operations has been doing this for years. Every incident / issue requires us to react/
Our highest priority
is to satisfy the
early and continuous
delivery of valuable
Our highest priority is to satisfy the customers: endusers but also developers
What is early for the customer? 4d for a server, 2 min for a new account?
What is value is for customer?
DEV /Project = Creating value
Loss of Value (protect value) = OPS
Welcome changing requirements even
late in development. Agile processes harness
change for the customer’s competitive advantage
Ops are often very resistive to change. Bussines might require constant adaptation.
from a couple of
weeks to a couple of
months, with a
preference for the
Do things often so you get better at it.
Avoid Big bang migrations. Go in small steps.
Business people and developers must work
together daily throughout the project
Have operations in your project and afterwards
In good and bad times...
Build projects around
individuals. Give them
the environment and
the support they
need and trust them
to get the job done.
Different environments : dev, test, prepod, training, trial, prod, qa
Do you trust your developers to do deployment?
Do you any secrets/super power they don’t have?
The most efﬁcient
method of conveying
information to and with a
development team is
Don’t lock yourself in a small room with only email communication!
Working software is
the primary measure
It things work, and people are satisﬁed, you’re doing a good job!
developers, and users
should be able to
On call + daily job
extend deployment power beyond ops team to spread the load
Continuous Attention to
Technical Excellence and good
design enhances agility
Keep your skills sharp! You never know who is looking at you.
• One Product Owner?
• = Program Manager
Be clear on who is your customers. Your boss, project manager(s), tickets?
Incidents vs Projects
Avoid being a Shared resource, pick the phone, take complaints, and new projects
So you can commit to your work better.
Pair System Administration
Operations decided to go for pair sysadminstration
Project but also for incidents
Learning , spreading the knowledge (vs. specialist / hero culture)
• Burndown charts vs Qos
• Target, no absolute/ Estimation
Always try to improve yourself
Go virtual on your hardware. Stop your emotions ;-)
Automate things, that you don’t want to do over and over again.
DRY: don’t repeat yourself
Version control your stuff, use tools like puppet, chef in stead of custom scripts
Work in small steps
Changes in conﬁgurations: better traceability