Commonly Confused Concepts Flashcards
Crashing vs Fast tracking
In Crashing, schedule is compressed by applying additional resources, working overtime, etc. Whereas in Fast tracking, activities which are usually performed in sequence are performed in parallel, to compress the schedule.
Code of Account vs Chart of Account
Code of Account is any numbering system used to uniquely identify each component of the WBS, whereas Chart of Account is any numbering system used to monitor project costs by category.
Project Schedule vs Schedule Baseline
Project Schedule is the “actual” schedule progress of the project whereas Schedule Baseline is the “planned and approved” version of the project schedule. Schedule variance is measured by comparing the (actual) Project Schedule with the Schedule Baseline.
Validate Scope vs Control Quality
Scope validation differs from quality control in that scope validation is primarily concerned with acceptance of the deliverables, while quality control is primarily concerned with correctness of the deliverables and meeting the quality requirements specified for the deliverables. Quality control is generally performed before scope validation but the two can be performed in parallel as well.
Work Performance Data (WPD) vs Work Performance Information (WPI)
WPD are the raw observations or measurements gathered as work on the project is carried out (e.g. percent completion, quality/technical performance measures, activity start/finish dates, no. of change requests/defects, actual costs/durations, etc.) WPD is processed and analyzed to generate WPI (e.g. status of deliverables/change requests, forecasts, EV measures - SV, CV, SPI, CPI, etc.).
Progressive Elaboration vs Rolling Wave Planning
Rolling Wave Planning is a form of Progressive Elaboration.
Progressive Elaboration vs Prototyping
Prototyping is a form of Progressive Elaboration.
Weighted Average (PERT) vs Simple Average Three-Point Estimating
Weighted Average (PERT) estimate uses Beta distribution whereas Simple Average uses Triangular distribution to calculate the duration or cost estimate. Weighted Average formula is, E = (O + 4M + P) / 6 and Simple Average formula is E = (O + M + P) / 3, where O is the Optimistic, M is the Most Likely and P is the Pessimistic estimate.
Total Float vs Free Float
Total Float is the amount of time an activity can be delayed without delaying the project, whereas Free Float is the amount of time an activity can be delayed without delaying any successor activity.
Duration vs Effort
Duration is the number of work periods (not including holidays or other non-working periods) required to complete an activity, whereas Effort is the number of labor units required to complete an activity. Duration is expressed as work days, work weeks, etc., whereas Effort is expressed as man hours, man days, man weeks, etc.
Duration vs Elapsed Time
Duration is the number of work periods (not including holidays or other non-working periods) required to complete an activity, whereas Elapsed Time includes holidays and non-working periods also. Both are expressed as work days, work weeks, etc.
Project Team vs Project Management Team
A Project Team is comprised of the project manager, project management team, and other team members. Project Management Team includes a subset of Project Team members who are directly involved in project management activities.
Padding vs Buffer (or Reserve)
Padding is the amount of unreasonable extra time added to the estimate, just to feel confident with the estimate. Buffer is the extra time added to the estimate to account for uncertainty or risk. Buffer is clearly identified in schedule documentation whereas padding is hidden.
Lead vs Lag
Lead is the acceleration of a successor activity, whereas Lag is the delay of a successor activity.
Code of Account vs Control Account
Code of Account is any numbering system used to uniquely identify each component of the WBS. Control Account is a management control point where scope, budget, actual cost, and schedule are integrated and compared to earned value for performance measurement. Control Accounts are strategically placed at various points on the WBS.
Control Account vs Work Package
Control Account is a management control point in the WBS where Earned Value measurements take place. Work package is a unit of work or deliverable at the lowest level of each branch on the WBS. A Control Account may contain multiple Work Packages, but a Work Package can only be associated to one Control Account.
Planning Package vs Control Account
Planning Package is a logical group of work within a Control Account that is identified and budgeted in early planning, but is not yet sub-divided into Work Packages. Control Account is a management control point in the WBS where Earned Value measurements take place. The Planning Package is below the Control Account, but above the Work Packages in the WBS.
Planning Package vs Work Package
Planning Package is a logical group of work within a Control Account that is identified and budgeted in early planning, but is not yet sub-divided into Work Packages. Work Package is a unit of work at the lowest level of each branch of the WBS. The Planning Package is below the Control Account, but above the Work Packages in the WBS.
Contingency Reserve vs Management Reserve
Contingency Reserve accounts for “known-unknowns” or simply “knowns”. It covers the “residual risks” on the project. Management Reserve accounts for “unknown-unknowns” or simply “unknowns”.
Manage Quality vs Control Quality
Manage Quality checks whether quality standards are being followed, whereas Control Quality checks whether quality standards are being met. Audits and root cause analysis are examples of Manage Quality. Peer reviews and testing are examples of Control Quality. In Manage Quality think about “process”, and in Control Quality think about “deliverables”.
Quality vs Grade
Quality is the degree to which a deliverable meets the requirements. Grade is a category assigned to a product or a service that has the same functional use but different technical characteristics. For example, a software application may be of good quality (no defects, good performance, etc.), but low grade (limited features). Low grade may not be a problem, but low quality is almost always a problem.
Product Quality vs Project Quality
Product Quality focuses on the quality of the “product” of the project. It is measured in terms of the degree to which the product conforms to customer’s requirements. Whereas, Project Quality focuses on the quality of “project management processes”. It is measured in terms of the degree to which the project meets its objectives (scope, time, cost, customer satisfaction, etc.).
Product Scope vs Project Scope
Product Scope refers to requirements that specifically relate to the “product” of the Project. Project Scope is all the “work” that goes in to producing the project deliverables (products, services or results).
Requirements vs Product Scope
Requirements are “what” the customer needs. Requirements can be of many types. For example, product related requirements, performance requirements, quality requirements, project management requirements, etc. Whereas, Product Scope refers to requirements that specifically relate to the “product” of the project.
Precision vs Accuracy
Precision means that values have very little scatter (very close to each other). Accuracy means that values are very close to the true value. Precise values may not be accurate and vice versa. E.g., if your office starts at 8 am and you reach at 8:30 am sharp every day, you are precise, but not accurate. Whereas, if you reach between 7:45-8:15 am every day, you are more accurate, but less precise.
Verified Deliverable vs Accepted Deliverable
Verified deliverables are the deliverables that have been checked for correctness by the Control Quality process. They are an input to Validate Scope process. Accepted Deliverables are the deliverables that meet the acceptance criteria and have been formally signed off by the customer through the Validate Scope process.
Estimate vs Budget
Estimate is a quantitative assessment of the likely amount or outcome. It is usually applied to project costs, resources, effort, and durations. An “approved” cost estimate for a project or a work component is known as Budget.
Estimate At Completion (EAC) vs Estimate to Complete (ETC)
EAC is the expected total cost of the project or work component, whereas ETC is the expected cost of the “remaining” work. Note that both are “forecasts”.
Internal Failure vs External Failure
Internal Failure is the failure found by the project and External Failure is the failure found by the customer.
Specification Limits vs Control Limits
Specification Limits are set by the customers, whereas Control Limits are set by the project manager and appropriate stakeholders based on the organization’s quality standards. Control Limits are usually stricter than and within the Specification Limits.
Prevention vs Inspection
Prevention keeps errors out of the process, whereas Inspection keeps errors out of the hands of the customer.
Attribute Sampling vs Variable Sampling
In Attribute Sampling, data is in the “attribute” form, and the result either conforms or does not conform. In Variable Sampling, data is in the “variable” form, and the result is rated on a continuous scale that measures the degree of conformity. For example, whether a car starts in first attempt or not is Attribute Data, but the mileage of the car per liter of gasoline is Variable Data.
Tolerance vs Control Limits
Tolerances are used to determine whether individual components are acceptable, whereas Control Limits are used to control the process. Control Limits usually fall within Tolerance Limits.
Common Cause vs Special Cause
Common Cause is a source of variation that is inherent in the system and predictable, whereas Special Cause is not inherent in the system, and is unpredictable and intermittent. On a control chart, Common Cause appears as random data points within the control limits, whereas Special Cause appears as data points outside the control limits or non-random points within the control limits.
Histogram vs Pareto Diagram
A Pareto Diagram is a specific type of Histogram, ordered by frequency of occurrence. It shows how many defects were generated by type or category of the identified cause, and helps the project team focus on the causes creating the greatest number of defects.
Quality Audit vs Inspection
Quality Audit is a structured review of the project to determine whether it’s complying with policies, processes and procedures. Inspection is the process to check whether deliverables conform to standards. Audit is a QA function, whereas Inspection is a QC function. Audit is not just about finding problems, but also good practices of the project. Inspection is mostly for finding problems.
Responsibility Assignment Matrix (RAM) vs Responsible, Accountable, Consult, And Inform (RACI)
The RACI is just one type of RAM.
Authority vs Responsibility
Authority is the “right” to do something, whereas Responsibility is the “obligation” to do something.
Responsibility vs Accountability
Responsibility is the “obligation” to do something. Whereas, Accountability is the acceptance of success and failure. Responsibility can be delegated to some extent, but Accountability cannot.
Team Performance Assessments vs Project Performance Appraisals
Team Performance Assessments are the assessments of the entire team’s performance. They are measured in terms such as on-time, on-budget, etc. Project Performance Appraisals are the appraisals of individual project team members’ performance.
Tool vs Technique
A Tool is something tangible, like a template or a software program, that is used to perform an activity to produce a deliverable. Technique is a procedure performed by a human to perform an activity to produce a deliverable. A Technique may employ many Tools.
Residual Risks vs Secondary Risks
The risks that remain after risk responses have been implemented are called Residual Risks. New risks that emerge as a result of applying risk response strategies are called Secondary Risks.
Threat vs Opportunity
Threat (or negative risk) is a risk of a loss, whereas Opportunity (or positive risk) is a risk of a gain.
Avoid vs Mitigate
Avoid is to eliminate the threat entirely, whereas Mitigate is to reduce the probability of occurrence or the impact of the threat.