Cybertrax 2.1 Client (project plan)
From UG
(Difference between revisions)
(→Requirements Team) |
(→Project team and responsibilities) |
||
| Line 74: | Line 74: | ||
** documenting solution (primary owner of design spec) | ** documenting solution (primary owner of design spec) | ||
** focus on analysing all existing docs and making sure nothing is missing | ** focus on analysing all existing docs and making sure nothing is missing | ||
| - | ** serving as a liaison between Implementation | + | ** serving as a liaison between Implementation team (Kiev) and Requirements team (NY) |
| - | === Implementation | + | === Implementation team === |
* '''Kostya''' - lead developer and development manager | * '''Kostya''' - lead developer and development manager | ||
Revision as of 05:29, 20 June 2010
About this doc
This wiki provides all Proj Management info for Cybertrax 2.1 Client project.
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)
Time allocated and Error margin
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.
Project documentation
All information is gathered and structured in several wikis under Category:Cybertrax 2.1 Client
Project communication
All communication is done through:
- mantis
- Skype
- email (everyone must check min 2 times a day and reply or at least confirm e-mail received same day)
All mantis tasks are under this parent: http://mantis.jaguarfreight.com/mantis/view.php?id=2077
Project update meetings
- who must attend: Andrei, Sasha, Alex, Denise, Tira
- Tuesd, Thursd 10-11am
- Skype chat
- Coordinator on NY side / Host: Alex
- Coordinator on Kiev side: Andrei
Project broadcasts and forum
- Broadcasts / News posted into mantis: http://mantis.jaguarfreight.com/mantis/view.php?id=2127
- Questions / answers about proj planning should be posted there as well
Project team and responsibilities
Requirements Team
- Alex - Proj Manager and Solutions Architect; responsible for:
- proj management/coordination
- intergation
- helping everyone as required
- Denise - Business Analyst; responsible for:
- gathering and documenting requirements and interfacing stackeholders/clients/module owners
- must help Sys Analysts to discover info
- proof reading/editing docs (in terms of English lang)
- Tira - Systems analyst; responsible for:
- creating solution based on requirements
- documenting solution
- focus on creating user interface mockups
- helping Denise in more technical aspects of requirements gathering/analysis
- Andrei - Systems analyst; responsible for:
- creating solution based on requirements
- documenting solution (primary owner of design spec)
- focus on analysing all existing docs and making sure nothing is missing
- serving as a liaison between Implementation team (Kiev) and Requirements team (NY)
Implementation team
- Kostya - lead developer and development manager
- Sasha - lead developer
- Andriy - developer
- Roma - QA and Support
Important Dates
- 1st date for Release: Thur, July 15
- 2nd date for Release: Thur, July 22
Mantis tasks
- 2129 Finalize/document "requirements"
- 2126 Finalize/document "data_dictionary"
- 2128 Finalize/document "design"
- Dev tasks TBD
Weekly Plan
week 1: June 7 Mon - June 11 Fri
Plan
- meetings with clients
- preliminary design sessions
- end of the week targets:
- 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
- end of the week targets:
- 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
- end of the week targets:
- requirements: 100% done
- design: 80% done
- documentation: optimization/grade B-
- 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
- end of the week targets:
- documentation: optimization/grade B
- 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
- end of the week targets:
- documentation: optimization/grade A
- 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
