Ch 2 - Project Groups and Project Charter Flashcards
What are key elements common to life cycles?
- at highest level life cycle should describe deliverables for each phase
- life cycle should list categories of resources involved
- high-level timeline for the phase might be constructed
- should explain how output of project will be incorporated into org’s operational business upon completion
what are the five process groups?
- initiating
- planning
- executing
- monitor & controlling
- closing
what is the initiating process?
formal authorization for new project to begin or for existin gproject to continue
what number process is the initiating process in the process groups
first
what activities are associated with the initiating process?
- original process request
- identifying the project
- documenting business justification
- performing business validation
- using project selection methods
- document high-level requirements definitions
- perform cost justification
what is the purpose of initiating a project
to obtain commitment to start the project
what is typically the first step in initiating a project
assigning a project mgr (may be done after the project is approved)
what are the general steps in initiating a project?
- assign project mgr
- identify problem
- define project
- prepare project charter
what is the planning process?
- where the project goals, objectives and deliverables are refined and broken down into manageable units of work
- PM’s create time and cost estimates to determine resource requirements for each activity
what critical areas of project mgmt are included in planning process (5)
- communication
- risk
- HR
- quality
- procurement
what is the executing process
where the work of the project is performed
what is monitoring and controlling processes (3)
- activities that monitor the progress of the project to identify any variances from project plan
- requests for changes handled
- corrective actions taken to get work of project realigned to project plan
- scope control
- cost control
- schedule control
- quality control
- performance reporting
- risk control
what is the primary purpose of the closing process? (2)
document the formal acceptance of project work
2. hand off completed product to org for ongoing maintenance and support
what activities are included in the closing process
- sign-off
- archive of project documents
- turnover to maintenance group
- release of project team members
- review lessons learned
What are the next steps in initiating process, after receiving the request?
- meeting w/requester to clarify and further define project needs
- identify functional and technical requirements
- document high-level requirements
What does the high-level requirements/product description document explain?
major characteristics of product or service of project
2. describes relationship between business need and product/service requested
What are the three types of requirements that need to be identified in the initiating process?
- functional
- business
- technical
what is a functional requirement
defines what the product/service/result of the project will do; how the end user will interact with the product
what is a business requirement
big-picture result of fulfilling a project; anything from planned increase in revenue to decrease in overall spending to increased market awareness
what are technical requirements
(non functional requirements), the product characteristics needed for the product to perform the functional requirements
what are some examples of technical requirements
- usability requirements
- maintainability requirements
- legal requirements
- performance requirements
- operational requirements
- security requirements
Is the high-level requirements document part of the formal request for project approval or planning process?
project approval
In what aspects is the high-level requirements document a basis?
- part of formal request for project approval
- defining project scope
- estimating cost of project
- identifying resources required
- developing the schedule
what information should be included in the high-level requirements document
- problem statement
- objectives
- strategic value
- requirements
- timing
- historical data
what info should be included in the problem statement in the high-level requirements document? (2)
- what issue/problem generated this request
2. what is specific business need that the client wants to address
what info should be included in the objectives section in the high-level requirements document? (5)
- how do you define project success
- what is end result
- what are deliverables leading to end result
- what are the goals
- how are goals measure
What info should be included in the strategic value section in the high-level requirements document? (2)
- how does this product fit the strategic vision of the corp?
- is there a link to other proposed or ongoing projects?
What should be included in the requirements section in the high-level requirements document? (4)
- what work functions are required
- are there interfaces to existing systems
- what are the performance criteria
- what are the support requirements
what info should be included in timing section in the high-level requirements document? (4)
- when does the customer need the project completed
- are there market windows involved
- are there significant business expenses to be incurred if the project is not complete
- is there an impact to corp revenue if the project is delayed
what info should be included in the historical info section in the high-level requirements document? (3)
- have there been similar projects in the past
- were they successful
- can pieces of previous projects be reused for this project
What are 4 the steps in decompostion?
take the requirements initially given to you and examine every facet of them until their meaning is clear.
make determination as to whether requirement is functional, business, or technical in nature.
then break down further the requirements during Planning processes into small units of work or activities.
state requirements in clear and concise terms so there’s no misunderstanding
