Requirements prioritization and project scope: Difference between revisions
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
==Feature Priorities== | ==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 [[Features|present long-range set of features]]. | |||
#Address Book | |||
#Message Filters | |||
#Account Type | #Account Type | ||
#Message Composition | #Message Composition | ||
#Offline Mode | #Offline Mode | ||
Revision as of 15:50, 2 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.
- 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
Time Frame
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.