Value Matrix

This section will explain how Standard intends to create value for different stakeholders. It is essential to have an idea of who they are, so let's introduce:

The Software Sponsor Makes resources available in return for the expectation of future benefits.

The Provider of Automation Sets up and maintains the automation along the SDLC. A helpful analogy would be the person who sets up and maintains the conveyor belt which moves features to production.

The Consumer of Automation Consumes and co-maintaines the automation along the SDLC. A helpful analogy would be that this person not only uses and configures our conveyor belt, but is also capable of occasionally maintaining it.

It is essential to have an understanding of what they value, so let's try to get an overview. We'll make use of a high level value matrix with simple sentiment scores:

  • 😍 → "absolutely love it!!!"
  • 😄 → "feels pretty good."
  • 😐 → "whatever?!?"
Software Sponsor [Principal]Provider of SDLC Automation [Agent]Consumer of SDLC Automation [Agent]
Code Organization😄😍😄
Mental Model & Learning😄😍😄
Batteries Included😐😍😐
Community and Ecosystem😐😍😄
Reproducibility & Software Supply Chain Security😍😍😐
Modularity & Incremental Adoption😄😄😍
Developer Experience & Onboarding Story😄😄😍

So, this is for you and your team, if you:

  • Care about reproducibility for more reliablility throughout your software development
  • Value clean code for keeping a check on techincal debt and increased long-term maintainability
  • Have a deadline to meet with the help of the includes best practices and batteries
  • Want to serve an optimized UX to your colleagues via a repo CLI / TUI and (close to) zero-config CI

Selling Points

The main selling points of Standard are:

  • Efficiency: Standard automates the software delivery lifecycle, making the process more efficient and streamlined.

  • Reproducibility: Standard's emphasis on reproducibility ensures that every stage of the SDLC can be easily replicated, leading to a more consistent and reliable software development process.

  • Speed: Standard optimizes the critical path of the SDLC journey to achieve superior cycle times, which means that your software can be shipped to production faster.

  • Flexibility: Standard is built to be flexible and adaptable, which allows it to be used in a variety of different contexts and industries.

  • Cost-effective: Automating the software delivery lifecycle with Standard saves time and resources, making it more cost-effective.

  • Integration: Standard is a horizontal integration framework that integrates vertical tooling, making it easier to stitch together different tools and processes to create a polished whole.

  • Community Outreach: Standard is a part of the Nix ecosystem and is committed to community outreach to ensure that its optimization targets are met and that other perspectives are not dismissed.

These points show how Standard can help adopters to improve their software delivery process, and how it can save them time, money and improve the quality of their software.