--- robots: nofollow, noindex --- # Development Process ## Objectives and Key Results (ORKs) Quarterly, we plan using OKRs - Use OKRs to set our goals and measureable results `todo link`. - Identify a high level breakdown of the work tied up to our OKRs that we would like to get done for the quarter `todo link`. ## Project cycle Monthly, we execute on a project cycle. - In the week preceeding the cycle we identify work to be done in the next cycle GitHub Issues (Projects or Bugs) are added to the Milestone corresponding to the cycle (example: [November Project Cycle]( https://github.com/microsoft/fluentui/milestone/19)). - We update project issues with project propsoals for the work (example: `todo link`). - A project cycle by weeks - **Week 1:** Propsoals are reviewed and work starts - **Weeks 2,3+:** Work proceeds according to proposal - **Last week:** - Work wraps up - Work for next cycle identified - Propsoals for next cycle are written - Each week the whole team syncs on progess ## What is a project proposal? Properties of well shaped projects: From: [Principles of Shaping](https://basecamp.com/shapeup/1.1-chapter-02#property-1-its-rough) 1. Rough - Unfinished, not too much detail - Room for real contributions from others 3. Solved - Despite unfinished, it is thought through - All the pieces at the macro level are there and fit together - Clear direction showing the approach - Obvious holes and risks have been removed - Call out how we expect to resolve anticipated problems 5. Bounded - Also indicates what *not* to do - There is a specific amount of time to spend on the project - Scope has been limited to fit the appetite for investment ### Project template - [Create a new Proposal](https://github.com/microsoft/fluentui/issues/new?body=%23%20Project%20Proposal%0A%0A%23%23%20Problem%0A%23%23%20Appetite%0A%23%23%20Solution%0A%23%23%20Risks%20%28Rabbit%20holes%29%0A%23%23%20Out%20of%20scope%20%28No-gos%29&labels=Type:%20Feature) - Don't forget to pick a Milestone!