Chapter 2 Project Planning and Management Flashcards

1
Q

Situation Scenarios when Defining the Project?

A
  1. Demand from a lone business zealot
  2. Too Much Demand
    3.In Search of Demand
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Demand From a lone business Zealot

A

One business exec has a vision about getting better access to better info for better decision support

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Too Much Demand

A

Multiple business executives are voicing a need for better information
Need to prioritize the requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

In search of Demand

A

Can be viewed as demand from a CIO
By Far the most challenging scenario to deal with

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

2 Things before beginning a data warehouse of data mart project

A

-Understand whether there is demand and where that demand is coming from
-have strong business sponsor and eager users

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

5 Key factors to establish the foundation to ensure a successful DW?

A
  1. Strong Business Sponsors
    2.Compelling Business Motivation
  2. IS/Business partnership
    4.Current Analytical Culture
  3. Feasibility
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Strong Business Management Sponsors

A

-Influential Leader in organization who are well respected by others
-Sponsors should be strong, realistic and have basic understanding of data warehousing concept

-

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Compelling Business Motivation

A

DW that align with strategic business motivations stand a good chance of succeeding

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

IS/Business Partnershi

A

Successful DW result from a joint business and IS effort in which both groups share responsibility for the initiative

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Current Analytical Culture

A

When business community does not currently place value on information and analyses, it’s readiness is questionable

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Feasibility

A

-refers to tech feasibility
-better shape if the overall infrastructure is already in place
-premary feasibility concern relates to data

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What are techniques to address readiness shortfall

A

-High-level Business requirements analysis
-Business requirements prioritization
-Proof of Concept

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

How to develop a preliminary scope?

A

-Scoping is still a best-guess exercise at this point
-attempt to make as few promises as possible but enough to identify benefits and cost associated with going forward

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Guidelines for developing the preliminary DW project scope

A

-Joint effort by IS and Business representatives
-Initial scope is manageable
-focus on single Business requirement supported by data
-limit users
-establish success criteria

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Scope Refinement

A

Same size, contents may change

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Scope Creep

A

Expand the demensions

17
Q

Building Business Justification

A

-Identify anticipated costs and benefits
-Compare predicted financial return against the predicted investment
-Determine Financial returns and benifits
-Figure out ROI

18
Q

Planing the project

A

-Establishing the Project Identity
-Staffing Project
-Develop the Project Plan

19
Q

Establish the project Identity

A

Project needs a name and/or logo

20
Q

Staff Project

A

-Same staff may fill multiple roles
-Sponsor and Drivers
Project Managers and Leads
-Core Project Team (FT and PT)
-Special Teams
External Consultants

21
Q

Develop Project Plan

A

-Integrated and detailed plan
-Track ( Resources, Original Estimated effort , Start date…)

22
Q

Managing the Project

A
  • Unique Characteristics of data warehouse
    -Project Team Kickoff Meeting
    -Monitor Project Status
    -maintain Project Plan and Project docs
    -manage scope
    -Communications plan to manage expectations
23
Q

Unique Characteristics of DW

A

-Cross-Functional Implementation team
-Iterative development cycle
-Inevitable data issues
-Elevated visibility

24
Q

Project Kickoff meeting

A

Get teh entire project team on the same page in terms of where the project currently stands and where it hope to go.

25
Q

Monitor Project Status

A

Key to achieving coordination between numerous resources and task

26
Q

maintaining project plan and project documentation

A

-integrated project plan should be updated weekly to accurately reflect progress
-project falls behind schedule, have courage to acknowledge to management and sponsors