List out the task to be done in sequence according to submission deadline of deliverables
Mark down every task with detailed sub task or work breakdown for better monitoring and control
Check priority and dependency of all task and readjust sequence if necessary for best arrangement to speed up task completion schedule, i.e. critical path
Milestone should be highlighted since payment would be paid to vendor, e.g. SA&D, UAT or Rollout
List out target and then actual start/end date, add remark in last row with team member name and pay special attention to critical task with biggest effect to the project
Fill in by project manager or team leader (top-down), can ask the team member to fill in estimation themselves based on past experience of similar work (bottom-up) and adjust by system analyst
Allow sufficient time for project task
Buffer time cover application, feedback, approval, rejection, amendment, resubmission and effective required days such as firewall setting
Allow 1 to 2 weeks for user comment but prevent endless loop by user that delay project, especially too many details in requirement collection period, should be during implementation
Update schedule after adjustment by inserting a row below with only extra actual start/end date, responsible person and remark filled
Create Gantt Chart based on the input
Request for official extension if it is extra user requirement
Assign one person, such as project coordinator or external quality reviewer to check and remind all members of the progress
Reminder for task start, half time past, 1/3 time left, 1 week before deadline, 3 days and over due by email, phone call or in person contact especially for implementation or user feedback
Check status when 1/3, 1/2 or 3/4 time pass and make reminder or warning to team member
Report problem but not hide if anything could affect schedule for supervisor to readjust
Real time monitoring could use automation management tools with Dashboard functionality showing work in progress, completed and pending.
Overall project status could be shown in different lighting:
Green: project is on track
Yellow or Orange: warning that needs attention
Red: problem found
Blue: pause or pending
Purple: external dependencies
Escalate problem if ignore or without enough attention
Remind all team member consequences of project delay, i.e. penalty, bonus or even company crisis
Some big company will record delay related to team member in staff record of annual appraisal
One approach is to finish the easy task first, usually could finish quick and left more time for complicated task
Use color to reflect project task progress, background color white means not start, yellows in progress, orange subjected to further checking although complete, green means done; front color red means problem found
Reorganize, redistribute and reschedule outstanding tasks may catch up overall project schedule
Execute different task at same time by different parties could improve schedule
Item trade off to speed up development sometime
Some minor items to be developed later on or during maintenance period
No responses yet