Business of IT - Project Management (D324)

Correct Answer

C. Scope

Explanation

The scope of a project refers to all the work required to create the project's deliverables and the processes used to complete them. It outlines what is included and excluded from the project and ensures that all necessary tasks are identified and completed. The scope defines the boundaries of the project and serves as a guide for project execution and control.

Why other options are wrong

A. Deliverables

Deliverables are specific, measurable outputs produced as a result of the project. While deliverables are part of the project scope, they do not encompass all the work involved in creating the products or the processes used to create them.

B. Milestones

Milestones are key events or achievements in a project timeline that mark significant progress. They are part of the project's schedule but do not represent all the work involved in creating the products or the processes.

D. Product development

Product development refers to the process of designing, creating, and bringing a product to market. It is a part of the project scope but does not encompass all the work involved in the entire project, which may include other aspects beyond product development.

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

D. a Gantt chart

Explanation

A Gantt chart is a tool used to represent the project schedule visually, showing tasks, timelines, and dependencies. However, it is not typically included in the project charter. The project charter is a high-level document that formally authorizes the project, defines the project's objectives, identifies key stakeholders, and includes the project manager’s name, but it does not usually contain detailed scheduling information such as a Gantt chart.

Why other options are wrong

A. the name of the project manager

The name of the project manager is typically included in the project charter because it is crucial to formally appoint someone who will be responsible for managing the project.

B. budget information

The project charter generally includes high-level budget information, outlining the financial resources available for the project. While detailed budget breakdowns are provided later, the charter includes a rough estimate of the budget.

C. stakeholder signatures

Stakeholder signatures may be included in the project charter as a means of securing formal agreement and approval from key stakeholders. Their signatures indicate their commitment to the project and understanding of its objectives.

Correct Answer

A. deliverable

Explanation

A deliverable is any product or service that is produced as part of a project. It can include reports, hardware, software, or services that meet project objectives. Deliverables are typically tangible outcomes that are delivered to the client or stakeholders upon project completion or during key milestones.

Why other options are wrong

B. product

A product refers to the final result or output of a project, but it is not necessarily a specific service or item that is delivered at each phase. A product can be the end result of a series of deliverables, but the term "deliverable" encompasses smaller, more specific outcomes produced during the project.

C. work package

A work package is a group of related tasks or activities within a project that are defined at a level where work can be assigned. Work packages are a part of project management planning but do not directly describe the tangible items or services delivered as part of the project.

D. tangible goal

A tangible goal refers to a concrete objective but not necessarily to a specific product or service delivered during the project. While goals can be measurable, the term "deliverable" is more precise in describing what is produced or provided within the scope of the project.

Correct Answer

b. It is ahead of schedule and over budget.

Explanation

Schedule Performance Index (SPI) = EV / PV. An SPI greater than 1 means the project is ahead of schedule, so 110 percent means the project is progressing ahead of schedule.

Cost Performance Index (CPI) = EV / AC. A CPI less than 1 means the project is over budget, so 95 percent means the project is over budget.

Why other options are wrong

a. It is ahead of schedule and under budget. - The CPI is less than 1, indicating the project is over budget, not under budget.

c. It is behind schedule and under budget. - The SPI is greater than 1, indicating the project is ahead of schedule, not behind.

d. It is behind schedule and over budget. - The SPI is greater than 1, indicating the project is ahead of schedule, not behind.

Correct Answer

D. The government requirement that prompted the project was repealed.

Explanation

McDonald's terminated the project after spending $170 million because the government requirement that initially prompted the project was repealed. This made the project unnecessary, leading the company to halt the initiative.

Why other options are wrong

A. The company found better technology.

Although technological advancements can influence decisions, there is no evidence that McDonald's found better technology that led to the termination of the project. The decision was based on the repeal of the government requirement.

B. The company decided to outsource the work.

Outsourcing the work was not the reason for the termination. The project was canceled because the external requirement was no longer in place.

C. The scope was too much to handle.

While scope management can be a factor in project decisions, the project was canceled due to the repeal of a government mandate, not because the scope was too challenging.

Correct Answer

A. developing the project business case

Explanation

The project business case is typically developed during the initiation phase, but it is not a formal process within project integration management itself. It serves as the justification for the project and provides the rationale for its initiation, often aligning with the organization's strategic goals. While it is crucial in project initiation, it falls outside the scope of project integration management, which focuses on processes that combine and align various elements of project planning and execution, such as developing the project charter, project management plan, and project closure.

Why other options are wrong

B. developing the project charter

The project charter is a fundamental process in project integration management. It formally authorizes the project, outlines objectives, and defines key roles, responsibilities, and resources. The charter serves as the foundational document that initiates the project, making it an integral part of project integration.

C. developing the project management plan

Developing the project management plan is a central process in project integration management. It defines how the project will be executed, monitored, controlled, and closed. This plan integrates and consolidates all subsidiary plans for scope, schedule, cost, quality, and other project management components.

D. closing the project or phase

Closing the project or phase is a key process within project integration management. It involves finalizing all project activities, delivering the completed project to stakeholders, and formally closing out contracts and documentation. This process ensures that all project objectives have been met and that the project is concluded in a controlled and systematic manner.

Correct Answer

A. systems development life cycle

Explanation

The Systems Development Life Cycle (SDLC) is a structured framework that outlines the phases involved in developing an information system. It typically includes stages like planning, design, development, testing, and implementation, guiding the development process to ensure that the system meets the desired requirements and functions correctly.

Why other options are wrong

B. rapid application development

Rapid Application Development (RAD) is an alternative software development methodology that focuses on quick development and iteration, but it does not describe a complete framework for developing information systems like SDLC does. RAD emphasizes rapid prototyping and user feedback rather than a structured set of phases.

C. predictive life cycle

A predictive life cycle refers to a project management model where detailed planning occurs upfront, and the project progresses sequentially. While this approach may be used for IT projects, it is not specific to the development of information systems, which is what SDLC describes.

D. extreme programming

Extreme Programming (XP) is an agile development methodology that emphasizes technical excellence, continuous feedback, and collaboration. While it is used in software development, it does not describe the complete framework for developing information systems, as SDLC does.

Correct Answer

B. minimize change

Explanation

While it is important to control and manage changes during a project, the goal is not to minimize change, but to manage it effectively. Change can be necessary and beneficial, so the focus should be on having a system in place to control and assess changes rather than minimizing them outright.

Why other options are wrong

A. use good configuration management

Good configuration management ensures that changes are tracked, documented, and communicated effectively. This helps in controlling project changes and maintaining consistency across the project.

C. establish a formal change control system

A formal change control system is essential for tracking and managing changes in an organized way. This ensures that all changes are documented and reviewed systematically.

D. view project management as a process of constant communication and negotiation

Effective communication and negotiation are critical for managing changes, as they help in aligning stakeholders and obtaining agreement on necessary adjustments.