Building Blocks of DevOps

DevOps includes both

1. New project management principles : agile and lean 
2. old-school principles : ITIL (Information Technology Infrastructure Library) , ITSM (IT Service Management), and SDLC

Let's see three building blocks of DevOps. 

1. DevOps should be extensions of Agile 

Iterative and incremental process

Agile Manifesto

1.1 Individual and interactions > processes and tools
1.2 working s/w > comprehensive documentation
1.3 customer collaboration > contract negotiona
1.4 Responding to change > following plan

12 principles

1.1 highest priority is satisfy customer with early + continuous valuable s/w delivery
1.2 welcome requirement change
1.3 frequent delivery of working s/w
1.4 business people and developer works together daily
1.5 motivated individual 
1.6 face to face conversation
1.7 working s/w is primary measure of progress
1.8 constant pace and sustainable development
1.9 technical excellence and good design
1.10 simplicity 
1.11 self organising team
1.12 retrospection


DSDM : Dynamic System Development Method
FDD : Feature Driven Development
eXtreme Programming
Rational Unified Process

Widely used are scrum, Kanban and lean. 

1.1 scrum

from rugby game
meaning: tight player formation that is trying to move the ball towards goal
Scrum Life Cycle : Product backlog -> Sprint Backlog -> Sprint -> Valuable product
Sprint = timebox of a month or less

1.2 kanban

5 principles

1.2.1 Visualize workflow
1.2.2 Limit WIP
1.2.3 Manage the flow
1.2.4 Make process policies explicit
1.2.5 Improve collaboratively 

SAFe (Scaled Agile Framework) to reduce complexity for large scale implementation. 
2. Lean 

Lean inspired by SPC, Kizen, DoE, JIT, ToC, quality tools

Value Stream Mapping

From Supplier to Customer : What Information and Materials are flowing 

Seven principles 

2.1 Eliminating waste 

waste = The effort spend on anything other than creating value

* Muda : Absorbs resources but no value. 7 wastes
       Type 1: Technical waste for compliance 
       Type 2: Plain waste
* Mura : unevenness , No regular flow of work. Overburden 
* Muri : overburden process, person or system. unevenness 

2.1.1 Partially done work
2.1.2 Extra Features
2.1.3 Re-Learning
2.1.4 Handoffs
2.1.5 Delays
2.1.6 Task Switching
2.1.7 Defects

2.2 Amplify Learning
2.3 Decide as late as possible
2.4 Deliver as fast as possible
2.5 Empower the team
2.6 Build an integrity
2.7 See the whole

Plan Do Check Act of Kaizen
Build Measure Learn Repeat in Lean

Four Principles

2.1. Pull scheduling
2.2. Kanban
2.3. Visual Management 
2.4. Employee empowerment

For software industry

2.1 Limiting WIP
2.2 Kanban Visibility to flow
2.3 Customer f/b
2.4 Empowered team

Upcoming : Lean UX

3. Six principles of Kaizen

3.1. Good process brings good results
3.2. Gemba
3.3. Speak with data
3.4. Take action to correct root cause

* Five Whys
* Focus on causes not symptoms
* Fish Bone : Equipment, Process, People, Materials, Environment, Management 
* Do not accept (1) No time (2) human error . People does not fail. Process fails. 

3.5. Team work
3.6. Kaizen is for everyone

4. ITIL (Information Technology Infrastructure Library), ITSM (IT Service Management) and SDLC


Post a Comment