Timeline:
- Start of project – June 1st 2009.
- Deployment – Sept 1st 2009.
Actual available time: 3 months – 12 weeks.
Since a week is a easy to manage time frame, the work is divided into specific work items:
|
Item |
Content |
Duration (weeks) |
|
User perspective design |
Information Flow User actions |
1 |
|
Backend logic |
DB design Flow design Information model |
2 |
|
URL logic |
Pages flow relationships |
0.5 |
|
Infrastructure coding |
DB coding DB interface coding |
1 |
|
Main page coding |
Menus Links |
2 |
|
Table presentation coding |
Presentation table Editing table |
2 |
|
Security |
Logic Cookies Enforcement |
2 |
|
Testing |
Developer testing End user testing |
4 |
|
Total |
|
14.5 |
Due to the limited timeframe, only a subset of the application can be developed, forcing stepped development. For stepped development, grouping functionality allows concentrating on specific features without having to skimp all over the place.
As first step of the project, only three features need to be developed:
- database
- Menus and URLs
- main table display
Having these 3 features allow internal deployment, using a local computer and the parents reading the information from a monitor.
So the plan now is:
|
Item |
Content |
Duration |
|
Design |
Data model Urls Site flow |
2 weeks |
|
Database |
Table creation SQL queries creation |
1 week |
|
Main Page |
Header Footer Menus Links (static) |
2 weeks |
|
Main table |
Calendar Main entry table Main display table |
2 weeks |
|
Testing |
With sample or real data |
2 weeks |
|
Total |
|
9 weeks |
Having 14 weeks, this is doable, even with some delays added.
Now comes the hard part, actually making it.
If you read this far, you should follow me on twitter here.
Related posts:
No tags for this post.
Comments on this entry are closed.