Cycle Task Planning Form v1.0
NAME TITLE CYCLE DATE
WBS#
Task Name Estimation Resource Description Entry Criteria (Dependence) Exit Criteria (Output) Milestones
Cycle Task Planning Form Instruction
Objective: Gather tasks planning from each member, to make development plan for the whole team for the whole cycle. Who should fill up this form? All team members. What should be included? The tasks define in WBS, owned by individual member. When should be submit? At the beginning of each cycle Instruction
Name: Input your name example: Dawei Gu Title: Input your team role title example: Planning Manager Cycle: The cycle information, (planning manager will do it) example: No.1 Learning Cycle– Basic Date: The begin and end date of the cycle, (planning manager will do it) example: 09/17/2002 to 10/1/2002 Task No: The tracking number of the task according to WBS.
example : 1.5.1
Task Name: The name of task
example : Talk to “Experts”
Estimation: Time Estimate for whole task (in hours)
example : 1.5 hours
Resource (People): Designated specific person or any available person
example : Lalit => 1 hour [Someone] => 0.5 hours
Description: Description of task for better understanding example: Talk to expert, ask for suggestion on PALM development. Entry criteria: Task dependencies: what other tasks, if any (Track by Task # of other Task) example: Complete task 1.4.2
Exit criteria: Artifacts from Task example: Comprehensive report about all possible PALM development tech. Milestone: For a long time tasks’ Intermediate milestones (for tracking/earned value) example: -Finish PALM developing language report -Finish PALM emulator report