...
This document will use the term Sponsor User, or Sponsors, to refer to an individual or organization that has a vested interest in the user outcomes of the proposed Feature Candidate. The author of the submission may also be the Sponsor User.
Processes and Tools
Any proposed Feature should be described and communicated according to Design Thinking keys and processes. Feature deliverables will be stored and managed using GitHub and ZenHub tools according to a flexible/pragmatic Agile/Kanban methodology. And the Feature’s user outcomes will be decomposed into technical requirements that can be developed, merged, and activated as sub-features by feature flags as they are completed.
Overview
The Feature Request process is divided into four distinct stages, collectively comprising the Feature Request Lifecycle:
- Feature Candidate – This is the stage where an idea for one or more user outcomes is defined as a Feature, described and presented, and accepted or rejected.
- Feature Design – This is the stage where the Feature is built. The technical requirements will be decomposed into discrete tasks/issues, development will ensue, then testing and deployment.
- Feature Support – This stage covers the time when the functionality is available to the public and OH will work to fix any identified bugs.
- Feature Archive – This stage is the final resting place for obsolete, superseded, or deprecated Features that may be of historical significance but are no longer under development or supported.