Cybertrax 2.1 Client (project plan)
From UG
(Difference between revisions)
(→Intro) |
|||
| Line 1: | Line 1: | ||
[[Category:Cybertrax 2.1 Client]] | [[Category:Cybertrax 2.1 Client]] | ||
| + | |||
== Intro == | == Intro == | ||
This project is very important therefore planning is critical. | This project is very important therefore planning is critical. | ||
| + | |||
| + | '''Time vs Features vs Quality:''' | ||
| + | * Focus of this project is to deploy minimal set of core features ASAP. As a result feature set will be reduced to minimum and quality might be average (but must not fall below reasonable level) | ||
| + | |||
| + | Summary of time allocated: | ||
| + | * only 1 week for design | ||
| + | * only 3 weeks for coding | ||
| + | |||
| + | == Weekly Plan == | ||
| + | [[File:2010 summer calendar.JPG]] | ||
| + | |||
| + | === week 1: June 7 Mon - June 11 Fri === | ||
| + | * meetings with clients | ||
| + | * preliminary design sessions | ||
| + | |||
| + | :* requirements: 50% done | ||
| + | :* design: 30% done | ||
| + | :* documentation: 10% done | ||
| + | :* coding: 0% done | ||
| + | :* QA: 0% done | ||
| + | |||
| + | === week 2: June 14 Mon - June 18 Fri === | ||
| + | * analyze requirements | ||
| + | * invent design | ||
| + | * write detailed documentation | ||
| + | |||
| + | * '''Wed 2pm:''' send draft to Simon, Marc | ||
| + | * '''Fri 4pm:''' send ver 1.0 to Bill | ||
| + | |||
| + | :* requirements: 80% done | ||
| + | :* design: 70% done | ||
| + | :* documentation: 60% done | ||
| + | :* coding: 5% done | ||
| + | :* QA: 0% done | ||
| + | |||
| + | === week 3: June 21 Mon - June 25 Fri === | ||
| + | * finalize requirements | ||
| + | * finalize design | ||
| + | * improve documentation | ||
| + | * define tasks for every developer | ||
| + | * start coding and QA | ||
| + | |||
| + | * '''Tue 10pm:''' Kiev/NY status update | ||
| + | * '''Thur 10pm:''' Kiev/NY status update | ||
| + | |||
| + | :* requirements: 95% done | ||
| + | :* design: 90% done | ||
| + | :* documentation: 80% done | ||
| + | :* coding: 30% done | ||
| + | :* QA: 20% done | ||
| + | |||
| + | === week 4: June 28 Mon - July 2 Fri === | ||
| + | |||
| + | * continue coding and QA | ||
| + | * start UC testing | ||
| + | |||
| + | * '''Tue 10pm:''' Kiev/NY status update | ||
| + | * '''Thur 10pm:''' Kiev/NY status update | ||
| + | |||
| + | :* requirements: 99% done | ||
| + | :* design: 99% done | ||
| + | :* documentation: 90% done | ||
| + | :* coding: 60% done | ||
| + | :* QA: 50% done | ||
| + | |||
| + | === week 5: July 5 Mon - July 9 Fri === | ||
| + | |||
| + | * complete coding and QA | ||
| + | * complete UC testing | ||
| + | * Create User Guide, Rollout Schedule, Training Plan, Support plan | ||
| + | |||
| + | * '''Tue 10pm:''' Kiev/NY status update | ||
| + | * '''Thur 10pm:''' Kiev/NY status update | ||
| + | |||
| + | :* documentation: 99% done | ||
| + | :* coding: 99% done | ||
| + | :* QA: 99% done | ||
| + | |||
| + | === week 6: July 12 Mon - July 16 Fri === | ||
| + | |||
| + | * QA on staging | ||
| + | * Release | ||
| + | |||
| + | * '''Mon 9am:''' release to Staging | ||
| + | * '''Tue 10pm:''' Kiev/NY status update | ||
| + | * '''Thur 10pm:''' Kiev/NY status update | ||
| + | * '''Thur 7-8pm:''' release to Production | ||
| + | |||
| + | === week 7: July 19 Mon - July 23 Fri === | ||
| + | |||
| + | * First week of release | ||
| + | |||
| + | * '''Tue 10pm:''' Kiev/NY status update | ||
| + | * '''Thur 10pm:''' Kiev/NY status update | ||
== Weekly Plan == | == Weekly Plan == | ||
Revision as of 02:50, 20 June 2010
Contents |
Intro
This project is very important therefore planning is critical.
Time vs Features vs Quality:
- Focus of this project is to deploy minimal set of core features ASAP. As a result feature set will be reduced to minimum and quality might be average (but must not fall below reasonable level)
Summary of time allocated:
- only 1 week for design
- only 3 weeks for coding
Weekly Plan
week 1: June 7 Mon - June 11 Fri
- meetings with clients
- preliminary design sessions
- requirements: 50% done
- design: 30% done
- documentation: 10% done
- coding: 0% done
- QA: 0% done
week 2: June 14 Mon - June 18 Fri
- analyze requirements
- invent design
- write detailed documentation
- Wed 2pm: send draft to Simon, Marc
- Fri 4pm: send ver 1.0 to Bill
- requirements: 80% done
- design: 70% done
- documentation: 60% done
- coding: 5% done
- QA: 0% done
week 3: June 21 Mon - June 25 Fri
- finalize requirements
- finalize design
- improve documentation
- define tasks for every developer
- start coding and QA
- Tue 10pm: Kiev/NY status update
- Thur 10pm: Kiev/NY status update
- requirements: 95% done
- design: 90% done
- documentation: 80% done
- coding: 30% done
- QA: 20% done
week 4: June 28 Mon - July 2 Fri
- continue coding and QA
- start UC testing
- Tue 10pm: Kiev/NY status update
- Thur 10pm: Kiev/NY status update
- requirements: 99% done
- design: 99% done
- documentation: 90% done
- coding: 60% done
- QA: 50% done
week 5: July 5 Mon - July 9 Fri
- complete coding and QA
- complete UC testing
- Create User Guide, Rollout Schedule, Training Plan, Support plan
- Tue 10pm: Kiev/NY status update
- Thur 10pm: Kiev/NY status update
- documentation: 99% done
- coding: 99% done
- QA: 99% done
week 6: July 12 Mon - July 16 Fri
- QA on staging
- Release
- Mon 9am: release to Staging
- Tue 10pm: Kiev/NY status update
- Thur 10pm: Kiev/NY status update
- Thur 7-8pm: release to Production
week 7: July 19 Mon - July 23 Fri
- First week of release
- Tue 10pm: Kiev/NY status update
- Thur 10pm: Kiev/NY status update
Weekly Plan
week 1: June 7 Mon - June 11 Fri
- meetings with clients
- preliminary design sessions
- requirements: 50% done
- design: 30% done
- documentation: 10% done
- coding: 0% done
- QA: 0% done
week 2: June 14 Mon - June 18 Fri
- analyze requirements
- invent design
- write detailed documentation
- Wed 2pm: send draft to Simon, Marc
- Fri 4pm: send ver 1.0 to Bill
- requirements: 80% done
- design: 70% done
- documentation: 60% done
- coding: 5% done
- QA: 0% done
week 3: June 21 Mon - June 25 Fri
- finalize requirements
- finalize design
- improve documentation
- define tasks for every developer
- start coding and QA
- Tue 10pm: Kiev/NY status update
- Thur 10pm: Kiev/NY status update
- requirements: 95% done
- design: 90% done
- documentation: 80% done
- coding: 30% done
- QA: 20% done
week 4: June 28 Mon - July 2 Fri
- continue coding and QA
- start UC testing
- Tue 10pm: Kiev/NY status update
- Thur 10pm: Kiev/NY status update
- requirements: 99% done
- design: 99% done
- documentation: 90% done
- coding: 60% done
- QA: 50% done
week 5: July 5 Mon - July 9 Fri
- complete coding and QA
- complete UC testing
- Create User Guide, Rollout Schedule, Training Plan, Support plan
- Tue 10pm: Kiev/NY status update
- Thur 10pm: Kiev/NY status update
- documentation: 99% done
- coding: 99% done
- QA: 99% done
week 6: July 12 Mon - July 16 Fri
- QA on staging
- Release
- Mon 9am: release to Staging
- Tue 10pm: Kiev/NY status update
- Thur 10pm: Kiev/NY status update
- Thur 7-8pm: release to Production
week 7: July 19 Mon - July 23 Fri
- First week of release
- Tue 10pm: Kiev/NY status update
- Thur 10pm: Kiev/NY status update
