Conducting a DevOps Assessment: From Project Overview to Value‑Stream Mapping

1. Defining the Problem The author stresses that, like any investigation, a DevOps assessment must start with a thorough understanding of the specific organization, team and project before proposing improvements, echoing the principle that “no investigation, no right to speak.”

2. Understanding Project and Team Context The assessment begins by gathering high‑level information about the business (who uses the product), the software shape (backend services, mobile apps, embedded devices), scale (code size, team size, user base, deployment footprint) and quality requirements. It also examines management practices such as terminology for requirements, hierarchy of work items, development methodology (Scrum, Kanban), and release frequency.

3. Mapping the Value Stream Using a lean value‑stream approach, the author walks through the six stages of software delivery: code change accumulation, code commit, feature accumulation, feature commit, integration, and release. Each stage is described with its typical activities (static analysis, unit testing, CI pipelines, branch strategies) and the importance of shifting quality checks left.

4. Investigating Branch Strategies The assessment looks at the overall branching model (GitFlow vs. AoneFlow), the branch that represents the latest production version, integration/release branches, and optional feature branches, asking concrete questions about naming, origin, merge targets and quality gates.

5. Detailing Specific Activities Activities are grouped into non‑testing (source control, build, artifact management), deployment (environment provisioning, runtime support), static testing (code review, automated scans) and dynamic testing (unit, integration, performance, production testing). The author notes that a comprehensive book, Software Delivery Fundamentals , covers these topics in depth.

6. Promotional Note The article mentions the published book and provides a link for purchase, as well as an upcoming offline workshop titled “Utopia Plan” for large‑scale agile collaboration.