Controlling Quarter

Controlling Quarter (hereinafter, the Quarter) is the first of four lectures of Operations Quadrivium (hereinafter, the Quadrivium):

• The Quarter is designed to introduce its learners to enterprise discovery, or, in other words, to concepts related to obtaining data needed to administer the enterprise effort; and
• The Quadrivium examines concepts of administering various types of enterprises known as enterprise administration as a whole.

The Quadrivium is the first of seven modules of Septem Artes Administrativi, which is a course designed to introduce its learners to general concepts in business administration, management, and organizational behavior.

Outline

The predecessor lecture is Monitoring Quarter.

Concepts

1. Controlling. Management function that involves comparing actual work performance with planned one, analyzing variances, evaluating possible alternatives, and suggesting appropriate corrective actions as needed.
   • Feedback control. Control that takes place after a work activity is done.
   • Concurrent control. Control that takes place while a work activity is in progress.
   • Feedforward control. Control that takes place before a work activity is done.
2. Control process. A three-step process of measuring actual performance, comparing actual performance against a standard, and taking managerial action to correct deviations or inadequate standards.
   • Variance analysis. Analysis of discrepancies between planned and actual performance, to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.
   • Range of variation. The acceptable parameters of variance between actual performance and the standard.
3. Regulatory compliance.
   • ISO 9000. A series of international quality management standards that set uniform guidelines for processes to entire products conform to customer requirements.
   • Standard.
4. Quality control (QC). 1) Enterprise efforts undertaken in order to monitor specific outputs from specified processes to determine if they comply with requirement specifications, customer expectations, and relevant quality standards and, if they don't, identify ways to eliminate causes of unsatisfactory performance. 2) The organizational unit that is assigned responsibility for quality control.
   • Quality attribute. The subset of nonfunctional requirements that describes properties of the software's operation, development, and deployment (e.g., performance, security, usability, portability, and testability).
5. Quality. The degree to which a set of inherent characteristics fulfills requirements. In other words, quality is the ability of a product to reliably do what it is supposed to do and to satisfy customer expectations.
   • Grade. A category or rank used to distinguish items that have the same functional use (e.g., "hammer"), but do not share the same requirements for quality (e.g., different hammers may need to withstand different amounts of force).
6. Heuristic review. Evaluating a product or a process and documenting usability flaws and other areas for improvement.
   • Customer journey map. an holistic, visual representation of your users’ interactions with your organization when zoomed right out (usually captured on a large canvas). See also: Experience Map
   • Experience map. An experience map is an holistic, visual representation of your users’ interactions with your organization when zoomed right out (usually captured on a large canvas). See also: Customer Journey Map
7. Enterprise information.
   • Information.
8. Content audit. Reviewing and cataloguing an existing repository of content.
   • Analytics. A broad term that encompasses a variety of tools, techniques and processes used for extracting useful information or meaningful patterns from data.
9. Data processing.
   • Controlled processing. A detailed consideration of evidence and information relying on facts, figures, and logic.
   • Automatic processing. A relatively superficial consideration of evidence and information making use of heuristics.
10. Data analysis.
    • Analysis.
    • Analysis paralysis.
    • Data review. Review of capabilities and performance related data to determine its adequacy.
    • Data verification. Verification of data to check its accuracy.
    • Data validation. Validation of data to check its accuracy.
11. Data reliability. The trustworthiness of data; this trustworthiness is a result of analysis of (a) content reliability, (b) source reliability, and (c) data intent.
    • Content reliability.
    • Source reliability.
12. Data intent. Intention or purpose with which data was created.
    • Fact-based data. Data created with the intent to provide its users with facts.
    • Opinion-based data. Data created with the intent to provide its users with opinions.
    • Agenda-based data. Data created with the intent to provide its users with information desired to accommodate one's business goals or agendas.
13. Enterprise analysis.
    • Root cause analysis. Root cause analysis is a structured examination of an identified problem to understand the underlying causes.
    • Fishbone diagram. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem, and the relationships that exist between those causes.
    • Return on investment (ROI). A financial measurement that accesses how profitable investments are. This is calculated by dividing the expected return (profit) by the financial outlay. In other words, ROI is the money an investor gets back as a percentage of the money he or she has invested in a venture. For example, if a venture capitalist invests $2 million for a 20 percent share in a company and that company is bought out for $40 million, the venture capitalist's return is $8 million.
    • "Boiled frog" phenomenon. A perspective on recognizing performance declines that suggests watching out for subtly declining situations.
14. Performance. (1) An act of staging or presenting; (2) The action or process of carrying out or accomplishing an action, task, or function; (3) The combination of effectiveness and efficiency at undertaking an enterprise effort.
    • Organizational performance. A comprehensive review of the original specification, statement of work, scope and contract modifications, with a purpose to avoid pitfalls in future procurements.
    • Contractor performance. A comprehensive review of contractor's technical and cost performance and work delivery schedules.
    • Job analysis. An assessment that defines jobs and the behaviors necessary to perform them.
    • Work-in-progress limit (WIP). refers to work that is currently being developed and not yet ready to be released as a deliverable. For Scrum teams, this would apply to the work being accomplished during a sprint. For Kanban teams, this refers to work that has been pulled from the backlog and is being developed, indicated by cards in the ‘Doing’ or ‘Work-in-Progress’ column of the Kanban task board.
15. Productivity. The amount of goods and services produced divided by the inputs needed to generate that output.
    • Productivity. The combination of the effectiveness and efficiency of an organization.
    • Organizational effectiveness. A measure of how appropriate organizational goals are and how well those goals are being met.
    • Graphic rating scale. An evaluation method in which the evaluator rates performance factors on an incremental scale.
    • Breakeven analysis. A technique for identifying the point at which total revenue is just sufficient to cover total costs.
    • Burn rate. “The rate at which a new company uses up its venture capital to finance overhead before generating positive cash flow from operations. In other words, it’s a measure of negative cash flow.” (Source: Investopedia) When your burn rate increases or revenue falls it is typically time to make decisions on expenses (eg reduce staff).
16. Estimate. An assessment of the likely quantitative result. Usually applied to project costs and durations and should always include some indication of accuracy (e.g., ±x percent). Usually used with a modifier (e.g., preliminary, conceptual, feasibility). Some application areas have specific modifiers that imply particular accuracy ranges (e.g., order-of-magnitude estimate, budget estimate, and definitive estimate in engineering and construction projects).
    • Estimate at completion (EAC). The expected total cost of an activity, a group of activities, or the project when the defined scope of work has been completed. Most techniques for forecasting EAC include some adjustment of the original cost estimate, based on actual project performance to date.
    • Estimate to complete (ETC). The expected additional cost needed to complete an activity, a group of activities, or the project. Most techniques for forecasting ETC include some adjustment to the original estimate, based on project performance to date. Also called "estimated to complete." See also earned value and estimate at completion.
    • Should-cost estimate. An estimate of the cost of a product or service used to provide an assessment of the reasonableness of a prospective contractor's proposed cost.
    • Percent complete (PC). An estimate, expressed as a percent, of the amount of work that has been completed on an activity or a group of activities.
17. Estimation. The process of assigning a quantifiable measure to the amount of workload needed to complete a project or task, in order to determine the duration, effort, or cost required to complete the project or task.
    • Relative estimation. One of several types of estimations Agile teams use to determine the amount of effort needed to complete project tasks. Tasks or user stories are compared against equivalent, previously completed tasks or group of tasks of similar difficulty.
    • Planning poker. A team building exercise or game used to arrive at a group consensus for estimating workload based on the Delphi method.
18. Kaizen. In Japanese, the word means "improvement". This is the philosophy of continuous process improvement using analytical tools and methods.

Methods

1. Peer review. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
   • Walkthrough. A type of peer review in which participants present, discuss, and step through a work product to find errors. Walkthroughs of requirements documentation are used to verify the correctness of requirements. See also structured walkthrough.
   • Structured walkthrough. A structured walkthrough is an organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
2. Earned value management (EVM). A method for integrating scope, schedule, and resources, and for measuring project performance. It compares the amount of work that was planned with what was actually earned with what was actually spent to determine if cost and schedule performance are as planned.
   • Earned value (EV). The physical work accomplished plus the authorized budget for this work. The sum of the approved cost estimates (may include overhead allocation) for activities (or portions of activities) completed during a given period (usually project-to-date). In other words, this value is the budgeted cost of work performed for an activity or group of activities.
   • Actual cost (AC). The actual amount of money either paid for material or charged as labor, material, or overhead to a work order. In other words, actual costs are total costs incurred that must relate to whatever cost was budgeted within the planned value and earned value (which can sometimes be direct labor hours alone, direct costs alone, or all costs including indirect costs) in accomplishing work during a given time period.
   • Planned value (PV). The physical work scheduled, plus the authorized budget to accomplish the scheduled work. Previously, this was called the budgeted costs for work scheduled (BCWS).
3. Gap analysis. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.
   • Gap analysis. A study of whether the data that a company has can meet the business expectations that the company has set for its reporting and BI, and where possible data gaps or missing data might exist.
4. Parametric estimating. An estimating technique that uses a statistical relationship between historical data and other variables (e.g., square footage in construction, lines of code in software development) to calculate an estimate.
5. Opportunity cost. The loss of potential gain from other alternatives when one choice is made.

Instruments

1. Balanced scorecard. A performance-management tool that holistically captures an organization's performance from several vantage points (e.g., sales results vs. inventory levels) on a single page. The scorecard indicates more than just the financial results.
2. Quality control tool.
   • Checklist. A quality control tool that includes a standard set of quality elements and/or possible risks that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.
   • Pareto diagram. A histogram, ordered by frequency of occurrence, that shows how many results were generated by each identified cause.
   • Control chart. A graphic display of the results, over time and against established control limits, of a process. They are used to determine if the process is "in control" or in need of adjustment.
3. Effort performance indicator.
   • Schedule variance (SV). 1) Any difference between the scheduled completion of an activity and the actual completion of that activity. 2) In earned value, EV less BCWS = SV.
   • Schedule performance index (SPI). The schedule efficiency ratio of earned value accomplished against the planned value. The SPI describes what portion of the planned schedule was actually accomplished. The SPI = EV divided by PV.
   • Cost variance (CV). 1) Any difference between the budgeted cost of an activity and the actual cost of that activity. 2) In earned value, EV less ACWP = CV.
   • Cost performance index (CPI). The cost efficiency ratio of earned value to actual costs. CPI is often used to predict the magnitude of a possible cost overrun using the following formula: BAC/CPI = projected cost at completion. CPI = EV divided by AC.

Practices

The successor lecture is Process Engineering Quarter.