Streamline your processes

Welcome to our checklists. They serve as useful companions during Navigating DevOps through waterfall journeys, help jog our memory, and point us in the right direction.

OBJECTIVECHECK
Embrace technical governance to create a common ground.[ ]
Streamline value creation across the organization to close the gaps between business and technology.[ ]
Streamline change management to remediate at root cause level.[ ]
Limit work in progress to maximize focus and minimize context switching. Refer to Multitasking: Switching costs (American Psychological Association, 2006) for information on the penalty of context switching work and collaboration.[ ]
Foster continuous experimentation to determine value and adapt quickly.[ ]
Automate to promote performance, stability, and consistency.[ ]
Shift testing and security left to raise quality and lower vulnerabilities.[ ]
Shift configuration right and promote a consistent and traceable one build, many delivery models.[ ]
Create a common organizational cadence (iterations, sprints) to support collaboration.[ ]
Maintain a transparent and groomed backlog to enable Lean practices and a pull over push working model.[ ]
Release only production ready code![ ]
Checklist – Streamline your processes when embracing a DevOps mindset

Share this post

Download our free white paper on Technical Debt and Business Agility.

Fill out the form below, and we will send you a white paper along with a drawing for a free drawing for our DevOps book!

Ready to level up your career?

Recent Posts

Add to Waitlist

If a course has an ‘add to waitlist’ button then it is likely booked up. Spots often become available so please fill out the form below. We will be in touch within 24hrs

CIO

Born 1965, San Antonio, Texas and lives in Dallas, Tx.
Mr. James, Ronald, Maverick holds a Bachelor of Science in Psychology at The University of Texas, San Antonio.

Mr. Maverick or JR as many call him is a “slick” but warm and friendly character in our upcoming book on the DevOps Mindset. Mr. Maverick cares about his IT team very much and could charm the socks off a Texas Longhorn. JR is liked by many in his organization; however, he is not as well trusted by the Overlords as he used to be. Mr. Maverick has a group of loyal staff, including Mr. Barker a bit of an opposite to JR. Of course, Mr. Barker would never call him JR; he would only call him Mr. Maverick because well, Mr. Maverick is his boss. Mr. Maverick has held many IT positions in the past, including starting as a Sales Professional for HP and IBM mini and mainframe computers. Over the years he has risen through the ranks to hold this senior position by delivering using high-paid consultants and Big name firms. He also received his promotion from outsourcing to a foreign country where he was able to reduce his IT spend significantly. Recently he has discovered (actually this was made painfully aware to him by the Overlords) that both the Offshore roadmap and use of external consultants was not giving him the value and velocity for his IT department, and he was probably paying more than he bargained for

So, after hearing a talk at a DevOps event by the Agents of Chaos, JR decided to enlist them to help with their digital transformation roadmap and help improve the value, focus and velocity of his department. However, MR. Maverick has a few ideas about agile and DevOps, something he has heard about for a while and read in various CIO magazines; he thinks of these as Marketing terms and something that can be bought. While Mr. Maverick has held on for many years to traditional IT ways of working he has come to the end of his tenure if he doesn’t do something fast and get DevOps working quickly as he has promised to the Overlords providing him with a little more rope to get the transformation completed more quickly as they view his IT department ageing, procrastinators who are not able to keep up with business demands. JR says in his mind, “I will get it done, they don’t call me Maverick for nothing!“