Requirements prioritization and project scope
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.
- Address Book
- Message Filters
- Account Type
- Message Composition
- Offline Mode
Task Priorities
- Notional architecture of the entire extension
- Identification of architectural risks
- Design and execution of experiments to reduce architectural risks
- Architectural refinement and modularization of the extension
- Parallel work on the modules, focusing on those that address the account type feature
- 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.
Week 18 | Week 19 | Week 20 | Week 21 | Week 22 | Week 23 | Week 24 | Week 25 |
---|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
Week 26 | Week 27 | Week 28 | Week 29 | Week 30 | Week 31 | Week 32 | Week 33 |
---|---|---|---|---|---|---|---|
|
|
|
|
|
Sprints
The following lists the focus of each sprint:
- Initial integration test creation and development of base functionality
- Feature development and integration test refinement
- Integration test validation and extension packaging