|
|
| Maintenance - The modification of a software product, after delivery, to correct faults, to improve performance or other attributes, or to adapt the product to a changed environment. |
| M&O Transition Plan - The M&O Transition Plan addresses how the project office will manage the project once the system is implemented in the production environment. The plan focuses not only on the transition implications when moving into the M&O life cycle, but also on the transition of M&O responsibilities between the prime contractor and the M&O contractor. |
| Maintenance and Operations (M&O) Plan - The M&O Plan summarizes the project’s approach to M&O. The plan is similar to the Master Project Plan, but with an emphasis on sustained operations instead of development and implementation. The M&O Plan places a stronger emphasis on the strategic direction of the project/system, the approach to system releases, upgrades and maintenance, and ongoing operations and customer support. |
| Master Schedule - Schedule consisting of key events or milestones (generally, critical accomplishments planned at time intervals throughout the project) and used to monitor overall project performance. May be either a network or bar chart and usually contains minimal detail at a highly summarized level. |
| Mediation - Process of brining parties engaged in a dispute or disagreement together to settle their differences through a meeting with disinterested party, the mediator. Unlike binding arbitration, the mediator has no authority to force a settlement. |
| Mechanism - Technology or other utility that is used by a business system that helps automate a business process, activity, or task. |
| Memorandum of Understanding (MOU) - A formal agreement with another organization that defines the roles and responsibilities and expectations of each party. Usually used to establish an agreement with counties/local offices, particularly when the project will be reimbursing the county/local office for implementation expenses. Refer to the State Contracting Manual. |
| Metrics Process - The Metrics Process describes how measurements will be identified, collected, and analyzed to ensure quality goals (including management and system goals) are being accomplished. The Metrics Process is usually included or referenced in the Quality Management Plan. |
| Milestone - (1) Event with a zero duration and requiring no resources. Used to measure the progress of a project signifies completion or start of a major deliverable or other significant metric such as cost incurred, hours used, payment made, and so on. (2) Identifiable point in a project or set of activities that represents a reporting requirement or completion of a large or important set of activities. |
| Milestone Schedule - Schedule consisting of key events or milestones (generally, critical accomplishments planned at time intervals throughout the project) and used to monitor overall project performance. May be either a network or bar chart and usually contains minimal detail at a highly summarized level. |
| Mission - Specific purpose that all or part of the organization is dedicated to achieving. |
| Mission Statement - Description prepared and endorsed by members of the organization that answers these questions: What do we do? For whom do we do it? How do we go about it? Used as a guide for making decisions in projects. |
| Mitigation - (1) Carefully organized steps taken to reduce or eliminate the probability of a risk's occurring or the impact of a risk on a project.
(2) Actions taken to eliminate or reduce risk by reducing the probability and or impact of occurrence.
|
| Mitigation Strategy - Carefully organized steps taken to reduce or eliminate the probability of a risk's occurring or the impact of a risk on a project. |
| Modification - Change to a project's scope or the terms of a contract; usually written. Examples are changes orders, notices of termination, supplemental agreements, and exercises of contract options. |
| Model - The graphical representation or simulation of a process, relationship or information, along with a narrative that supports the diagram(s). |
| Module - a self-contained software component of a business system, which has a well-defined interface to the other software components; something is modular if it includes or uses modules which can be interchanged as units without disassembly of the module. Design, manufacture, repair, etc. of the modules may be complex, but this is not relevant; once the module exists, it can easily be connected to or disconnected from the system. |
