Project Selection and Management Overview

<p>Only one of the projects may be selected (A)</p> Signup and view all the answers

<p>How much of the organization is affected by the system (A)</p> Signup and view all the answers

<p>Choosing between multiple high-payoff, high-risk projects (D)</p> Signup and view all the answers

<p>To improve the technical infrastructure (A)</p> Signup and view all the answers

<p>To return a greater amount than the total project costs (C)</p> Signup and view all the answers

<p>To manage the project tasks and schedule (B)</p> Signup and view all the answers

<p>Task dependencies and current statuses (B)</p> Signup and view all the answers

<p>To ensure essential steps are not overlooked (B)</p> Signup and view all the answers

<p>Changes needed to meet the project deadline (A)</p> Signup and view all the answers

<p>Detailed marketing strategies (C)</p> Signup and view all the answers

<p>To keep the business running. (C)</p> Signup and view all the answers

<p>It depends on the business lines that create the most value. (C)</p> Signup and view all the answers

<p>Must-do’s, should-do’s, and nice-to-do’s. (C)</p> Signup and view all the answers

<p>Business initiatives and strategies are enabled by IT. (A)</p> Signup and view all the answers

<p>Only during infrastructure upgrades. (D)</p> Signup and view all the answers

<p>Return on investment and financial measures. (A)</p> Signup and view all the answers

<p>More innovation. (A)</p> Signup and view all the answers

<p>Service levels, cost, and productivity measures. (C)</p> Signup and view all the answers

<p>To respond to user demands for speed and flexibility. (B)</p> Signup and view all the answers

<p>It enables teams to adjust functionality based on delivery dates. (B)</p> Signup and view all the answers

<p>They fail to adapt easily to schedule changes. (D)</p> Signup and view all the answers

<p>They designated certain team members as agile mentors and coaches. (D)</p> Signup and view all the answers

<p>RAD methodologies involve close user involvement throughout the project. (D)</p> Signup and view all the answers

<p>Monitoring project time schedules is complicated. (B)</p> Signup and view all the answers

<p>When the user base demands regular updates and iterations. (A)</p> Signup and view all the answers

<p>User-centered design and close involvement. (A)</p> Signup and view all the answers

<p>Calculating the time spent in the planning phase. (A)</p> Signup and view all the answers

<p>35% (C)</p> Signup and view all the answers

<p>They do not account for the specifics of the individual project. (D)</p> Signup and view all the answers

<p>Through their past project experiences and established methodologies. (A)</p> Signup and view all the answers

<p>22.66 person-months (C)</p> Signup and view all the answers

<p>Maintaining a record of actual time and effort values. (D)</p> Signup and view all the answers

<p>30% (A)</p> Signup and view all the answers

<p>It helps in avoiding overall project failure. (A)</p> Signup and view all the answers

<p>9 days (C)</p> Signup and view all the answers

<p>Staging database design (A)</p> Signup and view all the answers

<p>Universe design and Develop OLAP design part 1 (C)</p> Signup and view all the answers

<p>9 days (D)</p> Signup and view all the answers

<p>Open (D)</p> Signup and view all the answers

<p>Data export utility design (B)</p> Signup and view all the answers

<p>4 days (C)</p> Signup and view all the answers

<p>Develop OLAP design document (B)</p> Signup and view all the answers

<p>Web entry application UI design (B)</p> Signup and view all the answers

<p>High-priority reports design (B)</p> Signup and view all the answers

A collection of projects an organization undertakes, carefully balanced for optimal benefit and risk.

Factors used to evaluate and prioritize projects, considering size, cost, purpose, length, risk, scope, and economic value.

The chance of a project failing to deliver expected outcomes. It's crucial to asses its level.

The magnitude of a project, often measured by the number of people involved.

The financial resources needed to implement a project.

The main goal or objective of the project, ranging from infrastructure improvement to supporting business strategy

The process of overseeing and prioritizing a project portfolio by the selection committee.

The process of assigning resources (funds or staff) to different projects in a portfolio for the best possible outcome of the selected ones

CIOs categorize projects based on their roles (keeping business running, innovation, and strategic opportunities), adapting to the business environment.

At Marriott, IT projects are viewed as components of business initiatives and strategies, not independent IT projects.

Marriott evaluates IT-involved business projects using standard business proposal criteria, such as ROI.

Projects at Marriott are categorized as 'must-do', 'should-do', or 'nice-to-do' with each having varying priority and importance.

CIOs prioritize and manage projects to align with the areas of the business that create the most value for the company.

IT is involved with business projects in a supporting role to enable those projects, not as separate IT endeavors.

CIO uses service levels, costs, and productivity metrics to measure the success of business operations support.

Traditional IT projects typically take the form of infrastructure upgrades which can reduce operational expenses or improve functioning; these projects must demonstrate a clear business case.

A software development approach that emphasizes flexibility, speed, and customer feedback.

A sequential software development approach where each phase must be completed before the next begins.

Converting to agile development can be difficult as it often requires a major cultural shift for the development team.

Agile methods work well with short development times, allowing for adjustment based on specific delivery dates.

Predicting the schedule of waterfall projects is difficult as design and implementation are done later in the process.

Techniques used in software development to quickly produce systems by moving key design aspects earlier in the project.

Agile development benefits from immediate, ongoing user feedback, making schedule visibility easier.

In agile methods projects, functionality can be removed under development to adjust to schedule slippage.

Predicting how long a project will take, considering planning, analysis, design, and implementation phases.

The amount of time spent in the planning phase can be used to estimate the overall project time.

Commonly accepted percentages for time allocation in different SDLC phases (e.g., 15% planning, 20% analysis).

The actual time needed for each phase can vary based on a project's unique characteristics.

Tracking actual time and effort during the SDLC can improve future project estimates.

Using data from previous projects with similar tasks and technologies to estimate time.

Estimating project time with a safety margin to account for potential delays or unforeseen issues.

Consulting firms often have established methodologies and estimates based on their experience with similar projects.

A hierarchical list of tasks needed for a project, breaking down large goals into smaller, manageable steps.

A table that organizes and manages project tasks with details like task durations, statuses, dependencies, and assigned team members.

Relationships between tasks where one task cannot begin until another is completed.

Important dates or deadlines on the work plan that mark significant progress points in the project.

The project work plan, which is used to monitor progress, identify issues, and make necessary adjustments.

A hierarchical structure that breaks down a project into smaller, manageable tasks. It defines the scope of the project and helps track progress.

A unique identifier assigned to each task within a project.

A descriptive title that clearly identifies what the task involves.

The estimated time required to complete a task, measured in days.

A relationship between tasks where one task cannot start before another is finished.

The current state of a task, indicating whether it is open, in progress, or completed.

A task that has not yet been started.

A WBS offers several benefits, including:

• Clear Scope: Defines the project's boundaries and prevents scope creep.
• Task Management: Breaks down complex projects into manageable pieces.
• Progress Tracking: Tracks the completion of individual tasks and overall project progress.
• Resource Allocation: Helps plan resource allocation and monitor costs.
• Communication: Facilitates clear communication among team members.

A WBS aids in project planning by:

• Breaking Down Tasks: Identifies all necessary tasks and sub-tasks within a project.
• Estimating Time: Helps determine the duration of each task and create a realistic project timeline.
• Defining Dependencies: Reveals relationships between tasks, facilitating sequencing and resource allocation.
• Facilitating Communication: Provides a common framework for understanding project scope and progress.

A well-defined and maintained WBS is crucial for project success. It provides a roadmap to guide project execution, ensures efficient allocation of resources, and enables effective monitoring of progress. By breaking down complex projects into manageable components, a WBS assists in better planning, communication, and control, leading to higher chances of achieving project goals and objectives.