Project Process
Our work is organized into projects that move through the following funnel:
Spontaneous Ideas: Everyone on the team is expected to contribute ideas for improving the product. Link your ideas to relevant Roadmap items, the Human Interface Library, and Definitions so they can be easily discovered in the future.
Write Pitches: When an idea becomes essential, its owner should develop it into a well-defined project proposal.
Approve Projects: Projects are approved during Hypertuesdays. Each project should be scoped to last one, two, or at most three weeks.
Deliver Projects: Working software must be demoed on Tuesdays. The expectation is a high-quality, fully functional product. Define scoped projects to build them on time.
Projects
A project should originate from users’ conversations and needs. It’s unlikely that a Pitch will be approved if no users have expressed interest or requested it.
Location on the Product Map: Clearly define where the project fits in the Product Map by mapping it to activities, user tasks, and user stories.
Human Interface Library (HIL): Any related designs must be complete and published in the HIG section.
New Definitions: If the project introduces new concepts or terminology, these must be documented in the Definitions section.
Protocol Changes: If the project affects the Hypermedia Protocol, it must be accompanied by a dedicated document detailing the changes.