Chandler 0.6 App Feature Scoping

Scoping Guidelines

There are several things we need to do on this task list: perform a basic SWAG, add missing tasks and identify the risk areas.

• Basic SWAG: This is composed of 2 data: the Scope and the Confidence level. Please estimate the tasks where you are listed as an owner. If you think someone else is better suited for the SWAG, please change the owner.

  Scope

  Give an idea of the workload associated with the task. Choose one of the following:

  • Trivial (< 1 day)
  • Small (1 day)
  • Medium (1-3 days)
  • Large (4-5 days)
  • Huge (>5 days)

  Confidence

  Give an idea of how confident you are with the Scope estimate. Choose one of the following:

  • High (>80%)
  • Fair (50-80%)
  • Low (20-50%)
  • Nil (<20%)

• Add Missing Tasks: More than likely, they are quite a bit of missing tasks in this list. A rule of thumb is that any task should not be bigger than 5 days of coding (low granularity). Please, break down (and SWAG) tasks that you'd otherwise scope as Huge and add tasks that you know are missing in your work area. Tasks remaining that cannot be broken down in smaller chunks are in need of spec or should be postponed till we know more (may be some dependence on completion of another task). Please add such info in the Comment column.
• List Risk Areas: Risk areas are not necessarily identifiable as tasks (e.g. wxWidgets 2.6 has some unforseen issue, Mac OS X Tiger requires some deep rework, ...). List the ones that you are worried about and give for each of them a probability of the risk to materialize and a potential cost (in dev days or weeks).
• Other: Please, do not hesitate to add Comments. You can also comment and SWAG any task that is not assigned to you but on which you have some pertinent idea. In general, any info that will help plan and schedule the work is welcome (those are guidelines...).

Risk Areas

Please add here risk areas that we should take into account in the plan.

• Detail View issue areas with incomplete scope or design:
• Recurrence: changes to "DV displays an item" model to support display of "virtual" items, if the DV can't treat them as ordinary items.
• Recurrence: changes that create exceptions to recurrence
• Recurrence: reminder state handling
• Recurrence: UI for limiting infinite recurrence
• DV: Collection membership field; UI for deleting? Triggers need for dynamic resizing in DV?
• AE: Reconsidering editability and readonlyness in the DV
• Timezone support: design goals unspecified; bug 2087 is related
• Sharing detail view: show collection detail view on invitation acceptance
• Sharing detail view: additional attribute editors needed; permission management UI might need complicated AEs
• Chandler Platform: detail view / AE documentation for developers unscoped
• Chandler Platform: more useful basic AEs? (several parcel authors have asked for them)
• DV: rework for whatever replaces parcel xml?

Feature Scoping

We are now using Bugzilla to track feature work (marked with the keyword "task") as well as bugs. The SWAG is attached for each record we decide to fix in the Whiteboard Status field.

For more info, please check how we use Bugzilla to track tasks and bugs.