Difference between revisions of "Using FogBugz"

From Dryad wiki
Jump to: navigation, search
(Priorities)
Line 2: Line 2:
 
# managing incoming questions from Dryad's customers (authors, editors, data consumers, etc.)
 
# managing incoming questions from Dryad's customers (authors, editors, data consumers, etc.)
 
# managing schedules for major development work
 
# managing schedules for major development work
 +
 +
'''NOTE:''' High-level prioritization is captured on the [https://trello.com/datadryad Dryad Trello boards], primarily the Dryad Development board. FogBugz is periodically updated to reflect the prioritization in Trello.
  
 
== Priorities ==
 
== Priorities ==

Revision as of 07:04, 27 April 2012

Dryad uses FogBugz for internal task tracking. FogBugz serves two major purposes:

  1. managing incoming questions from Dryad's customers (authors, editors, data consumers, etc.)
  2. managing schedules for major development work

NOTE: High-level prioritization is captured on the Dryad Trello boards, primarily the Dryad Development board. FogBugz is periodically updated to reflect the prioritization in Trello.

Priorities

Dryad assigns the following meanings to priorities:

  • 1 - Do it now, damnit: A critical problem that needs to be fixed within the next day or two (use sparingly)
  • 2 - Very high: This item absolutely must be addressed before the milestone can be considered "complete", and it should be done in the next 2 weeks.
  • 3 - High: This item absolutely must be addressed before the milestone can be considered "complete". It should be done within the next month.
  • 4 - Medium: This item must be addressed for the milestone to be considered complete.
  • 5 - Low: This item should be done if opportunity allows, but it is not needed for milestone completion.
  • 6 - Not prioritized: A priority has not yet been assigned to this case. It should be prioritized as soon as possible.

Milestones, Tasks, and Sub-tasks

Dryad organized FogBugz content according to the following rules:

  1. A milestone is created whenever we wish to track the time at which a specific activity (or set of activities) will be completed. It is best if milestones are strictly sequential. FogBugz does not work well for concurrent milestones -- it is too easy to forget to work on one of them.
  2. Some milestones are designated as "releases".
    1. A release may be based on a single feature, but it is typically focused on the set of features needed for a particular deadline.
    2. If the space between two major deadlines is too great, a release may be scheduled between the deadlines to ensure that progress stays on track.
  3. A task is a feature, bugfix, or activity that is required to meet a given milestone.
    1. A task may be broken down into subtasks, and the subtasks may be assigned to different people.
    2. If a task will take more than 2 days to complete, it should be broken down into subtasks.

Special milestones:

  • Undecided is the default milestone that FogBugz uses when a new task is created. Anything in this milestone needs to be sorted into a different milestone.
  • Someday is a catch-all milestone. It stores items that need to be done, but do not have high enough priority to be on the current schedule.

User Accounts

Many Dryad staff members have individual accounts in FogBugz, so they may perform the activities listed above. There are "virtual" accounts for some staff and external contractors, which are used to organize task lists (but not for direct time tracking).

There are two special-purpose accounts:

  • Dryad Personnel is a virtual account that only sends notifications to Ryan. This is to help us keep track of tasks being performed by people who do not use Fogbugz directly.
  • Dryad Helpdesk is a virtual account that receives the cases from help@datadryad.org. It sends notifications to Ryan, Elena, and Kevin. Tasks in this account need to be resolved quickly or assigned to another user.