Task Essay Example

  • Category:
  • Document type:
  • Level:
    High School
  • Page:
  • Words:

Project Questions

Submission Date:

  1. The purpose of the case study in a project is to help an individual to get more insight to a phenomenon and how different theories and concepts are applied. This is important in helping one to understand these theories and concepts are applied in real situation.

  2. It is important to use scope and out of scope in the sense that it helps identify the elements of time and cost the project will take and also other elements not covered. This is important in planning the implementation process of the project.

  3. A milestone helps describes the status of the project while the deliverable is described as an outcome of a project that can measured and verified. In addition to this, a milestone describes all the steps that have to be covered in the project implementation.

  4. Communication in the project is important in the sense that it helps disseminate important information about the project progress to various stakeholders. This is important in coordinating the various stakeholders and activities of the project.

  5. The purpose of the network diagram is to show different activities that will be performed and therefore constraint could not be catered for. In other words, the network diagram is only used as a management tool to show what activities that have to be performed in a given project.

  6. Communication with the stakeholders is beneficial in the sense that it helps engage the stakeholders and address their interests more effectively. It is through communication that the project manager will be able to monitor the progress of the project based on the available information.

  7. The purpose of change control is to ensure that there are no unnecessary changes that are made to the project and that all changes made are recorded. This is important in ensuring that a project is focused on its goals and objectives.

  8. The primary purpose of WBS is to help the project planners and organizers to accurately define and specify the scope of their project.

  9. Top-down methods uses someone with experience to help determine the duration of the project. On the other hand, the bottom-up method serves as a check on various cost elements as identified in the WBS.

  1. A network diagram is a flow chart that is used by the project planners and organisers to show the different tasks that should be performed as shown in the diagram below and the sequence that will be followed. The network diagram from the start to the finish shows various activities and their levels of interdependence.


Network Diagram Example

A network diagram is the most excellent way of planning and replanning a particular project by showing all the project activities, the sequence and most important the critical path. A critical path in project management refers to the longest sequence of the identified activities in the project plan that must be completed on time in order for the project to complete on the required date. This technique as indicated by a red colour in the above network diagram is used in project management to help ensure that more focus is placed on key tasks. The use of network diagram has both pros and cons.

Pros of network diagrams

  1. With network diagrams, the planning team is able to identify all tasks that are necessary for completion for the project to be successful.

  2. Further, network diagrams in project management are also important in building a strong view of how the project will progress and how each task will affect the flow of the whole project. This is important in ensuring that special attention is given to critical activities of the project.

  3. Finally, network diagrams are also important in setting the project duration and deadline.

  1. Network diagrams do not help identify the constraints that will be faced on each and every task. It is therefore based on assumptions that whatever the constraints, the project flow will not be affected.

  1. Parallel planning entails the process of making other small plans about a project which should run concurrently with the main project plans. In project terms, parallel plan is actually considered a contingency plan and in most instances it is used as a back-up in case there was failure in the main project activities. Parallel planning is common in IT projects. Perhaps, because of the nature of works IT projects are aimed at addressing. There are various reasons that make parallel planning important with the case of IT projects.

First and foremost, many of the IT projects are expected to touch on the data that is being used by an organisation on a daily process. This means that an organisation may be depended entirely on the information input in the IT systems and hardware. Unlike the case of the other projects which can run independently with affecting the organisational processes, IT projects do. In that case therefore, parallel planning is encouraged to ensure that at times organisational processes and operations are not disrupted for lack of data processing.

In addition to this, there is also an aspect of security. IT projects are aimed at helping organisations apply IT tools to collect, analyze and share information among the stakeholders for the purpose of decision making. Parallel planning in IT projects is therefore very important in safeguarding an organisation’s information from loss.

  1. IT project management methodology should be flexible in order to allow for software upgrade at all times. This is the case technology continues to change and therefore flexibility will allow for new updates to the IT systems.

  2. Project selection and approval process is need in project management to help get the most viable project.

  3. Project success refers to the level at which a project is able to deliver on the goals and objectives of the user. In other words, a project that is a success is the one that helps deliver the intended deliverables.

  4. Triple constraint need to be managed for three main reasons: remain within the project scope, control cost and finish the project within the required time. Triple constraint limits the project to specific activities, budget allocated and the estimated time duration.

  5. Project oriented scope entails those tasks are aimed at helping completing a given project. On the other hand, the product oriented scope entails tasks that are aimed at producing a particular product.

  6. Product oriented scope is more important. This is because it will affect the user satisfaction level. In addition to this, the success of a project will depend on how best an organisation understand what product a given project is expected to deliver or improve.

  7. Risks are mitigated in order to help to reduce the chances of project failure. This is because many risks are likely to hinder the progress of the project.

  8. Risk management in IT project is important in safeguarding organisational data and information.

  9. Communication channel refers to the media through a message flows. Communication channels include: face-to-face, mobile, electronic and written.

  10. WBS is important in ensuring consistency in project planning and execution since it breaks the project into small and manageable components.

  11. Deserve in budget, refers to adequate budget for executing a given project. This budget is based on the different activities of the projects and their respective costs.

  12. In scope and out of scope gives the project manager the opportunity to focus his attention on important elements of the project and whose management will affect the outcome of the whole project.

  13. A quality plan refers to the team’s blue on how to produce quality deliverables.

Quality assurance policies and systematic activities to ensure quality deliverables

Quality assurance is the means to ensure that the required standards are maintained are maintained throughout the project.


Berkun, S. 2005. The Art of Project Management. O’Reilly Media.

Charvat, J. 2003. Project Management Methodologies: Selecting, Implementing, and Supporting Methodologies and Processes for Projects. Hoboken, NJ: John Wiley & Sons.

Kerzner H. 2003. Project Management: A Systems Approach to Planning, Scheduling, and Controlling JohnWiley and Sons.

Ramakrishna, K. 2010. Essentials of Project Management,PHI Learning Pvt. Ltd, Boston, Massuchetts.