Project management assignment
Table of Contents
The essay discusses basic prices of project management. The first part tackles the initial technical aspect of project planning where scheduling is done to determined logical flow of activities. At this stage, a critical path is determined and project is visualised using Gantt chart and network diagram. Importance of network diagrams is also discussed. The second case discusses general skills and competencies that are needed to successful project management. A range of skills are classified by various authors. In this article, skills that are discussed include technical, communication, people management, and leadership and motivation skills. 2.0 Task A: Project scheduling
2.1 Network diagram
2.2 How timing of activities was done
Timing of activities was done using a scheduling technique where the main aim to list and arrange activities in a sequence that leads to realisation of the final goal, which is completion of the goal in time, in the required quality and using the planned goals. In scheduling, a Gantt chart was drawn which helped visualise when all activities were to be accomplished, where there was start and finish time. Relationship between activities was worked out finally when coming up with a network diagram, whose purpose was to provide a visualisation overview of flow of all activities and how they relate with each other. 2.3 Determination of total float
This is the time that a project can be delayed without affecting the time of completion of the whole project or without affecting the project schedule. This was calculated by getting the difference between the latest finish and the earliest finish. It could also be calculated from getting the difference between latest start and earliest start of the whole project (Lester, 2007). 2.4 Determination of the critical path
Critical path is determined by summing up the durations of activities during which no activity can be delayed without affecting the schedule of the project. This is the longest path that the project can take and which determines shortest time that a project can take to be fully completed. To determine activities which are critical, calculation of earliest time to start and latest to finish time was calculated to find the slack time. Where activities had a slack time of zero, the activities was considered as critical; it meant the activity could not be delayed or started earlier as then it would delay the whole project. The activities have these conditions: ES=LS and EF=LF. The critical path had also to flow continuously, carrying all the activities which determine the earliest time when the project would be carried. 2.5 The earliest the project can be completed if it started on 9 May 2011 The earliest time the project can be completed is 28 August 2011. This was calculated by calculating the time of all possible critical paths and taking the shortest. A project could have more than one critical path on basis that it carries activities from beginning to the end. The time of all critical activities was carried added to the beginning date (9 May 2011), excluding weekends. 2.6 Effect of the duration of the project if the following happened: a) If P delayed by 1 day: This would not affect duration of the project, it is not a critical activity. The slack time is not zero in this and therefore has no effect on duration of the project duration or completion date. b) If activity Q is delayed 1 day, the project duration would also not be delayed. Also, Q is not a critical activity considering that its ES≠LS and EF≠LF. ES-LS and EF-LF=1, hence not a critical path because of the one day float. c) A 2 day delay during activity M would not affect the duration of the project. ES≠LS and EF≠LF. ES-LS and EF-LF=2, which means the activity has a float of 2 days which means the project can be delayed by this duration without affecting the schedule...
References: Cagle, R. B., 2005. Your Successful Project Management Career. New York: AMACOM.
Campbell, C. A., 2010. The One-Page Project Manager: Communicate and Manage Any Project With a. New York: Joghn Wiley & Sons.
Dow, W. & Taylor, B., 2010. Project Management Communications Bible. New York: Taylor & Francis.
Grande-Bretagne, 2009. Managing successful projects with PRINCE2. Norwich: The Stationery Office.
Heldman, K., 2011. PMP Project Management Professional Exam Study Guide. New York: John Wiley & Sons.
Kliem, R. L., 2008. Effective Communications for Project Management. Boca Raton: CRC Press.
Lester, A., 2007. Project Management, Planning and Control: Managing Engineering, Construction. 5th ed. Burlington: Butterworth-Heinemann.
Levin, G., 2010. Interpersonal Skills for Portfolio, Program, and Project Managers. Vienna: Management Concepts Press.
Luckey, T. & Phillips, J., 2011. Software Project Management For Dummies. New York: John Wiley & Sons.
Morris, P. & Pinto, J. K. eds., 2010. The Wiley Guide to Project Organization and Project Management Competencies. New York: John Wiley & Sons.
Murch, R., 2001. Project Management: Best Practices for IT Professionals. Upper Saddle River: Prentice Hall Professional.
Neil, W., 2013. Core Competencies of a Project Manager. [Online]
Available at: http://www.linkedin.com/groups/Core-Competencies-Project-Manager-89398.S.93636213
Parker, D., Craig, M. & Craig, M. A., 2008. Managing Projects, Managing People. Sydney: Macmillan.
Richman, L., 2006. Improving Your Project Management Skills. New York: AMACOM.
Richman, L., 2011. Improving Your Project Management Skills. 2nd ed. New York: AMACOM.
Rick A. Morris, B. M. S., 2008. Project Management That Works: Real-World Advice on Communicating, Problem Works. New York: AMACOM Div American Mgmt Assn.
Royer, P. S., 2002. Project Risk Management: A Proactive Approach. Vienna: Management Concepts Press.
Turner, J. R., 1999. The Handbook of Project Based Management: Improving the Processes for Achieving Strategic Objectives. New York: McGraw-Hill Education.
Please join StudyMode to read the full document