Module 7: Predictive Approaches Flashcards
Questions for a Predictive approach
@ Are the requirements stable?
@ Will the customer not be able to provide feedback during development?
@ Is a single point of delivery possible with limited refinements?
@ Is the development and delivery process well understood with low risk of change?
@ Would incremental delivery and feedback be difficult to arrange?
Agile suitability filter assessment tool
A wheel that assists in choosing a project management approach. It assesses based on…
Team - team size, experience, access
Culture - buy-in, trust, decision-making
Project - changes, criticality, delivery
Process Groups in Predictive Approach
Initiating - defining the new project, authorization for a project
Planning - establish scope, objectives, and develop plan of action
Executing - completing the work outlined
Monitoring & Controlling - tracking, reviewing, and regulating progress and performance
Closing - closing out project, phase, or contract
Factors to Consider (Tailoring a Predictive Approach)
Product/Deliverable
Project Team
Org Culture
Product/Deliverable Factors (Tailoring a Predictive Approach)
Compliance/Criticality - how much quality assurance (documentation, testing, etc)?
Type of Product/Deliverable - physical (subject to less change) or intangible (subject to more change)?
Industry/Market - changing or regulated market?
Technology - well established or rapidly changing?
Timeframe - short vs long duration?
Stability of Requirements - subject to change?
Security - is confidentiality needed?
Incremental Delivery - repeated check-ins or not until end of project?
Project Team (Tailoring a Predictive Approach)
Project Size - # of people, part time vs full time
Project Team Geography - where are team members located?
Org Distribution - where are stakeholders located?
Project Team Experience - team member experience amount
Access to Customers - can we get customer feedback?
Organization Culture (Tailoring a Predictive Approach)
Buy-In - acceptance & support for project?
Trust - high levels of trust and commitment on the team?
Empowerment - is the team trusted, supported, and encouraged?
Org Culture - do org values align with the project?
Project Charter
A document issued by the project initiator/sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities
Provides a high level description of the project’s who, what, when, where, why, and how
Project Charter Template
Introduction
Problem Statement
Scope Outline
Definition of Success
Risk Summary
Constraints and Assumptions
Business Cases
Schedule
Deliverables Schedule
Budget
Team Structure
Organizational Structure
Project Approach
Steering Committee Decision
Resource Planning includes…
Team members
Supplies
Materials
Equipment
Services
Facilities
Resource Calendar
A calendar identifying the working days, shifts, start, and end of normal business hours, weekends, and public holidays when each specific resource is available
Resource Management Plan
Guides how project resources should be categorized, allocated, manage, and eventually released
Phases of Team Development
Forming
Storming
Norming
Performing
Adjourning
Procurement Management
The process of acquiring goods and services from external resources to meet a project/organization’s needs
Procurement Contract
A mutually binding agreement that obligates the seller to provide specific products and services in exchange for compensation in return
Fixed-Price Contract
(aka Lump Sum Contract)
A contract where the price is set and agreed upon upfront, regardless of actual costs
Used when there is a well-defined scope and requirements
Seller has the greatest risk
Cost-Plus Contract
A contract where the buyer agreed to reimburse the seller for actual costs incurred plus an additional fee for profit
Best for projects where scope and costs are uncertain
Buyer has the greatest risk
Time and Materials Contract
A contract where the buyer pays for actual labor hours (time) and the materials used
Best for projects with uncertain scope or when quick hiring is needed
Buyer has the greatest risk
Bid Document
A formal document to solicit offers from vendors/contractors for goods, services, or projects. Can provide details about the requirements, scope, and evaluation criteria.
Request for Information (Bid Document)
Used to gather general information from vendors related to the product, service, or seller capability
Request for Proposal (Bid Document)
Used when a buyer needs a customized or recommended solution and vendors must submit detailed proposals on how they will meet the requirements
Request for Quotation (Bid Document)
Used when the buyer knows exactly what they need and is primarily looking for pricing information
Statement of Work (SOW) (Bid Document)
Defines the scope, deliverables, and expectations for a project between a company and a vendor, contractor, or service provider
Project Management Plan
A document that describes how the project will be executed, monitored & controlled, and closed