Microsoft Frameworks Integrated GlossaryThe Microsoft Integrated Glossary contains terms for: MSF - Microsoft Solutions Framework MOF - Microsoft Operations Framework MSPMO - Project Management Office
A snapshot of a project, specification, schedule, or other entity at a set point in time. A baseline consists of the original approved plan, plus or minus approved scope changes; it is used as a point of reference to measure progress. It is usually used with a modifier (a cost baseline or schedule baseline, for example). It may document an IT architecture and underlying dependencies at a given point in time, or may be used to document the current status of a development or other project.
For availability management in an operations setting, the term also is used to identify an agreed set of availability definitions and targets for an IT service. Such definitions and targets normally would have been proved through modeling and, once defined, would be used as key availability design and reporting criteria.
An optimal set of procedures and functional principles, typically derived from previous experience. When followed, best practices generally result in improved results, enhanced work flow, and other benefits in completing project activities. However, following best practices does not guarantee satisfactory results from a particular project.
Testing of a stabilized product by external end users.
A principle of good scheduling. It means having those who do the work estimate the effort, rolling up task-level estimates, and recognizing that experience is the best estimating technique.
An incidental, short-term interruption of automated information services.
Time added to a project schedule to help the project team accommodate unexpected problems and changes. Synonymous with PMI Body of Knowledge reserve, which may be applied to either schedule or cost. A buffer is typically created by setting an internal deadline that occurs sooner than the external one that has been publicized.
Any issue arising from the use of the product.
Making bugs actionable by determining severity, which measures its impact on the product, and by priority, which measures how important it is to fix the bug.
The point at which the rate of fixed bugs exceeds the rate of found bugs.
Addressing a bug in some fashion.
Evaluating and prioritizing bugs to determine their appropriate resolution.
The process involved in taking one or more input configuration items and processing them (building them) to create one or more output configuration itemsfor example, software compile and load.
One of the four strategies designed to extricate an organization from the IT abyss. The build strategy endeavors to define a long-term infrastructure target that increases flexibility while maintaining cost levels.
In the MOF risk model, a description of the way in which the operational consequence would affect the business as a whole.
The highest level of what business processes are intended to accomplish. For example, financial management is a business function; accounts receivable is a related business process. See also business process.
A desire of the project customer that focuses on the business problem; its fulfillment is strategic to organization goals. See also user requirement.
An IT project from the point of view of the associated business processes. Most commonly, this is the view taken by the project customer, sponsor, and/or product manager.
A process is a structured, measured set of activities designed to produce a specified output for a particular customer or market. It implies a strong emphasis on how work is done within an organization. (Davenport, Harvard Business Review, 1993). Business processes have customers and in most cases (but not always) cross organizational boundaries.
A unit of application logic that controls the sequencing and enforcing of business rules.