Value streams are complex. Few enterprises have simple software development anddelivery value streams. Most are multi-modal, cross-domain and somewhat fragile, meaning a change to a single element can impact other elements, positively or negatively. DevOps transformations require systems thinking, which may be elusive.
Inconsistent adoption of DevOps practices. Some teams learn and adopt faster than others. Without help from a trusted, independent expert, self-managing teams can fall behind and slow the progress of the overall transformation. DevOps success requires
that all teams accelerate their learning and application of best practices.
Effectively balancing demands to change, learn and execute. Transformative initiatives can stall after initial success with first-level best practices. Help from a trusted third party can keep teams focused on continual improvement and experiential learning needed to embrace new mental models, behaviors and activities.
Toolchain expertise. DevOps inevitably involves technologies across IT domains from multiple vendors. Critical areas such as security and automation need special attention. If gaps in technical expertise exist, critical momentum for the team can be lost.
Full value steam agility. Disconnected agile and DevOps adoption typically results in counterproductive work and duplication that can be avoided by taking an integrated approach to these critical initiatives.