Cybertrax 2.1 Client (project plan)
From UG
(Difference between revisions)
(→Weekly Plan) |
(→Plan) |
||
| Line 63: | Line 63: | ||
==== Plan ==== | ==== Plan ==== | ||
| - | * | + | * requirements - must be 100% completed |
| - | * | + | ** |
| - | * | + | |
| - | * | + | * design - must be 80% completed |
| - | + | ** | |
| + | |||
| + | * coding - tasks for every developer must be assigned, start coding | ||
| + | ** | ||
* '''Tue 10pm:''' Kiev/NY status update | * '''Tue 10pm:''' Kiev/NY status update | ||
* '''Thur 10pm:''' Kiev/NY status update | * '''Thur 10pm:''' Kiev/NY status update | ||
| - | :* requirements: | + | * by the end of the week: |
| - | :* design: | + | :* requirements: 100% done |
| + | :* design: 80% done | ||
:* documentation: 80% done | :* documentation: 80% done | ||
:* coding: 30% done | :* coding: 30% done | ||
Revision as of 03:24, 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 analysis and requirements gathering * only 1 week for design * only 3 weeks for coding, testing, rollout/training planning * only 1 week for staging/release ----------------- Total: 6 weeks
NOTE: This is an estimate. Error is -1 week/+2 weeks.
Important Dates
- 1st date for Release: Thur, July 15
- 2nd date for Release: Thur, July 22
Weekly Plan
week 1: June 7 Mon - June 11 Fri
Plan
- meetings with clients
- preliminary design sessions
- requirements: 50% done
- design: 30% done
- documentation: 10% done
- coding: 0% done
- QA: 0% done
Actual
Completed as planned!
week 2: June 14 Mon - June 18 Fri
Plan
- 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
Actual
Completed as planned!
week 3: June 21 Mon - June 25 Fri
Plan
- requirements - must be 100% completed
- design - must be 80% completed
- coding - tasks for every developer must be assigned, start coding
- Tue 10pm: Kiev/NY status update
- Thur 10pm: Kiev/NY status update
- by the end of the week:
- requirements: 100% done
- design: 80% done
- documentation: 80% done
- coding: 30% done
- QA: 20% done
Actual
TBD
week 4: June 28 Mon - July 2 Fri
Plan
- 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
Actual
TBD
week 5: July 5 Mon - July 9 Fri
Plan
- 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
Actual
TBD
week 6: July 12 Mon - July 16 Fri
Plan
- 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
Actual
TBD
week 7: July 19 Mon - July 23 Fri
Plan
- "2nd release date" in case we could not release previous week
- Mon 9am: release to Staging
- Tue 10pm: Kiev/NY status update
- Thur 10pm: Kiev/NY status update
- Thur 7-8pm: release to Production
Actual
TBD
