Features/Planning and Tracking: Difference between revisions

; Why do we need to do this?

: We always have more things that we want to do than people and time we have to do them.  This system is a simple way for us to have a shared understanding of our priorities, where people are spending their time, how things are going, and what the various tradeoffs are if/when we have to make hard decisions about what to work on (and therefore what not to).  

; But what about this bugfix I'm working on?

: Single bugfixes do not need to have Feature pages or be tracked via the Flight Trackers.  The current working rule-of-thumb is that if something is significant enough that we would mention it in the release notes, it should probably have a Feature Page and be tracked using this system.

; The Features List is missing something important!

: Great - [[#If_your_Feature_is_not_on_the_Feature_List|let us know]]. The product team owns the list and the prioritization, but we do not expect to be the source of every idea, we expect to be the clearinghouse bringing them all together and aligning them against our long term plans.

; I am excited to start working on a feature, how do I start?

: Ping the listed owner for that feature and let them know. The first step is to identify the team involved (Project Manager, Developer(s), QA lead, contacts from security, usability and elsewhere as appropriate), get it into the tracker with an appropriate estimate, and then start hacking.