<aside> 🚨

Work In Progress: Suggest any changes or ideas, you are welcome to participate.

Also some things may look messy, so please forgive that for now. Though feel free to point at it and complain 😭

</aside>

Objective

The purpose of this policy is to establish a clear, open, collaborative, and structured approach for developing Status features. By engaging key stakeholders from the outset and ensuring consistent involvement throughout the feature’s lifecycle, this policy aims to improve quality, reduce rework, and align deliverables with business goals.

graph TD
    A[📜 Requirements Document - User Stories]
    subgraph DD [📃 Derivative Documents]
        B(✅ Acceptance Requirements)
        C(⚙️ Technical Specification)
        D(🎨 Designs)
    end
    
    A --> DD
    
    %%C <--> D
    %%B <--> C
    %%B <--> D
    
    
    E[[💻 Implementation and Testing]]
    F[[🧪 QA and Design Review]]
    G[[🚀 Release]]
    
    DD --> E
    DD --> F
    
    E --> F
    F --> G

Scope

This policy applies to all feature development projects within the Status organisation and covers the entire lifecycle of a feature, from ideation to maintenance.

🔑 Key Principles

📃 Requirements-Driven Development

Every feature begins with clearly defined requirements. These requirements serve as the foundation for all subsequent documentation, design, development, and testing activities.

Requirements Document with User Stories

The Requirements Document serves as the foundation for each feature’s development. In the context of this process, user stories act as the primary way to define the requirements and communicate them across teams. By focusing on the actual needs of users, user stories provide a simple, iterative, and adaptable method of specifying and evolving requirements throughout the feature's lifecycle.

What is a Requirements Document?

In this process, the Requirements Document is composed of a set of user stories, which describe the desired outcomes from the user's perspective.

See ‣

This document also includes acceptance criteria and other supporting documentation such as designs and technical specifications to ensure clarity for the development, design, and QA teams.

Traceability to User Stories

• Every acceptance requirement, technical specification, and design should be traceable back to its corresponding user story. This ensures that the feature being built aligns with the original intention and delivers the desired value to the end user.

🦸🦹🧛 The Three Amigos

A Three Amigos group is composed of a developer, QA specialist, and designer, responsible for a specific feature or set of features.