Project planning: Difference between revisions

From Thunderforce
Jump to navigation Jump to search
m (Protected "Project planning" [edit=sysop:move=sysop])
 
(16 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Obsolete}}
==Schedule==
==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 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.
The following table depicts the current schedule for Thunderforce. Weeks begin on Mondays in this schedule. 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.


Please note that, as with any open-source software project, this schedule does not constitute any promise of delivery or adherence.
Please note that, as with any open-source software project, this schedule does not constitute any promise of delivery or adherence.


{| border="1"
{| border="1" width="100%"
! Week 18
! Week 18
! Week 19
! Week 19
Line 18: Line 20:
|width="12.5%" valign="top"|
|width="12.5%" valign="top"|
*Project plan and scope
*Project plan and scope
|width="12.5%" valign="top"|
*Context diagram
*Use cases
|width="12.5%" valign="top"|
*Notional architecture
*Notional architecture
|width="12.5%" valign="top"|
*Identification of architectural risks
*Identification of architectural risks
*Experiment planning
*Experiment planning
Line 27: Line 32:
*XUL files tested with Usability Engineering (UE)
*XUL files tested with Usability Engineering (UE)
|width="12.5%" valign="top"|
|width="12.5%" valign="top"|
*XUL files refined
*Experiment execution
|width="12.5%" valign="top"|
|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"|
|width="12.5%" valign="top"|
|}
|}
<br>
<br>
{| border="1"
{| border="1" width="100%"
! Week 26
! Week 26
! Week 27
! Week 27
Line 49: Line 47:
|-
|-
|width="12.5%" valign="top"|
|width="12.5%" valign="top"|
*Initial integration tests using skeleton
*End of sprint 1
|width="12.5%" valign="top"|
|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"|
|width="12.5%" valign="top"|
|width="12.5%" valign="top"|
|width="12.5%" valign="top"|
|width="12.5%" valign="top"|
*End of sprint 2
*Experiment execution
*Demonstration of sprint 2 functionality
|width="12.5%" valign="top"|
*Sprint 3 kick-off
*Developer on-boarding instructions
|width="12.5%" valign="top"|
|width="12.5%" valign="top"|
*Integration tests needed for release pass
*Architectural refinement
|}
<br>
{| border="1" width="100%"
! Week 34
! Week 35
! Week 36
! Week 37
! Week 38
! Week 39
! Week 40
! Week 41
|-
|width="12.5%" valign="top"|
|width="12.5%" valign="top"|
*Module identification
|width="12.5%" valign="top"|
*M1 release XUL extensions
*System code skeleton created
*Initial integration tests for M1 release
|width="12.5%" valign="top"|
|width="12.5%" valign="top"|
|width="12.5%" valign="top"|
*[http://www.salesforce.com/dreamforce/ Dreamforce]
|width="12.5%" valign="top"|
|width="12.5%" valign="top"|
|width="12.5%" valign="top"|
*Module code for M1 complete
*Integration tests needed for M1 release pass
*Packaging
*Packaging
*First pre-alpha release
*M1 release
*End of sprint 3
|}
*Demonstration of sprint 3 functionality
<br>
{| border="1" width="100%"
! Week 42
! Week 43
! Week 44
! Week 45
! Week 46
! Week 47
! Week 48
! Week 49
|-
|width="12.5%" valign="top"|
|width="12.5%" valign="top"|
|width="12.5%" valign="top"|
*Integration tests needed for version M2 release
|width="12.5%" valign="top"|
|width="12.5%" valign="top"|
|width="12.5%" valign="top"|
|width="12.5%" valign="top"|
|width="12.5%" valign="top"|
*Module code for M2
*Integration tests needed for the M2 release pass
*Packaging
*M2 release
|}
|}
==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

Latest revision as of 21:39, 22 November 2008

Note: This page is obsolete. Please go to the home page.

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. Weeks begin on Mondays in this schedule. 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.

Please note that, as with any open-source software project, this schedule does not constitute any promise of delivery or adherence.

Week 18 Week 19 Week 20 Week 21 Week 22 Week 23 Week 24 Week 25
  • Project plan and scope
  • Context diagram
  • Use cases
  • Notional architecture
  • Identification of architectural risks
  • Experiment planning
  • Initial XML user interface language (XUL) files created
  • XUL files tested with Usability Engineering (UE)


Week 26 Week 27 Week 28 Week 29 Week 30 Week 31 Week 32 Week 33
  • Experiment execution
  • Developer on-boarding instructions
  • Architectural refinement


Week 34 Week 35 Week 36 Week 37 Week 38 Week 39 Week 40 Week 41
  • Module identification
  • M1 release XUL extensions
  • System code skeleton created
  • Initial integration tests for M1 release
  • Module code for M1 complete
  • Integration tests needed for M1 release pass
  • Packaging
  • M1 release


Week 42 Week 43 Week 44 Week 45 Week 46 Week 47 Week 48 Week 49
  • Integration tests needed for version M2 release
  • Module code for M2
  • Integration tests needed for the M2 release pass
  • Packaging
  • M2 release