"Software engineering governance helps teams make decisions, Sarah Wells said at Goto Copenhagen. She argued it should support value delivery, not hinder it. Poor governance slows progress and can increase costs. A technical strategy with a radar can help teams to make better decisions, and aligning with DORA capabilities can boost their performance. Wells defined software engineering governance as the set of principles, practices, and tools that help teams make consistent, informed, and safe technical decisions:"
"Often, governance didn't include tools; it was more about setting expectations. But tools offer an opportunity to help people do the right thing by making that an easy option. Governance should be about helping teams to deliver value, not telling them off, Wells said. And it should keep the company safe, secure, cost-effective, and moving in a consistent direction. Governance that requires coordination with external teams or waiting for approval can have a big impact on productivity and effectiveness, Wells said."
Software engineering governance comprises principles, practices, and tools that enable consistent, informed, and safe technical decisions. Governance must make the right option easy through tooling and support teams in delivering value rather than policing them. Effective governance preserves security, cost-effectiveness, and organisational alignment while preventing slowed progress and higher costs. Coordination delays or approval bottlenecks reduce productivity and effectiveness. Lack of governance risks security vulnerabilities, slow patching, cloud resource sprawl, and duplicated engineering efforts. A clear technical strategy with a technology radar helps teams make better decisions, and alignment with DORA capabilities improves delivery performance.
Read at InfoQ
Unable to calculate read time
Collection
[
|
...
]