Requirements prioritization and project scope: Difference between revisions

From Thunderforce
Jump to navigation Jump to search
No edit summary
Line 16: Line 16:
#Parallel work on the modules, focusing on those that address the account type feature
#Parallel work on the modules, focusing on those that address the account type feature
#First release
#First release
==Schedule==
The first release of Thunderforce is planned to occur around mid-August of this year. The details of the plan will work backwards from that release date.
The following table depicts the current schedule for Thunderforce. Note that week 18 is the week beginning on April 30, 2007. Items in the table cells indicate when those activities should be completed by, which can be by the end of the week indicated.
{| border="1"
! Week 18
! Week 19
! Week 20
! Week 21
! Week 22
! Week 23
! Week 24
! Week 25
|-
|width="12.5%" valign="top"|
*Project plan and scope
*Notional architecture
|width="12.5%" valign="top"|
*Identification of architectural risks
*Experiment planning
|width="12.5%" valign="top"|
*Initial XML user interface language (XUL) files created
|width="12.5%" valign="top"|
*XUL files tested with Usability Engineering (UE)
|width="12.5%" valign="top"|
*XUL files refined
*Experiment execution
|width="12.5%" valign="top"|
*Architectural refinement
*Module identification and assignment
*System code skeleton created
|width="12.5%" valign="top"|
*Sprint 1 kick-off
|width="12.5%" valign="top"|
|}
<br>
{| border="1"
! Week 26
! Week 27
! Week 28
! Week 29
! Week 30
! Week 31
! Week 32
! Week 33
|-
|width="12.5%" valign="top"|
*Initial integration tests using skeleton
*End of sprint 1
|width="12.5%" valign="top"|
*Demonstration of sprint 1 functionality
*Sprint 2 kick-off
|width="12.5%" valign="top"|
|width="12.5%" valign="top"|
|width="12.5%" valign="top"|
|width="12.5%" valign="top"|
*End of sprint 2
*Demonstration of sprint 2 functionality
*Sprint 3 kick-off
|width="12.5%" valign="top"|
*Integration tests needed for release pass
|width="12.5%" valign="top"|
*Packaging
*First pre-alpha release
*End of sprint 3
*Demonstration of sprint 3 functionality
|}
==Sprints==
The following lists the focus of each sprint:
#Initial integration test creation and development of base functionality
#Feature development and integration test refinement
#Release finalization and packaging

Revision as of 07:03, 3 May 2007

The requirements fed into the feature list, and the prioritization of those features will appear on this page.

Feature Priorities

Note that some features have dependencies upon each other. This is a general list, and the actual module priorities will likely include functionality from all modules as the top priorities. The initial focus will be on associating both incoming and outgoing email messages with Salesforce.com records, but the architecture will factor in the present long-range set of features.

  1. Address Book
  2. Message Filters
  3. Account Type
  4. Message Composition
  5. Offline Mode

Task Priorities

  1. Notional architecture of the entire extension
  2. Identification of architectural risks
  3. Design and execution of experiments to reduce architectural risks
  4. Architectural refinement and modularization of the extension
  5. Parallel work on the modules, focusing on those that address the account type feature
  6. First release
Retrieved from "https://www.moonlightdesign.org/thunderforce/wiki/index.php?title=Requirements_prioritization_and_project_scope&oldid=122"