At FlowStates, “DevOps” is how we’ve always designed and delivered our services, even before the phrase was coined. When successful transformations hinge on cultural unity, trust and process consistency, attempting large scale DevOps transformations in any size organization is not for the faint of heart. It takes courage, patience, honesty, humility and leadership.

What would a transformation look like?  There is no formal definition of DevOps, but there are some principles everyone agrees upon.  Ultimately it is about delivering the right value to your businesses in the most effective way possible.  It is about delivering a constant stream of usable features instead of waiting for 2 releases a year.  It is about creating a collaborative IT atmosphere and shifting quality to the front of the development cycle.  Studies show that when these elements are present in an IT organization, it is a predictor of overall firm performance.

Every organization will be different, both in desired outcomes and in their starting points.  They will have different skills, cultures, and impediments.

We’ve created a DevOps path that consists of 5 levels which build upon each other.  Each level has a prerequisite of the prior foundational sections.


wall     Phase 1 – Foundations & Principles:

Education, Boot Camps, Team & Executive Reviews

Process-52      Phase 2 – Assessments:

Assess Culture, Process Interactions and Automation / Tooling States

Collaboration Filled-100     Phase 3 – Strategy & Design:

Create Roadmaps, Reference Models / Processes and Proofs

setting-flow-interface-symbol (Custom)     Phase 4 – Transformation:

Guide, Coach and Implement combinations of Culture, Process and Delivery Transformations

Resize Four Directions-50    Phase 5 – Service Scaling:

Operationally Scale into Divisional and Enterprise Services, including organizational alignments


The FlowStates Transformation Process

There are 5 general phases to a long-term Transformation Engagement.

Each phase is designed to be a self-contained step in the DevOps transformation.  The caveat is that should a client wish to achieve higher levels of transformation or mastery, the phases must follow the sequence above.

In the spirit of DevOps, Consulting Engagements are designed such that a client can experiment with low-commitment early phases, and continue to layer phases if they are seeing the outcomes they want.  It also means that the early phases are truly quick efforts for learning and baselining your organization as input to your broader IT Strategy discussions.

For clients that are committed to the long-term transformation, the phases may proceed in parallel  for many steps so we can compound and accelerate the transformation where possible.

If a client chooses a longer engagement with execution results, the earlier phases tend to be ongoing and more detailed.  We may overlap efforts in phases to accelerate the overall change and reinforce various aspects of the overall transformation.  So for example, the Foundations and Assessments phase may be continuous as we enter a Strategy / Design phase.

More details on each phase will be posted shortly.