This document discusses Centric Consulting's approach to helping clients implement a "bimodal" IT model that supports both predictable "Mode 1" systems and more innovative "Mode 2" systems. It summarizes Centric's view that balancing speed and stability requires abstracting dependencies, aligning teams, embracing automation, and focusing on culture. Case studies demonstrate how Centric has successfully delivered Mode 2 applications while integrating with clients' Mode 1 operations through practices like microservices, cloud deployment, and iterative development.

1. NOTICE: PROPRIETARY AND CONFIDENTIAL
This material is proprietary to and contains trade secrets and information which is solely the property of Centric Consulting, LLC. It is solely for the Client’s internal use and shall not be used, reproduced, copied, disclosed, transmitted, in whole or in part,
without the express consent of Centric Consulting, LLC. © 2017 Centric Consulting, LLC. All rights reserved.
Making Bimodal IT a Reality
Scaling and running Agile Software Development
Teams without disrupting the current IT delivery
model.
May 9, 2017
Centric Development Studio

2. CONTENTS
• What is Bimodal?
• Challenges moving to Bimodal
• Centric’s Point of View on how to make Bimodal IT work
• Centric Services
• Centric’s Key Differentiators
The presentation addresses the following topics.
2

3. WHAT IS BIMODAL?
Gartner introduced prescriptive enterprise IT organizational model “Bimodal” in 2014.
3
Bimodal is the practice of managing two separate but
coherent styles of work – one focused on predictability
and the other on exploration.
Mode 1
Legacy Evolution
Mode 2
New and Innovative
• More predictable and well understood
• Focused on exploiting what is known and
• Renovating the legacy environment
• Exploratory
• Experimenting to solve new problems
• Optimized for areas of uncertainty
• Begins with hypothesis - tested and adapted
• Developed in short iterations
• Minimum Viable Product (MVP) approach
Gartner

4. TRENDS DRIVING BIMODAL
Digital business innovation is creating disruption - impacting people and technology.
4
 Digital Experience and Engagement – new ways to interact using technology
 Business Innovation – Disruptors: Google, Apple, Amazon, Facebook, Uber, etc.
 Ripple Effect – Expanding digital capabilities increases importance on Mode 1

5. CHALLENGES BEING BIMODAL
There is tension between Mode 1 legacy and Mode 2 innovation.
5
“Tension rises when dev teams operate outside the guardrails.”
Tension
Mode 1 Mode 2
Outsourcing
Contracts
On Premise
Infrastructure
SDLC ProcessIT Staffing & Skill
Mix
Tightly Coupled
Architecture
Data Security
Cloud First
Mobile First
Customer Facing
Innovation
Legacy New and Innovative
Guardrails – the predictable things ordinarily
done… known as “inertia.”
Agile
CI/CD
Automation
Forces Creating Tension
Release
Schedules

6. OBSTACLES WE ARE SEEING
Transitioning to Bimodal has many challenges – from technology to organization.
6
Turf Wars
DevOps, Infra, Arch.
Decision Conflicts
Culture
“Us vs Them”
Re-work Fear
Can’t fail –wait so
don’t create rework
Upfront Design
All Requirements
Before Dev Starts
Architecture
Tight Coupling
Creates Dependency

7. SPEED WITHOUT DISRUPTION
Overcoming obstacles in Mode 2 requires balancing speed without disrupting Mode 1.
7
Speed
Disruption
Rapid Startup
Embrace DevOps & Automation
Manage Priorities Against Backlog
Flex Resources to Balance Supply/Demand
Digital Innovation w/ Software
Faster Delivery
Lower Cost
Remove Tight Dependencies
Productive Teams
Make it Easy to change
Self Documentation
Goal: Don’t make it take longer than it needs to take.
Mode
1 + 2

8. CULTURE MATTERS
The organizational, culture and people impacts in Bimodal are paramount.
8
Mode 1 + Mode 2 Teams Go through
High Performing Team Stages
Form
Storm
Norm
Time
Performance
• Clear vision and purpose
• Mutual goals - 1+1=3
• Org alignment on technology
• DevOps and Legacy coexist
• Agile skills - Mode 1 and 2
• Test and learn mindset
• Culture norm - Failure is ok
• New thinking – its ok to change
• Knowing enough to get started
• Career paths – Mode 1 and 2
Cultural Factors in Bimodal

9. MAKING MODE 2 WORK
The new norm is iterative test and learn application development.
9
Goal: Shorten Feedback Loops by applying know patterns and practices.
Write failing
Unit Test
Make
Unit Test
Pass
Refactor
Repeat until acceptance
test passes
Write failing
Acceptance
Test
Verify
Feature
Complete
Repeat until feature is complete
Acceptance Test Driven Development
Discuss
Feature
and
Acceptance
Criteria
Backlog
Repeat until Backlog is empty
Promote
Code

10. SECRET SAUCE
Abstraction and alignment with Dev and Ops – such that Modes 1 and 2 applications
have common “shared” dependencies governed by contracts and known practices.
10
Mode 1 Mode 2
Tight Coupling
Implementing Agile
without Abstraction
“Mode 2 can only go
as fast as Mode 1”

11. SECRET SAUCE
Abstraction and alignment with Dev and Ops – such that Modes 1 and 2 applications
have common “shared” dependencies governed by contracts and known practices.
11
Mode 1 Mode 2
XTight Coupling
Infrastructure
• Shared File System
• API Gateway
• Asynchronous Queuing
• ESB
Contracts
Examples
Shared Dependencies
governed by contracts
Key: Address ownership
and accountability in IT
organization

12. INGREDIENTS
Here is how Centric makes Mode 2 work alongside Client’s Mode 1 teams.
12
Centric
Scrum
Team
Team
Tools – embrace automation
Space
Collaboration
• Preserve Core Team (SM, BA, etc.)
• Team trust and know each other
• Team Profiles – Know standard
technologies, Open Source, and are
curious learners
• Don’t use every tool – menu choices
• Team Boards (Jira, Pivotal, Trello, TFS)
• Source Control (GitHub mainly, TFS)
• CI/CD (TeamCity, TFS, Octopus)
• Testing (Cucumber, Selenium Web Driver)
• Coding (node.js, JavaScript, Java, .Net)
• Cloud (AWS, Azure, Heroku)
• Everything needed - nothing not needed
• Remove distractions - No bureaucracy
• Care and Feeding (Snacks/Drinks)
• Pleasant environment to work
• Balance public and private space
• Screen sharing, Video Conferencing
• Team Collaboration - Slack
• Transparency – Digital Team Boards
• Agile – build things that are easy to change
• Shorten feedback loop – embed client
• Show and Tells – what we have done
• Set priorities regularly
• Allow client to change mind

13. Centric Services
Centric helps client operate Bimodal with three service offerings
13
Readiness
Assessment and
Roadmap
Mode 2 Software
Development
Application Support
• Educate clients on bimodal – trends, hurdles, etc.
• Assess organizational readiness & gaps
• Create Roadmap and Plan for Bimodal journey
• Form Team - Columbus Dev Studio
• Align and Integrate with Mode 1 Teams
• Execute Agile software delivery in Mode 2
• Transition Mode 2 App Delivery to Support Model
• Leverage Centric India App Support Organization
• Align SLAs with Client Mode 1

14. BIMODAL PARTNERSHIP
• True Partnership (between Centric/Client and between Mode 1/2 teams)
• Open and frequent dialogue
• Candid expression of how things are working
• Honesty
• Leadership - client organizations committed to making bimodal work
• Culture Shift - Know and understand we may fail, and if we do, learn and make it better
• Apply Bimodal Success Factors
• Shared dependencies – not tight coupling
• Defined contracts and owners
• Alignment on technology stack/menu and IT direction
• Defined processes - Agile Development, DevOps, Team Collaboration, Backlog, etc.
• Agreed decision making and escalation process
These are “Must Haves” for a successful Centric and Client Bimodal partnership.
14

15. DIFFERENTIATORS
• We are humble. “It’s not our way or the highway approach”
• We work to integrate seamlessly within the client’s culture - it’s critical to success!
• Decouple Mode 2 application development from Mode 1 architecture dependencies
• Prepare to bring back application back into the Enterprise – right from the start
• Offer to run and support application after deployment
• Work as one – our goal is to ensure that the business needs are met… while
ensuring both Mode 1 and Mode 2 team members feel they are contributing
There are six key factors that make Centric a preferred Mode 2 Bimodal partner
15

16. CASE STUDY #1
Learning: Alignment between Agile teams and Client IT Dev and Ops teams is key.
16
Situation: US Healthcare Solutions provider needed a customer portal where they could
access account information, view documents and manage their account user preferences.
Challenges: Client was new to Agile software delivery and did not have a mature IT team.
What We Did: What We Learned:
• Built app in Java and JavaScript
• Consumed APIs to access patient info
• Leveraged productivity tools: Jira,
Confluence, GitHub, Selenium, Maven
• Deployed in Cloud – AWS
• Extended tech stack for new CSR App
• Now rewriting in Angular2
• Team dynamics key – know each other
• Anchor new teams w/ proven talent
• Spawn new teams from existing teams
• API versioning – w/o introducing
breaking changes
Key Takeaway: Need disciplined process to govern contracts – knowing when to change,
how to change, and by whom.

17. CASE STUDY #2
Learning: Abstraction of applications from infrastructure is key.
17
Situation: Global health care services company and leading American health care retailer
needed a system to reconcile generic drug pricing against contractual agreements.
Challenges: new joint company, No IT, very large data sets (>M trxs/day), AWS deployment,
High $ value/high risks.
What We Did: What We Learned:
• Built application in Java
• Deployed in AWS
• Extracted/imported from multiple db’s
• Performed daily reconciliations
• Created reporting UI
• Built analytic views – evaluated bids
• Provided comparative COGS
• Know team, trust team and their skills
• Leadership key – both SM and BA
• Poly-skilled team: i.e. SM with BA skills
• Insulate team from bureaucracy
• Analytics services in Azure (custom)
• Leverage Open Source tools
• Efficient processing: asynchronous
communication, micro services, etc.
Key Takeaway: Well defined contracts (applications to infrastructure) enable teams to move
at right speed.

18. SUMMARY
Here are the key characteristics of Centric’s successful Bimodal projects
18
● Team Culture – operate with humility, collaboration and transparency
● Micro services – flexibility to remove tightly coupled dependencies
● Alignment - Agile Teams and Mode 1 Dev and Ops teams w/ Patterns and Practices
● Cloud First – look to cloud first as an enabler for rapid startup
● Test and Learn – Embrace a “Fail, Learn, Grow” mindset
● Embrace automation – seek to shorten feedback loops
● Standards – align on design patterns and guidelines, not specs
● Agile – be product focused, apply iterative test and learn approaches

19. CENTRIC BIMODAL EVOLUTION
Our goal is to become the best software delivery partner for our clients.
19
2014 2015 2016 2017
• Get Better, Faster, Cheaper
• Choice “Partner” – Extension of IT
• Become “Go to Innovation Developer”
• Break thru Design Patterns / Practices
• Hire local IT Talent
Unmatched Client Experience
“Making Bimodal IT a Reality”
Est Dev
Studio
Launched 1st
Agile Team
Delivering at
Large Scale
Est Rapid
Launch
Model
Centric Milestones Future Goals
2020

20. CONTACT INFORMATION
20
Gina Heffner
Email: gina.heffner@centricconsulting.com
Phone: 740.485.2910
To learn more about Centric’s Bimodal Services,
contact:

21. THANK YOU!
21