2. 2
Introduction
“The DevOps Journey” webinar series
Sept. 30 High Performance Team Collaboration
Oct. 28 Increase the Speed of Software Delivery
(ft. XebiaLabs)
Today Managing Distributed Delivery
Dec. 16 How to Implement DevOps
2016 To be announced
3. 3
Introduction
Housekeeping
▶ All visitors are on “mute”
▶ Please use the webinar tool to submit questions
(these will be logged and addressed in the Q&A
section)
▶ This session is being recorded and will be made
available after the Webinar
▶ Slide deck will be shared after the presentation
▶ No names of specific customers will be mentioned.
4. 4
Introduction
Today’s speakers and panelists
Jeroen Heikens
Practice Manager DevOps
Atos
John Brouwer
Theme Director DevOps
Atos
Stefan Groot
Business Consultant
Atos
Ineke Vermeulen
Global Head of C&SI Marketing
Atos
Jeevan T.M.
Thought leader DevOps
Atos
Email:
Jeevan.tm@atos.net
Arijit Sarbagna
Agile & DevOps Practice
Lead
Atos India
Email:
arijit.sarbagna@atos.net
5. 5
Todays’ agenda
▶ Welcome and Introduction
▶ Vision DevOps
▶ Managing Distributed Delivery
– “What” and “Why” of Distributed Delivery
– Typical approach
– Pitfalls and Solutions
– Beyond obvious
▶ Closing presentation
▶ Question and Answers
▶ Closing webinar
6. 6
Organization
Business
Business
Processes &
Organization
Products
& Services
IT
IT
Mission / Vision
Market
Competitors
Chain partner
Channels
Market is changing:
▶ New business models
▶ Shift to different and new channels
▶ Customers (consumers / citizens)
demand and depend on online contact.
▶ New ways and more intense
cooperation between organizations
and customers.
Business is changing:
▶ Even faster changing need
▶ More channels and more
distinctiveness.
▶ Brand is getting more
important
▶ Flexible cooperation.
IT has to change:
▶ The IT landscape has to
support the business and
respond to changing needs.
▶ The IT landscape is often rigid
through legacy.
Can the IT organization of the past respond to these new changes?
IT
Processes &
Organization
Business
Processes &
Organization
Products
& Services
Vision DevOps
IT organizations face an increasingly faster changing world
7. 7
Vision DevOps
DevOps finishes what Agile has started
Business
Domain A
Business
Domain B
Customers
Organization
Business
focus on speed
and flexibility
focus on continuity
Application
management
Infrastructure
Management
Agile
Development DevOps
Operations
Infrastructure
project
Application
Development
Development
Feedback
idea / incident / enhancement
Product
focus on customer
8. 8
Vision DevOps
The promises of DevOpsCASHFLOW
BETTER Customer
Satisfaction
FASTER Time to
Market
LOWER Cost
Traditional practices
DevOps practices
IMPROVED Stability
and Quality
APPLICATION LIFECYCLE (TIME)
> 8
12 times
faster
50%
fewer
failures
Up to
50%
10. 10
Cornerstones of DevOps
10
Vision DevOps
Empowered, self-organizing, cross-functional,
stable and knowledgeable teams
Integrated IT solution stack and use of
standardized and proven services
Automation of repetitive manual IT tasks
(build, deploy, test, release and monitor)
Iterative way of working based on business
priorities and continuous improvement
Make Agile
Collaborate
Automate
Simplify &
standardize
11. 11
DevOps: area’s of interest
11
Vision DevOps
Knowledge
Compe-
tences
Commitment
Management
of change
Culture & People
Deployment
Pipeline
Provisioning
environ-
ments
Enablement
Transfor-
mation
Chains
Rationali-
zation
IT Landscape
Structure
Collaboration
within
the team
Collaboration
outside
the team
Economics /
Budget
Organization
Team based
Product
based
Enterprise
based
Measure-
ment
Learning &
Improvement
Customer
satisfaction
Agreement Evidence
Performance
Time to
market
14. 14
Distributed Delivery
▶ What do we mean by DISTRIBUTED?
– A distributed environment refers to an environment where we do not all work in the
same place
▶ Why we need DISTRIBUTED AGILE Teams?
– The answer speaks to the reality of doing business today: a company’s need to have a
global presence, to access global talent and to develop outsourced options (cost benefits
associated).
17. 17
What is actually Distributed?
▶ Infrastructure (via Cloud)
▶ Requirement (using ALM)
▶ Talent (via PMO)
▶ Communication/Collaboration (via Tools/Platforms)
▶ Governance (with councils)
Private Public
Public
Public
Hybrid Cloud
18. 18
Team Distribution Challenges
▶ Questions
– Where will be the PO (Product Owner)?
– Where will be Scrum Master?
– Where is the Architect going to be placed?
– How do we engage the split members?
– How do we track progress?
– When/how to drive Daily Standup?
– How often do we collaborate?
– What should be the composition of the split
members?
MinorityMajority
23. 23
Distributed Delivery
Distribution models
Team 1 1
Team 2
Team 1 Team 2
Advantages :
1. Team presence on both shore
2. Easy coordination with client
Challenges:
1. Problems with the collaboration
2. More Dependency
3. People and Culture
4. Time zone
Advantages :
1. Easy intra team collaboration
2. Less Dependency
3. Better team velocity
Challenges:
1. Time zone
2. Coordination with client
24. 24
Distributed Delivery
Best Practices
Align Business and delivery teams by functional area.
A single voice of the customer for each team.
Vertical slicing of user stories
Post-daily scrum, collaboration
Scrum of Scrums
Look for trends, learn fast and adapt fast; don’t overreact to one “bad” iteration
Focus on the Agile values
Maintain real time data on ALM ( Jira, Rally, TFS etc. )
Use Collaborative Tools
Web Conferencing ,Google Hangout, Skype,
Lync .Phone, Wiki, Email, Chat etc.
25. 25
Implementation approach
Distributed Delivery
Preparing
Selecting
Forming
Training
Landing & Swarming
Performing
Distributing
Rotating
Selecting
Forming &
Training
Swarming:
Storming &
Norming
Performing
Evaluating
Based on Tuckmans: Forming, Storming, Norming, Performing
Team
Skill matrix with:
• Technical
• Functional
• Business domain
• Big 5
”Swarming is
simply the act
of coming
together to
solve a
problem or
get something
done quickly”.
DISC
D : dominance
I : influence
S : supportive
C : critical thinking
• Retrospectives
• Performance
monitoring
• Coaching /
Guidance
Distributing
26. 26
Case study
Organization & Teams
Program Manager
Cost Management
Contract Management
Stakeholder Management
DevOps Coach
DevOps Enablement
Team Productivity , coherence &
collaboration
Story Dependency management
Architect
Architecture
Software Quality
procedures
Development
Guidelines
Product Owner
Scrum MasterScrum MasterScrum Master Scrum Master
Scrum Master
Proxy Product Owners
Dev Team 1
Netherlands
Dev Team 3
India
Ops Team
Netherlands
Dev Team 2
Netherlands
28. 28
Atos Adaptive Agile Framework - AAAF
1. A Flexible, Light-weight and Scalable delivery model
2. Resonates best practices of industry established frameworks (e.g. Scrum, LeSS,
Nexus, SAFe) – with strong binding to DevOps culture
3. Focused on delivering QUALITY at a faster pace
4. Provides flexibility to adapt – either a project flow or DevOps
5. Ready to spread across locations/geography
29. 29
Do you want to learn more about DevOps?
Contact Atos
John Brouwer
Theme Director DevOps
john.brouwer@atos.net
