Tools & Techniques Descriptions (1 of Each) Flashcards
Expert Judgment
Expertise which may come from individuals with experience, knowledge, skills, and/or training and can be from the company, consultants, PMO, SMEs, Industry Groups, etc. Technical and management expertise may be required in developing documents. Expert Judgment is a tool and technique for every Integration Process.
Used as a T&T in:
- Develop Project Charter
- Develop Project Management Plan
- Direct & Manage Project Work
- Monitor & Control Project Work
- Perform Integrated change Control
- Close Project or Phase
- Plan Scope Management
- Define Scope
- Create WBS
- Plan Schedule Management
- Define Activities
- Estimate Activity Resources
- Estimate Activity Durations
- Plan Cost Management
- Estimate Costs
- Determine Budget
- Plan HR Management
- Control Communications
- Plan Risk Management
- Identify Risks
- Perform Qualitative Risk Analysis
- Perform Quantitative Risk Analysis
- Plan Risk Responses
- Plan Procurement Management
- Conduct Procurements
- Identify Stakeholders
- Plan Stakeholder Management
- Control Stakeholder Engagement
Facilitation Techniques
Brainstorming, conflict resolution, problem solving, and meeting management techniques.
Used as a T&T in:
- Develop Project Charter
- Develop Project Management Plan
Stakeholder Analysis
A technique used to identify the stakeholders, and their interest, experience and influence on the project.
Used as a T&T in:
- Identify Stakeholders
Meetings
Special meetings called Profile Analysis Meetings can be used to develop an understanding of roles, interested, knowledge, and the overall position of Project stakeholders, especially major stakeholders.
Used as a T&T in:
- Direct & Manage Project Work
- Monitor & Control Project Work
- Perform Integrated Change Control
- Close Project or Phase
- Plan Scope Management
- Plan Schedule Management
- Plan Cost Management
- Plan Quality Management
- Plan HR Management
- Plan Communication Management
- Control Communications
- Plan Risk Management
- Control Risk
- Plan Procurement Management
- Identify Stakeholders
- Plan Stakeholder Management
- Control Stakeholder Engagement
Questionnaires & Surveys
Used to quickly gather information from a large number of participants.
Used as a T&T in:
- Collect Requirements
Prototypes
A common technique for soliciting requirements by making a working model (usually on a smaller scale), of the end product. A prototype helps customers visualize their end product and provide early feedback. It also helps reduce the risks on the project.
Used as a T&T in:
- Collect Requirements
Observations
This technique, also called “job shadowing”, involves “watching over the shoulder” of end-users (of the proposed product) to see how they perform their tasks. It is used to uncover “hidden” requirements, which the users may not be able to articulate themselves.
Uses as a T&T in:
- Collect Requirements
Interviews
A formal or informal approach to seek information from the stakeholders by talking to them directly. Interviewing stakeholders, and subject matter experts can help in identifying and defining the features and functions of the project deliverables.
Used as a T&T in:
- Collect Requirements
Group Decision-Making Techniques
Used to assess various alternatives. The objective is to classify and prioritize (low, medium, high) requirements. There are multiple methods of reaching a group decision, such as Unanimity, Majority, Plurality, and Dictatorship.
Used as a T&T in:
- Collect Requirements
- Validate Scope
- Estimate Activity Durations
- Estimate Costs
Group Creativity Techniques
Used to collect project and product requirements via Brainstorming, Nominal Group Technique, Mind Mapping, Affinity Diagram, and Multi-criteria decision analysis.
Used as a T&T in:
- Collect Requirements
Focus Groups
Meeting that bring together dry stakeholders and subject matter experts to learn about their expectations and attitudes about a proposed product, service, or result. They are conducted by trained moderators.
Used as a T&T in:
- Collect Requirements
Facilitated Workshops
Bring key stakeholders together for defining cross-functional requirements and reconciling stakeholder differences. Examples include Joint Application Development (JAD) in software development, Quality Functional Deployment (QFD) in manufacturing.
Used as a T&T in:
- Collect Requirements
- Define Scope
Document Analysis
Gathering requirements by analyzing business plans, marketing material, agreements, RFP, business rules, business processes, use cases, problem/issue logs, policies, procedures, and regulatory documentation.
Used as a T&T in:
- Collect Requirements
Context Diagrams
Help stakeholders visualize the product scope by showing the interaction between a business system (process, equipment, computer system, etc.), with people and other systems.
Used as a T&T in:
- Collect Requirements
Benchmarking
Comparing the current project’s processes to those of other comparable projects (within or outside the organization) order to identify best practices, generate ideas for improvement, and provide a basis for measuring performance.
Used as a T&T in:
- Collect Requirements
- Plan Quality Management
Product Analysis
Translates high-level product descriptions into tangible deliverables. Project Deliverables are a art of the Project Scope Statement, which is an outp of Define Scope process. Product analysis includes techniques such as Product Breakdown, Systems Analysis, Requirements Analysis, Systems Engineering, Value Engineering, and Value Analysis.
Used as a T&T in:
- Define Scope
Alternatives Generation
A technique to identify different approaches to perform the work of the project. Brainstorming and Lateral Thinking are commonly used to identify alternatives.
Used as a T&T in:
- Define Scope
Decomposition
Th technique of breaking down a very laager project into manageable components.
Used as a T&T in:
- Create WBS
- Define Activities
Analytical Techniques
Various techniques such as rolling wave planning, leads and lags, alternative analysis, and methods for reviewing schedule performance may be employed. Techniques such as payback period, return on investment, internal rate of return, discounted cash flow, and net present value, may be used for making funding decisions (self-funding, funding with equity, or funding with debt) and financing project resources (making, purchasing, renting, or leasing).
Used in:
- Plan Schedule Management
- Plan Cost Management
- Plan Risk Management
- Plan Stakeholder Management
- Conduct Procurements
- Monitor & Control Project Work
- Close Project or Phase
Rolling Wave Planning
In the beginning of the project when requirements and scope are not well defined, the activities are defined in detail for the work to be done in near term, and defined at a high level for the work to be done in future. As requirements and scope become clear, the work packages are decomposed further. This technique is known as Rolling Wave Planning.
Used in:
- Define Activities
Dependency Determination
All types of dependencies - Mandatory, Discretionary, External, and Internal - meet to be considered when sequencing activities.
Leads & Lags
Refinements applied during network analysis and activities to develop/create a viable schedule and a viable project schedule network diagram.
Example of Lead: User Documentation can start 2 weeks before schooled completion of testing.
Example of Lag: The successor activity must wait 3 days after pouring of the concrete to allow the concrete to set.
Precedence Diagramming Method (PDM)
A method used in Critical Path Methodology (CPM) for developing a project schedule network diagram. It uses boxes or rectangles, referred to as nodes, to represent activities, and connects them with arrows that represent the logical relationships between activities.
Alternatives Analysis
Alternative ways to accomplish an activity. For example, two less experienced resources could be used to accomplish a task instead of an experienced resource. An activity could be automated by using a tool instead of being performed manually, in order to expedite work. Some components could be purchased instead of being manufactured in-house.
Bottom-Up Estimating
An estimating technique in which complex activities are broken down into smaller and more manageable activities. Resource requirements are determined for these smaller activities and then aggregated or “rolled-up” to determine the resource requirements for the entire activity.
Used in:
- Estimate Activity Resources
- Estimate Costs
Project Management Software
Such as a scheduling tool (e.g. MS Project) can help to plan, organize, and manage resource pools and develop resource estimates.
Used in:
- Estimate Activity Resources
- Control Schedule
- Estimate Costs
- Control Costs
Published Estimating Data
Production rates and unit costs for resource, equipment and supplies for different regions can be used to estimate activity resource requirements. Such information could be optioned from publicly available databases.
Used in:
- Estimate Activity Resources
Analogous Estimating
An estimating technique that uses information from a previous, similar activity as the basis for estimating a future activity. For example, a similar project done in the past took 5 months to complete. so, the current project, which is slightly more complex, should take about 6 months.
Used in:
- Estimate Activity Durations
- Estimate Costs
Critical Chain Method
A schedule network analysis technique that modifies the project schedule to account for limited resources and project uncertainties. It is developed from the critical path method. The resource-constrained critical path is known as the critical chain.
Used in:
- Develop Schedule
Critical Path Method
A schedule network analysis technique used to determine the minimum project duration by analyzing the amount of float on various paths in the project schedule network.
Used in:
- Develop Schedule
Modeling Techniques
A technique used to develop and control project schedule by assessing the feasibility of project schedule under various scenarios. It works by asking questions such as “what if scenario X happens?”. Monte Carlo Analysis is commonly used to conduct “What if” analysis.
Used in:
- Develop Schedule
- Control Schedule
Resource Optimization Techniques
Techniques such as Resource Leveling and Resource Smoothing are used to produce a resource-limited schedule. These techniques alter the project schedule to reduce the extreme variations in resource usage, and achieve a more stable usage over the course of the project.
Used in:
- Develop Schedule
- Control Schedule
Schedule Compression
It is the shortening of the project schedule duration without reducing the project scope. Commonly used schedule compression techniques include Crashing and Fast-tracking.
Used in:
- Develop Schedule
- Control Schedule
Schedule Network Analysis
This technique generates the project schedule model. It identifies early and late start dates, as well as early and late finish dates, for the uncompleted portions of project schedule activities.
Used in:
- Develop Schedule
Scheduling Tool
Schedule tools such as MS Project can expedite the process of schedule development.
Used in:
- Develop Schedule
- Control Schedule
Cost of Quality
The total cost of all quality related if forts throughout the product life cycle. It includes prevention and appraisal costs (cost of conformance), and failure costs (cost of non-conformatnce).
Used in:
- Estimate Costs
- Plan Quality Management
Parametric Estimating
An estimating technique that uses a statistical relationship established based on historical data, to calculate an etiolate project cost, budget, or duration. For example it costs $100K to build one apartment unit. So, it should cost about $10M to construct a complex with 100 units.
Used in:
- Estimate Activity Durations
- Estimate Costs
Reserve Analysis
An analytical technique to establish a contingency (or buffer) for project duration or budget to mitigate schedule or cost risks. Contingency reserves account for “known-unknowns” in the project. The reserve is calculated either as a fixed number (e.g. $50K), or a percentage (e.g. 10%) of total project cost.
Used in:
- Control Costs
- Control Risks
- Determine Budget
- Estimate Activity Durations
- Estimate Costs
Three-Point Estimating
An estimating technique that uses three cost or duration estimates (optimistic, most likely, and pessimistic) to account for risk or uncertainty involved in an activity.
Used in:
- Estimate Activity Duration
- Estimate Costs
Vendor Bid Analysis
The bids from various vendors are compared to estimate total project cost. Separate bids may be invaded for different deliverables. Costs are estimated for all the deliverables in order to determine the total project cost.
Used in:
- Estimate Costs
Cost Aggregation
The individual cost estimates of activities in the WBS are aggregated to get the cost estimates by work package. Cost estimates by work packages are aggregated to get cost estimates by Control Account. Finally, cost estimates by Control Account are rolled up to determine the total project cost.
Used in:
-Determine Budget
Funding Limit Reconciliation
In this technique, the funding available in each time period (say each month) is compared with the planned expenditure in the time period to ensure that the planned expenditure is within the available funding. For example, if the planned expenditure in a given month is more than the funding available in that month, then the work in that month may have to be rescheduled to another month when more funds are available.
Used in:
- Determine Budget
Historical Relationships
Knowledge gained from past experience can be translated into mathematical models to predict the total project cost. For example, cost for a construction project can be calculated by using cost per sq. ft. rather than using bottom-up estimating.
Used in:
- Determine Budget
Additional Quality Planning Tools
These include Brainstorming, Force field analysis, Nominal group techniques, and other quality management and control tools such as Affinity diagrams, PDPC, Tree diagrams, Matrix diagrams, Prioritization matrices, etc.
Used in:
- Plan Quality Management
Cost-Benefit Analysis
It compares the cost of quality activities with the expected benefit. For example, if a quality improvement activity cots $10,000 and results in only a marginal increase in quality, then it’s probably not worth doing.
Used in:
- Plan Quality Management
Design of Experiments
Is a statistical approach that helps to determine the factors that have the most impact on quality. Ex) Lets say a company wants to optimize its e-commerce portal to generate maximum revenue. One way is to change one element of the web site at a time, try it out for a week , and analyze its impact on revenue. A more efficient and faster way is to use DOE and change a combination of elements at the same time to determine the best layout. DOE is used during the
Plan Quality Management process to determine the number and type of tests to be used and their impact on cost of quality.
Used in:
- Plan Quality Management
Seven Basic Quality Tools
Seven Basic Quality Tools are:
- Cause-and-Effect Diagrams
- Flowcharts
- Checksheets
- Pareto Diagrams
- Histograms
- Control Charts
- Scatter Diagrams
Used in:
- Plan Quality Management
- Control Quality