Capabilities First

urn:js:virtue:aspire:principle:34.1

TL;DR

All squads working on building ASPIRE MUST make use of our capabilities to deliver their solutions, or else they must present to Decision Forum why not.

Rational

• Return on investment; we spend a lot of engineering budget on designing and developing our capabilities, we would like to see a return on that investment.
• Developing a great engineering culture; by adopting one another’s capabilities, we help to promote:
  • Continuous learning and development for one another
  • Shared code ownership
  • Respect for one another
  • Focus on high quality code
  • Developing towards the right software abstractions that really work for us
  • A functional maturity for ASPIRE that is greater than the sum of it’s parts

    Implications

    None.

    Appendix

    This principle will remain active for a period of 12 months when it will be reviewed again for it’s suitability.

Migrated From Confluence

link Original Author : Pine, Ben