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.

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

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
Project plan and scope Notional architecture	Identification of architectural risks Experiment planning			Experiment execution Architectural refinement	Module identification and assignment		Initial integration tests

Week 26	Week 27	Week 28	Week 29	Week 30	Week 31	Week 32	Week 33
Module plans		Module unit tests			Modules developed	Integration tests run	Feature set for release stabilized Feature set for later release disabled Packaging First release