Agile Computing Authors: Yeshim Deniz, Pat Romanski, Liz McMillan, Elizabeth White, Andy Thurai

Related Topics: @DevOpsSummit, Agile Computing, @CloudExpo

@DevOpsSummit: Blog Post

Where to Begin Your DevOps Journey By @Datical | @DevOpsSummit [#DevOps]

How long your journey takes depends on where you begin

Sanjeev Sharma, IBM's worldwide lead for DevOps technical sales, wrote an article recently describing a process for mapping out an IT organization's DevOps transformation (see article here).  As more and more IT professionals hear about the benefits and success stories in DevOps, they naturally begin their own investigations to determine if it would be a good fit for their organizations. One of the first questions they ask, and that Sanjeev hears often when consulting with clients, is about how long a DevOps transformation will take.

"A question I get asked often is how long will it take my organization to adopt DevOps? First of all, one does not just adopt DevOps. One starts a journey of adopting the capabilities that make up DevOps (more on that soon). Adopting DevOps is not a one-time thing – it is an ongoing thing. That said, even when it comes to adopting a single capability of DevOps, say Continuous Delivery, how long it takes you depends on where you start."

That last part – "how long it takes you depends on where you start" – is probably the most important factor in determining how long your transformation will take.  Remember that for any journey, you can't get to where you want to go if you don't know where you are.  If your organization is heavy on using manual processes for development and deployment, and releases are infrequent and monolithic, then your DevOps transformation will necessarily include a lot of steps, and your journey will be longer.  If your organization is currently practicing Agile methodologies and the culture is one that embraces automation and collaboration, then the starting point in your journey is much further down the road, and your transformation will be less complex.

Regardless of where you begin, it's important to internalize the analogy that a DevOps transformation is a journey.  "Adopting DevOps is not a ‘one-and-done' project.  It is adopting a mindset, a culture," says Sanjeev, "It is a commitment to a journey of continuous improvement by adopting a set of capabilities and practices that are based on Lean principles."  That journey consists of a number of steps, or smaller transformations that each will serve to improve the flow of value through your develop/test/deploy process, and bring benefits to the business at each successive stage.

But what are those steps an organization must undertake in order to adopt DevOps?  That is a complex question, and there can be many ‘right' answers for different organizations, as long as those answers are grounded in the proper fundamentals.  The answer that Sanjeev and IBM advocate for is that a transformation consists of six steps - "a set of six capabilities to adopt in this DevOps journey:"

  1. Continuous Business Planning
  2. Collaborative Development
  3. Continuous Testing
  4. Continuous Release and Deploy
  5. Continuous Monitoring
  6. Continuous Feedback and Optimization

The next natural question for most organizations, then, is about where to start?  For this, the analogy of a journey is once again appropriate.  According to Sanjeev, "This requires knowing ‘Point B' where you want to go - what business goals do you want DevOps to help you achieve?  And it requires knowing the ‘Point A' of your journey - where you are today - and how mature you are when it comes to practicing these capabilities today."  Two points make a line, and when you know where your points A and B are, you have the ability to chart out a path towards adoption.

To drive this home, I'd like to point out that this analogy of a DevOps journey is actually much more than just an analogy.  As an officer in the U.S. Army, I served as a battalion planner during a deployment to Iraq in 2007.  In this capacity I created plans ranging across the full spectrum of military operations, from planning actual journeys that involved moving hundreds of Soldiers and thousands of pieces of equipment over hundreds of miles, to planning both lethal and non-lethal operations against Al Qaeda in Iraq.

One of the tasks that I received during that year was to map out my battalion's campaign plan - essentially the transformation strategy that would cover our entire 15-month deployment, and consisted of achieving the singular task of unseating Al Qaeda from the stronghold they had built up in Baqubah as a way to prevent their ability to influence events in the capital city of Baghdad, located about 60 miles to the southwest.  If it makes you feel any better, I started out, much like you, wondering where the hell to begin in devising such a transformation strategy.  But the answer was no different than for any other operation that I had planned - it's a fundamental concept the Army calls ‘backwards planning,' which is almost exactly what Sanjeev is advocating for in determining both your end point and starting point.

In backwards planning, you first start with the destination - what is to be achieved in this operation?  To describe these goals, you first paint a vision of what that desired endstate looks like.  How will we be organized at this endstate; where will we be relative to the enemy; what does our composition and strength look like; what is our posture regarding expectations of next events?  Painting this picture of the desired endstate helps you to articulate the goals, and those tasks which are absolutely necessary to accomplish in order to achieve that endstate.  Then you work backwards in time and space.  If these three tasks must be accomplished in order to achieve the desired endstate, then what must we do in order to successfully complete those tasks?  And so on and so forth, until you arrive at the point you're at today.  By first focusing on the destination, you end up creating a realistic, tangible, and executable plan that gets you from point A to point B.

And that's what Sanjeev and IBM advocate for their clients embarking on a DevOps journey:

"At IBM, we help our customers get started by conducting a ‘DevOps pipeline Value Steam Mapping workshop'. This strategic workshop is a 1-day (usually 6 hour) executive workshop designed to enable IBM to understand your business and IT goals (Point B) and to help you identify gaps in your existing DevOps capabilities (Point A) that IBM can help you address. We identify ‘Point A' by mapping out your end-to-end Application Delivery pipeline, and identifying areas of inefficiencies in the pipeline."

If you're headed to IBM InterConnect next week, Sanjeev ends his article by inviting you to attend a condensed version of these workshops during the conference, which are 2-hr. sessions where you'll work with IBM DevOps SMEs to "map out your application delivery pipeline and identify your key ‘bottlenecks' or inefficiencies."  Once you're done with one of those sessions, stop by the Datical booth (# 658) and we'll show you how you can integrate your database deployments into your Continuous Delivery pipeline!

More Stories By Rex Morrow

Rex is the Marketing Director at Datical, a venture-backed software company whose solution, Datical DB, manages and simplifies database schema change management in support of high velocity application releases. Prior to Datical, Rex co-founded Texas Venture Labs, a startup accelerator at the University of Texas, and received his MBA from the McCombs School of Business. Before graduate school, Rex served as a Captain in the U.S. Army, and was awarded two bronze stars during combat deployments in Iraq.

IoT & Smart Cities Stories
The deluge of IoT sensor data collected from connected devices and the powerful AI required to make that data actionable are giving rise to a hybrid ecosystem in which cloud, on-prem and edge processes become interweaved. Attendees will learn how emerging composable infrastructure solutions deliver the adaptive architecture needed to manage this new data reality. Machine learning algorithms can better anticipate data storms and automate resources to support surges, including fully scalable GPU-c...
Machine learning has taken residence at our cities' cores and now we can finally have "smart cities." Cities are a collection of buildings made to provide the structure and safety necessary for people to function, create and survive. Buildings are a pool of ever-changing performance data from large automated systems such as heating and cooling to the people that live and work within them. Through machine learning, buildings can optimize performance, reduce costs, and improve occupant comfort by ...
The explosion of new web/cloud/IoT-based applications and the data they generate are transforming our world right before our eyes. In this rush to adopt these new technologies, organizations are often ignoring fundamental questions concerning who owns the data and failing to ask for permission to conduct invasive surveillance of their customers. Organizations that are not transparent about how their systems gather data telemetry without offering shared data ownership risk product rejection, regu...
René Bostic is the Technical VP of the IBM Cloud Unit in North America. Enjoying her career with IBM during the modern millennial technological era, she is an expert in cloud computing, DevOps and emerging cloud technologies such as Blockchain. Her strengths and core competencies include a proven record of accomplishments in consensus building at all levels to assess, plan, and implement enterprise and cloud computing solutions. René is a member of the Society of Women Engineers (SWE) and a m...
Poor data quality and analytics drive down business value. In fact, Gartner estimated that the average financial impact of poor data quality on organizations is $9.7 million per year. But bad data is much more than a cost center. By eroding trust in information, analytics and the business decisions based on these, it is a serious impediment to digital transformation.
Digital Transformation: Preparing Cloud & IoT Security for the Age of Artificial Intelligence. As automation and artificial intelligence (AI) power solution development and delivery, many businesses need to build backend cloud capabilities. Well-poised organizations, marketing smart devices with AI and BlockChain capabilities prepare to refine compliance and regulatory capabilities in 2018. Volumes of health, financial, technical and privacy data, along with tightening compliance requirements by...
Predicting the future has never been more challenging - not because of the lack of data but because of the flood of ungoverned and risk laden information. Microsoft states that 2.5 exabytes of data are created every day. Expectations and reliance on data are being pushed to the limits, as demands around hybrid options continue to grow.
Digital Transformation and Disruption, Amazon Style - What You Can Learn. Chris Kocher is a co-founder of Grey Heron, a management and strategic marketing consulting firm. He has 25+ years in both strategic and hands-on operating experience helping executives and investors build revenues and shareholder value. He has consulted with over 130 companies on innovating with new business models, product strategies and monetization. Chris has held management positions at HP and Symantec in addition to ...
Enterprises have taken advantage of IoT to achieve important revenue and cost advantages. What is less apparent is how incumbent enterprises operating at scale have, following success with IoT, built analytic, operations management and software development capabilities - ranging from autonomous vehicles to manageable robotics installations. They have embraced these capabilities as if they were Silicon Valley startups.
As IoT continues to increase momentum, so does the associated risk. Secure Device Lifecycle Management (DLM) is ranked as one of the most important technology areas of IoT. Driving this trend is the realization that secure support for IoT devices provides companies the ability to deliver high-quality, reliable, secure offerings faster, create new revenue streams, and reduce support costs, all while building a competitive advantage in their markets. In this session, we will use customer use cases...