docs: transacting a round of deep feedback

blaggacao · blaggacao · commit 0baf33ad8e22 · 2023-02-02T21:44:52.000-05:00
diff --git a/ARCHITECTURE.md b/ARCHITECTURE.md
diff --git a/PITCH.md b/PITCH.md
@@ -0,0 +1,60 @@
+# 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 alongside 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 alongside the SDLC.
+A helpful analogy would be that this person not only uses and configures our conveyor belt, but is also capable of maintaining it.
+
+It is equally essential to have an understanding 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:
+
+- :heart_eyes: &rarr; <i>"absolutely love it!!!"</i>
+- :smile: &rarr; <i>"feels pretty good."</i>
+- :neutral_face: &rarr; <i>"whatever?!?"</i>
+
+|                                                  | Software Sponsor [Principal] | Provider of SDLC Automation [Agent] | Consumer of SDLC Automation [Agent] |
+| ------------------------------------------------ | :--------------------------: | :---------------------------------: | :---------------------------------: |
+| Productivity                                     |         :heart_eyes:         |            :heart_eyes:             |              :smiley:               |
+| Code Organization                                |           :smiley:           |            :heart_eyes:             |              :smiley:               |
+| Mental Model & Learning                          |           :smiley:           |            :heart_eyes:             |              :smiley:               |
+| Batteries Included                               |        :neutral_face:        |            :heart_eyes:             |           :neutral_face:            |
+| Community and Ecosystem                          |        :neutral_face:        |            :heart_eyes:             |              :smiley:               |
+| Reproducibility & Software Supply Chain Security |         :heart_eyes:         |            :heart_eyes:             |           :neutral_face:            |
+| Modularity & Incremental Adoption                |           :smiley:           |              :smiley:               |            :heart_eyes:             |
+| Developer Experience & Onboarding Story          |           :smiley:           |              :smiley:               |            :heart_eyes:             |
+
+So, this is for you and your team, if you:
+
+- Care about reproducibility
+- Value clean code
+- Have a deadline to meet
+- Want to serve an optimized UX
+
+# 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.
diff --git a/ROADMAP.md b/ROADMAP.md
@@ -7,30 +7,32 @@ This roadmap gives an overview of the short and mid term direction that the proj
 
 ## Deliverable Categories
 
-We've identified a couple of deliverable categories that should help us better understand the work spectrum associated with the project.
-Please also complement this with the high level overview in the [Architecture](./ARCHITECTURE.md).
+We've identified a couple of deliverable categories in line with the [architectural overview](./ARCHITECTURE.md).
 
-##### Process Categories alongside the (automatable sections of the) SDLC
+These help us to better understand the work spectrum associated with the project.
 
-- Setup Processes
-- The actual automatable parts of the SDLC Cycle
+##### Process Categories
 
-While an instance of the actual SDLC process inside the boundaries of Standard's current scope is easy to break down into _eval_, _build_ and _effect/action_ and easy to measure with the _cycle time_ metric,
-the Setup Process is where adoption success or failure may be determined alongside:
+To run an _automation_ we have to _set it up_, first.
+We should keep that in mind when working on the backlog and therefore classify:
 
-- Provided Documentation
-- Shared Mental Models
-- Curated Quick Start Template
-- Onboarding & Learning Context
-- Actual Installation and Setup
+- Setup
+- Automation
+
+Work packages that supports setup typically involve:
+
+- Documentation & Setup Instructions
+- Pattern & Shared Mental Models
+- Quick Start Template
+- Onboarding & Learning Content
 
 ##### Process Regions
 
-As discussed in the [Architecture](./ARCHITECTURE.md) document, we roughly identify three regions with shifting characteristics alongside the SDLC:
+Per our [architectural overview](./ARCHITECTURE.md), we distinguishe these process regions:
 
-- Development Environment Region
-- Build Pipeline Region (including CI control loops)
-- Continuous Delivery and Beyond (Application Lifecycle Management)
+- Development Environment
+- Build Pipeline
+- Deployment and Beyond (Application Lifecycle Management)
 
 ##### Deliverable Types
 
@@ -45,6 +47,6 @@ As discussed in the [Architecture](./ARCHITECTURE.md) document, we roughly ident
 ## Milestone v1
 
 With the above in mind, the [issue backlog](https://github.com/divnix/std/issues) will be regularly groomed and prioritized.
-This is an aid for the core contributors, but it may also provide the necessary orientation and stability to convince interested new contributors.
+This is an aid for the core contributors, but it may also provide the necessary orientation to get new contributors set up.
 
 Welcome!
diff --git a/artwork/components.svg b/artwork/components.svg
diff --git a/docs/PITCH.md b/docs/PITCH.md
@@ -0,0 +1 @@
+../PITCH.md
diff --git a/docs/SUMMARY.md b/docs/SUMMARY.md
@@ -2,6 +2,7 @@
 
 [Introduction](README.md)
 [Design & Architecture](./ARCHITECTURE.md)
+[Sales Pitch](./PITCH.md)
 [Roadmap](./ROADMAP.md)
 
 # Tutorials
