โ† All IKM Flashcard Decks

IT Project Management Principles Flashcards

6 cards from real IKM practice questions. Tap to flip, then mark Knew It or Still Learning โ€” missed cards come back until you master them.

Read the first 6 IT Project Management Principles flashcards as text
  1. An IT project manager is using the Critical Path Method (CPM) for scheduling. A delay on a specific task has occurred, but the overall project deadline has not been affected. How is this possible?

    Answer: The delayed task was not on the critical path and had sufficient float.

    The Critical Path Method identifies the longest sequence of dependent tasks that determines the shortest possible project duration. Tasks on this critical path have zero float or slack. A delay in any critical path task will delay the entire project. Tasks not on the critical path have float, which is the amount of time they can be delayed without affecting the project's completion date.

  2. A software development team is working on a project where the requirements are expected to change frequently based on stakeholder feedback after each new feature is demonstrated. Which project management methodology is most suitable for this scenario?

    Answer: Agile

    Agile methodologies are designed for projects with evolving requirements. They use an iterative approach, breaking the project into small, manageable units (sprints or iterations) that allow for frequent feedback and adaptation. The Waterfall model, in contrast, is a linear, sequential approach best suited for projects with clearly defined and stable requirements from the outset.

  3. Which of the following is the primary purpose of a Work Breakdown Structure (WBS) in IT project management?

    Answer: To provide a hierarchical decomposition of the project's total scope of work.

    The primary purpose of a Work Breakdown Structure (WBS) is to break down the total project scope into smaller, more manageable components called work packages. It is a deliverable-oriented hierarchical decomposition of the work to be executed by the project team. While it serves as a key input for scheduling, resource assignment, and cost estimation, its core function is to define and organize the project's scope.

  4. During the execution phase of an IT infrastructure upgrade, a key stakeholder submits a formal request to add a new server that was not in the original plan. What is the immediate next step the project manager should take according to standard change control procedures?

    Answer: Log the change request and assess its impact on the project's scope, schedule, and budget.

    A formal change control process requires that all change requests are documented and evaluated before being approved or rejected. The first step is to log the request and then conduct a thorough impact assessment on key project constraints like scope, time, and cost. This ensures that decisions are made with a full understanding of the consequences, rather than reacting without analysis.

  5. A project manager is developing a risk management plan for a new data center migration project. The first step in the project risk management process is:

    Answer: Risk Identification

    The risk management process begins with identifying potential risks that could impact the project. This involves brainstorming and documenting all potential threats and opportunities before they can be analyzed or have responses planned for them. The subsequent steps include analysis (qualitative and quantitative), planning responses, and monitoring.

  6. In an IT project, what is the main difference between a risk and an issue?

    Answer: A risk is a potential event that may or may not happen, while an issue is a problem that is currently happening.

    A risk is an uncertain event or condition that, if it occurs, has a positive or negative effect on a project's objectives. It is a potential future problem. An issue is a current problem or event that has already occurred and is impacting the project. Risk management is proactive (planning for what might happen), while issue management is reactive (dealing with what has happened).