8b
Task identification & time allocation
During the production of the project proposal to give an “at a glance” overview of the project, I came up with an initial plan outline shown below:
Thankfully, good project management doesn't end here - I will now analyse the project at a deeper level by breaking the tasks shown above into smaller subtasks. I will then allot a realistic amount of time to each activity while, at the same time, bearing dependencies between them in mind. Subsequently, the information produced here will be inputted into the “project file” for safe keeping and so that progress can be tracked in an effective and efficient manner.
Note: tasks highlighted red are areas of risk
Analysis of project
- Project proposal (Presented: Wed 07/03/2007)
- Functional specification (Presented: Fri 09/03/2007)
- Task identification (Complete: 1 hour)
- Time allocation (Complete: 15 mins)
- Risk assessment (30 mins)
- Setup Microsoft Project 2003 “project file” (30 mins)
- Input tasks (15 mins)
- Assign resources to activities (30 mins)
- Produce GANTT chart 1 in MS Project (10 mins)
- Produce PERT chart and identify critical path (1 hour)
- Present plan to client (1 hour)
Initial design
- Compare old design with new concept (1 hour)
- Refine graphical design (3 hours)
- Produce navigational graphics (1 hour)
- Informally explain navigation to client (30 mins)
- Make necessary adjustments (30 mins)
- Finalise design concept (1 hours)
- Produce storyboards (4 hours)
- Update “project file” and produce GANTT chart 2 (1 hour)
- Present final design to client (1 hour)
Prototyping and formative testing
- Explain prototyping/evolutionary-development model to client (30 mins)
- Produce first prototype: version 1.0 (3 days)
- Document production techniques and formative testing (2 hours)
- Produce prototype evaluation questionnaire (30 mins)
- Present first prototype and questionnaire to client (1 hour)
- Evaluate prototype using functional specification (1 hour)
- Produce second prototype: version 2.0 (3 days)
- Document adjustments made in second prototype production (1 hour)
- Update “project file” and produce GANTT chart 3 (1 hour)
- Present second prototype and questionnaire to user-group (2 hours)
- Evaluate prototype using functional specification (1 hour)
- Complete product: version 3.0 (3 days)
- Document adjustments made in completing product (2 hours)
- Hold interim review meeting (30 mins)
Summative testing
- W3C XHTML Validation (1 hour)
- W3C CSS Validation (10 mins)
- JavaScript function testing (30 mins)
- Adobe Flash XML-based slideshow testing (30 mins)
- Update “project file” and produce GANTT chart 4 (1 hour)
Documentation
- Produce “Getting started” instructions (2 hours)
- Produce “Updating & adjusting” guidelines (2 hours)
- Update “project file” and produce GANTT chart 5 (1 hour)
Send deliverables
- Burn XHTML version and other deliverables to CD-ROM (10 mins)
- Zip and send (via Skype) PHP version to Mr G Yuen (5 mins)
- Hold end of project review meeting (1 hour)
Risk assessment
I have identified quite a number of areas of risk. Each one of these includes extra human involvement. This is quite an interesting observation. Being rather new to project management, especially with regard communicating formally with clients, organising meetings with some of the stakeholders may be prove to be tricky. For example, the ideal end of project review meeting would bring senior management and my client together but, at present, this seems to be unrealistic.
I believe I have allowed enough time for these areas of risk. However, they remain the most uncertain tasks because of the unpredictability of human beings. Another thing to note is that the majority of the meetings are all at significant stages of the project. They must therefore be well planned and well documented.
« BACK | Back to top | NEXT »
