Adding DevOps practices to a single development team is a relatively simple proposition as it usually comes down to introducing either people to the team to build up a DevOps, Release Engineering or Platform Engineering capability within an organisation.
Some of the pitfalls organisations are trying to avoid are:
- Inability to report progress consistently across multiple development teams, for example, if one team reports their progress in terms of the number of equally sized stories completed in 2 weeks; whereas another team reports in storypoints completed in a three-week sprint.
- Inconsistent application of a practice means team members can not easily move between teams within the same organisation without learning new ways of working.
- Mismatches in development cadence across multiple teams makes coordinating dependent releases difficult.
What can be employed to achieve this in a consistent manner in an organisation that has a large number of development teams, potentially in multiple separate business units?