Business of IT - Project Management (D324)

Correct Answer

D. control

Explanation

Project work thrives in environments that emphasize collaboration, creativity, and adaptability. While control can be important in some organizational settings, too much focus on control can stifle innovation and hinder the flexibility needed to complete projects successfully. Cultures that prioritize member identity, group emphasis, and risk tolerance foster more effective project work, as they encourage team collaboration and the willingness to take risks to achieve success.

Why other options are wrong

A. member identity

Member identity refers to how strongly employees identify with the organization or team. A strong sense of identity contributes to higher commitment, collaboration, and motivation in project work.

B. group emphasis

Group emphasis highlights the importance of teamwork and collaboration, which is critical in project work. Projects often require cross-functional cooperation, and a culture that values group effort fosters project success.

C. risk tolerance

Risk tolerance is essential for successful project work, as projects often involve uncertainty and challenges. A culture that encourages risk-taking allows teams to innovate and pursue opportunities without the fear of failure.

Correct Answer

a. unit testing, integration testing, system testing, user acceptance

Explanation

The preferred order of testing on IT projects follows a logical progression:

Unit testing is conducted first, focusing on testing individual components or functions to ensure they work correctly in isolation.

Integration testing is next, verifying that the individual components work together as expected when combined.

System testing checks the entire system as a whole, making sure it meets the overall requirements and functions as intended.

User acceptance testing (UAT) is the final phase, where the users test the system to confirm it meets their needs and requirements.

Why other options are wrong

b. unit testing, system testing, integration testing, user acceptance testing - System testing should come after integration testing, as integration ensures that components work together before testing the whole system.

c. unit testing, system testing, user acceptance testing, integration testing - Integration testing should be performed before system and UAT testing to ensure that components are working together before the full system is tested or accepted by the user.

d. unit testing, integration testing, user acceptance testing, system testing - User acceptance testing comes after system testing to ensure the system works as intended before getting feedback from users.

Correct Answer

B. business case

Explanation

The business case is typically completed before initiating a project. It provides the justification for the project, outlining the benefits, costs, and potential value it will bring. It is a critical document that helps stakeholders decide whether the project is worth pursuing.

Why other options are wrong

A. stakeholder register

The stakeholder register is developed during the initiation phase and identifies stakeholders involved in or impacted by the project. It is not typically completed before initiating the project, as it relies on identifying those stakeholders once the project is being planned.

C. project charter

The project charter is created during the initiation phase to formally authorize the project and outline its objectives, scope, and stakeholders. It is not usually completed before initiating the project but rather as part of the initiation process.

D. kick-off meeting

The kick-off meeting occurs after the initiation phase when the project team and stakeholders gather to discuss the project’s goals, roles, and responsibilities. It is not completed before initiating the project but marks the beginning of the project execution phase.

Correct Answer

D. Fast tracking is a technique for making cost and schedule trade-offs to obtain the greatest amount of schedule compression for the least incremental cost.

Explanation

Fast tracking involves overlapping project phases or activities that were originally scheduled to be performed sequentially. It is primarily focused on schedule compression rather than balancing cost and schedule. The statement in option D confuses fast tracking with crashing, which is the technique used to make cost and schedule trade-offs to achieve schedule compression at the least additional cost.

Why other options are wrong

A. Growing grass was on the critical path for a large theme park project.

This statement is true. For some projects, like the construction of a theme park, certain activities (such as growing grass or landscaping) might end up on the critical path if they cannot be accelerated or overlapped with other activities.

B. The critical path is the series of activities that determine the earliest time by which a project can be completed.

This statement is true. The critical path is the longest path in the project network and determines the earliest time the project can be completed, as delays in critical path activities will delay the entire project.

C. A forward pass through a project network diagram determines the early start and early finish dates for each activity.

This statement is true. A forward pass through the project network diagram helps determine the early start and finish dates for each activity by moving from the beginning to the end of the project timeline. This process helps in schedule planning.

Correct Answer

A. Configuration management

Explanation

Configuration management is a process that ensures that the descriptions of the project's products (deliverables) are correct and complete. It involves managing and controlling changes to project documents, deliverables, and other items that are part of the project's scope. This process ensures that any changes are made systematically and that the project’s products are clearly defined and properly controlled.

Why other options are wrong

B. Integrated change control

Integrated change control is a process that evaluates and manages changes to the project’s scope, schedule, and resources. While it plays a role in managing changes, it does not directly focus on ensuring that the descriptions of the project's products are correct and complete, which is the focus of configuration management.

C. Integration management

Integration management is the process of aligning and coordinating various project elements, but it does not specifically ensure the correctness and completeness of product descriptions. It involves processes like project planning, execution, and controlling, integrating all aspects of the project, rather than specifically managing product descriptions.

D. A change control board

A change control board (CCB) is a group responsible for reviewing and approving changes to the project. While the CCB helps manage changes, it does not directly ensure the correctness and completeness of product descriptions. That responsibility falls under configuration management.

Correct Answer

B. fallback

Explanation

A fallback plan is a backup or alternative plan that is put in place if the primary plan (in this case, using the new release of software) does not work out.

Why other options are wrong

A. contingency

Contingency plans are used to address potential risks, but a fallback plan specifically focuses on an alternative action if the primary plan fails.

C. reserve

A reserve is a buffer or additional resources set aside to handle unforeseen events, not an alternative plan.

D. mitigation

Mitigation refers to efforts to reduce the impact or likelihood of risks, but it does not involve having an alternative plan if the original one fails.

Correct Answer

A. interviews

Explanation

Interviews are often the most expensive and time-consuming technique for collecting requirements because they involve one-on-one interaction between the interviewer and the interviewee. This process can be resource-intensive, requiring significant time to schedule, conduct, and analyze the responses. Interviews are often used to gather in-depth, qualitative information from stakeholders, which can be valuable but requires careful planning and effort.

Why other options are wrong

B. focus groups

Focus groups are a group-based technique used to gather feedback from multiple participants at once. While they can be time-consuming, they tend to be less expensive than individual interviews and provide broader insights in a shorter time frame.

C. surveys

Surveys are a less expensive and quicker way to collect data from a large number of people. While they can be time-consuming to design and analyze, they are generally more efficient than interviews for gathering data from a large population.

D. observation

Observation is a method of collecting data by watching people or processes in action. It is generally less time-consuming and expensive than interviews, although it may still require effort to analyze the observed data. It is not typically as costly or time-intensive as conducting interviews.

Correct Answer

a. Contingency

Explanation

Contingency reserves are used to cover unforeseen events or situations that may arise during a project. These reserves are part of the project plan to address unpredictable issues that may affect the project's timeline or costs.

Why other options are wrong

b. Financial - Financial reserves refer to funds set aside for general business operations, not specifically for dealing with unexpected situations in project management.

c. Management - Management reserves are often used for unforeseen events but are broader and typically used for management decisions, not just unpredictable situations.

d. Baseline - A baseline is a fixed reference point used for measuring and comparing project performance, not a reserve for managing risks.

Correct Answer

A. Project management

Explanation

Project management is defined as the application of knowledge, skills, tools, and techniques to project activities to meet project requirements. It involves planning, executing, and closing projects to achieve specific goals within a defined timeframe, scope, and budget.

Why other options are wrong

B. Program management

Program management refers to managing a group of related projects to achieve strategic objectives. Unlike project management, which focuses on individual projects, program management coordinates multiple projects for broader organizational benefits.

C. Project portfolio management

Project portfolio management involves managing a collection of projects and programs within an organization to ensure they align with business strategy and objectives. It focuses on prioritizing and selecting the right projects rather than managing individual projects directly.

D. Requirements management

Requirements management involves gathering, analyzing, and managing project requirements. While it is a critical part of project management, it is a specific process rather than the overall application of knowledge, skills, tools, and techniques across a project.