Chapter 2 Project Planning and Management Flashcards
Situation Scenarios when Defining the Project?
- Demand from a lone business zealot
- Too Much Demand
3.In Search of Demand
Demand From a lone business Zealot
One business exec has a vision about getting better access to better info for better decision support
Too Much Demand
Multiple business executives are voicing a need for better information
Need to prioritize the requirements
In search of Demand
Can be viewed as demand from a CIO
By Far the most challenging scenario to deal with
2 Things before beginning a data warehouse of data mart project
-Understand whether there is demand and where that demand is coming from
-have strong business sponsor and eager users
5 Key factors to establish the foundation to ensure a successful DW?
- Strong Business Sponsors
2.Compelling Business Motivation - IS/Business partnership
4.Current Analytical Culture - Feasibility
Strong Business Management Sponsors
-Influential Leader in organization who are well respected by others
-Sponsors should be strong, realistic and have basic understanding of data warehousing concept
-
Compelling Business Motivation
DW that align with strategic business motivations stand a good chance of succeeding
IS/Business Partnershi
Successful DW result from a joint business and IS effort in which both groups share responsibility for the initiative
Current Analytical Culture
When business community does not currently place value on information and analyses, it’s readiness is questionable
Feasibility
-refers to tech feasibility
-better shape if the overall infrastructure is already in place
-premary feasibility concern relates to data
What are techniques to address readiness shortfall
-High-level Business requirements analysis
-Business requirements prioritization
-Proof of Concept
How to develop a preliminary scope?
-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
Guidelines for developing the preliminary DW project scope
-Joint effort by IS and Business representatives
-Initial scope is manageable
-focus on single Business requirement supported by data
-limit users
-establish success criteria
Scope Refinement
Same size, contents may change
Scope Creep
Expand the demensions
Building Business Justification
-Identify anticipated costs and benefits
-Compare predicted financial return against the predicted investment
-Determine Financial returns and benifits
-Figure out ROI
Planing the project
-Establishing the Project Identity
-Staffing Project
-Develop the Project Plan
Establish the project Identity
Project needs a name and/or logo
Staff Project
-Same staff may fill multiple roles
-Sponsor and Drivers
Project Managers and Leads
-Core Project Team (FT and PT)
-Special Teams
External Consultants
Develop Project Plan
-Integrated and detailed plan
-Track ( Resources, Original Estimated effort , Start date…)
Managing the Project
- 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
Unique Characteristics of DW
-Cross-Functional Implementation team
-Iterative development cycle
-Inevitable data issues
-Elevated visibility
Project Kickoff meeting
Get teh entire project team on the same page in terms of where the project currently stands and where it hope to go.