Cybertrax 2.1 Client (PM)

From UG

Revision as of 02:00, 20 June 2010 (edit) Alex (Talk | contribs) (→Project schedule) ← Older edit		Revision as of 02:02, 20 June 2010 (edit) (undo) Alex (Talk | contribs) (→week 6: July 12 Mon - July 16 Fri) Newer edit →
Line 112:		Line 112:
	* Release		* Release
		+	* '''Mon 9am:''' release to Staging
	* '''Tue 10pm:''' Kiev/NY status update		* '''Tue 10pm:''' Kiev/NY status update
	* '''Thur 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 ===		=== week 7: July 19 Mon - July 23 Fri ===

---

Revision as of 02:02, 20 June 2010

Contents 1 About this doc 2 Project documentation 3 Project communication 4 Project team 5 Project business processes and tools 6 Project update meetings 7 Project broadcasts and forum 8 Project schedule 8.1 week 1: June 7 Mon - June 11 Fri 8.2 week 2: June 14 Mon - June 18 Fri 8.3 week 3: June 21 Mon - June 25 Fri 8.4 week 4: June 28 Mon - July 2 Fri 8.5 week 5: July 5 Mon - July 9 Fri 8.6 week 6: July 12 Mon - July 16 Fri 8.7 week 7: July 19 Mon - July 23 Fri 9 Project plan and do list

About this doc

This wiki provides all Proj Management info for Cybertrax 2.1 Client project.

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

All mantis tasks are under this parent: http://mantis.jaguarfreight.com/mantis/view.php?id=2077

Project team

Project business processes and tools

Project update meetings

• who must attend: Andrei, Sasha, Alex, Denise
• 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 should be posted there as well or we will use wiki discussion, see http://en.wikipedia.org/wiki/SummarizeDiscussion

Project schedule

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

Project plan and do list