322AA Information Technology : Typical and Probable Risk

Gantt chart-Take the WBS you have already developed. Define all of the activities that will be necessary to create each deliverable in your WBS. Create a schedule for your project. First create the schedule by hand using Post-it Notes, and then put the information into MS Project. Take screenshots of the schedule to be pasted in your word document that you are submitting. Be sure to include all of the summary rows (including the first row for the project title) and any key milestones.

Make sure the critical path is easy to see
Create a time-phased budget for your example project using bottom-up estimating. To the extent your sponsor will supply rates for workers, use those. Approximate rates for ones you cannot get. Ask your sponsor how they treat indirect costs. Be sure to include direct labour costs for you and your team mates and add 20% for fringe. State all assumptions and constraints you have used when creating your budget. State how confident you are in your estimates and what would make you more confident. Give examples of known knowns and known unknowns on your project. Tell how you have budgeted for both of them plus how you have budgeted for unknown unknowns. 

Answer:

Task 1

WBS 

Task 2

Gantt chart 

Task 3

Time-phased budget

Training cost of employees 5000 AUD

Training the administrative workers 1000 AUD

Programmer 5000 AUD

Database manager 3000 AUD

Total amount 50,000 AUD

Task 4

Risk register

The risk register would entirely be based over the typical and probable risk that might hamper the proceedings of any project (Tipton & Nozaki, 2012).

Task 5

Quality management plan

• Ensuring quality standard has been adhered
• Defining the way quality is to be managed
• Defining quality assurance activities
• Implementing acceptable or reasonable quality standards

Task 6

Closure checklist and project evaluation

• Handing over total deliverables
• Each of the deliverables have been signed off and have also been acknowledged by the client or sponsor
• The final status of the project is complete
• Every financial process and the report is complete
• Assessing the project post complete is also complete
• Assessing staff presentation  is approved and complete
• Staff unemployment over the termination of the project
• Every procedure and the contract have been terminated post completion of the project
• Every site and their operations initiation are shut down
• Discarding materials and equipments is finished
• Making announcement regarding conclusion of the final project
• Storage upon conclusion of the project

References:

Corral, L., Sillitti, A., & Succi, G. (2012). Mobile multiplatform development: An experiment for performance analysis. Procedia Computer Science, 10, 736-743.

Espie, C. A., Kyle, S. D., Williams, C., Ong, J. C., Douglas, N. J., Hames, P., & Brown, J. S. (2012). A randomized, placebo-controlled trial of online cognitive behavioral therapy for chronic insomnia disorder delivered via an automated media-rich web application. Sleep, 35(6), 769-781.

Horner, J. (2011). RApache: Web application development with R and Apache.

Osentoski, S., Jay, G., Crick, C., Pitzer, B., DuHadway, C., & Jenkins, O. C. (2011, May). Robots as web services: Reproducible experimentation and application development using rosjs. In Robotics and Automation (ICRA), 2011 IEEE International Conference on (pp. 6078-6083). IEEE.

Winesett, J. (2012). Web Application development with Yii and PHP. Packt Publishing Ltd.