Chapter 2 Flashcards
(31 cards)
1
Q
Initiating (processes)
A
- formal acknowledgment that the project should begin.
* primary result of this process Project Charter
2
Q
Planning (processes)
A
- the process group where the project plans are developed that w/b used throughout the project to direct, monitor, & control work results.
- primary result of this process Project Plan
3
Q
Executing
A
- processes are where the work of the project is performed.
4
Q
Project life cycle & process groups:
A
- most projects are divided into phases that consist at a minimum of a beginning phase, middle phase, & ending phase.
5
Q
Project Process Groups
A
- Initiating (pre-project setup)
- Planning
- Executing
- Controlling (monitoring)
- Closing
6
Q
Project Life Cycle
A
- is the total composition of these multiple phases.
7
Q
Deliverable
A
- is an output or result that must be completed & approved before moving to the next phase of the project.
8
Q
Fast Tracking
A
- where you start the next project phase before the prior phase has completed.
9
Q
Monitoring & Controlling
A
- this project process group is where activities are performed to monitor the progress of the project
- determine variances from the project plan
*Corrective actions taken during this process
10
Q
Monitoring & Controlling Processes
A
- Scope control
- Cost control
- Schedule control
- Quality control
- Performance reporting
- Risk control
11
Q
Closing
A
- processes is to document the formal acceptance of the project work
- hand off the completed product to the organization
*operational units raw hands-off
12
Q
Closing Processes
A
- Sign-off
- Archive of project documents
- Turnover to maintenance group
- Release of project team members
- review of lessons learned
13
Q
Project Request Process
A
- can be formal (written) or informal (drive-bys)
14
Q
High-level Requirements/product description
A
- explains the major characteristics of the product
- describes the relationship b/t business need & the product
*need both functional requirements & technical requirements
15
Q
Functional Requirements
A
- define what the product service, or result of the project will do
- focuses on how the end user will interact w/the product
16
Q
Technical Requirements
A
- the product characteristics needed, for the product to perform the functional requirements.
- AKA nonfunctional requirements
17
Q
Stakeholder
A
- a person or organization that has something to gain/lose as a result of performing the project
- are key to project success
18
Q
Sponsor
A
- usually an executive of the organization who has the authority to assign money & resources to the project.
- may serve as project champion
- An advisor to the project manager
- acts as tie-breaker
19
Q
Sponsor (typical) Responsabilities
A
- provide or obtain financial resources
- authorize assignment of human resources to the project
- assign the project manager & state their level of authority
- serve as financial decision maker for all project issues
- negotiate support from key stakeholders
- monitor delivery of major milestones
- run interference & removed roadblocks
- provide political coaching to the project manager
20
Q
Project Champion
A
- Usually key stakeholder
- Spread news about the benefits of the project
- cheerleader
21
Q
Enterprise
A
- Complete array of business units
22
Q
Project Charter
A
- document provides formal approval for the project to begin & authorizes the project manager to apply resources to the project.
23
Q
Project Sponsor
A
- authorizes & approves the project charter.
24
Q
Triple Constraint
A
- Time
- Budget
- Scope
- all of which affect quality
25
Assumptions
- events, actions, concepts, or ideas you believe to be true.
26
Customer
- Recipient of the product or service created by the project.
27
Decompose
- Break down project requirements into manageable units of work.
28
End User
- Person who directly uses the product produced as a result of an IT project.
29
Project Description
- Documents the key characteristics of the product, service, or result that will be created by the project.
30
Request for Proposal (RFP)
- Procurement document that is advertised to the vendor community requesting vendors provide a written proposal outlining how they will meet the requirements of the project and how much it will cost.
* vendor bids
31
Statement of Work (SOW)
- Description of what product or service the vendor will provide
- generally included as part of contract
*vendor bids
