Cybertrax 2.1 Client (project plan)

From UG

Revision as of 02:37, 20 June 2010 (edit) Alex (Talk | contribs) (Created page with 'Category:Cybertrax 2.1 Client') ← Older edit		Revision as of 02:41, 20 June 2010 (edit) (undo) Alex (Talk | contribs) Newer edit →
Line 1:		Line 1:
	[[Category:Cybertrax 2.1 Client]]		[[Category:Cybertrax 2.1 Client]]
		+
		+	== Intro ==
		+	This project is very important therefore planning is critical.
		+
		+	== 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

---

Revision as of 02:41, 20 June 2010

Contents 1 Intro 2 Weekly Plan 2.1 week 1: June 7 Mon - June 11 Fri 2.2 week 2: June 14 Mon - June 18 Fri 2.3 week 3: June 21 Mon - June 25 Fri 2.4 week 4: June 28 Mon - July 2 Fri 2.5 week 5: July 5 Mon - July 9 Fri 2.6 week 6: July 12 Mon - July 16 Fri 2.7 week 7: July 19 Mon - July 23 Fri

Intro

This project is very important therefore planning is critical.

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