Microsoft Frameworks Integrated GlossaryThe Microsoft Integrated Glossary contains terms for: MSF - Microsoft Solutions Framework MOF - Microsoft Operations Framework MSPMO - Project Management Office
A contract between IT and one or more external vendors that defines the responsibilities of all participating parties. The contract binds these parties to provide a particular service (or service component, such as hardware, software, and so on) of a specific agreed-upon quality and quantity, and constrains the demands IT and/or its users may place upon the service (or service component) to those agreed-upon limits defined by the contract.
The enterprise architecture that results when an organization does not attempt to plan for the future.
An adjustment to the version or release in which the version number changes.
The time between incidents or failures when customer expectations are met as specified by the operating level agreement or the service level agreement.
The degree to which an action does not tolerate delay.
Testing whether the product works as intended. It occurs primarily during the stabilizing phase. See also coverage testing.
A behaviorally related sequence of interactions that an actor performs in a dialog with a system to provide some measurable value to the actor; a collection of scenarios.
The person who uses the services on a day-to-day basis.
user education role
One of six MSF team roles. It represents the end user and is responsible for optimizing the end user's performance and experience with the solution. It functions as team advocate to the end user and end-user advocate to the team, participates in defining user requirements and designing features, designs and develops performance support systems, including training materials, and drives the usability process.
The part of the application that interacts with the people operating it.
user performance support elements
One of the deliverables leading to the release milestone. They constitute the final release of the support elements.
A description of the eventual users of the solution in terms of geography, organizational and communication structures, user functions, resource availability, and other relevant information.
A desire of the end user of the application that focuses on the solution to the business problem; its fulfillment is necessary for day-to-day performance of work processes.
A unit of application logic that provides an application with its user interface.
Testing concepts through walk-throughs and prototyping.
The difference between a project's baseline status and current status.
The status of a configuration item, consisting of one or more changes at the specification level. The functional specifications are therefore changed in relation to the earlier version.
A version number, version date, or version date and time stamp.
A process directed at bringing and keeping under control various versions of configuration items of the technical infrastructure.
A combination of xxnn in which xx is the major number and nn is the minor number.
versioned release strategy
A time and resource control strategy in which a deployment project is treated as if it were a series of versioned product releases. This strategy allows the team to deliver a deployment within the expected time frame by providing the most critical functionality in the first version and postponing other desirable features until later releases.
Providing the most critical functionality for a product in the first version and postponing other desirable features into later releases. See also versioned release strategy.
An unbounded view of what the team wants to accomplish.
A major milestone at the end of the envisioning phase that sets forth all the projects and goals for the next versioned release of the enterprise architecture.
A deliverable that expresses the long-term vision of the product and provides a context for decision-making.
vision/scope approved milestone
The first of four major milestones in the IT project life cycle, at which the project team and the customer have agreed on the overall direction of the project. The vision/scope approved milestone is the culmination of the envisioning phase.
The primary deliverable for the envisioning phase. It expresses project goals and constraints as a business case.
vision/scope document drafted
An interim milestone of the envisioning phase, leading to the vision/scope approved milestone.
waterfall life cycle model
A project life cycle model that works well for complex projects as long as the team can easily specify requirements at the beginning. It uses milestones as transition and assessment points.
willingness to learn
A best practice or principle of a successful team. It means committing to self-improvement through gathering and sharing knowledge and institutionalizing learning through such techniques as reviews and postmortems. It is important because it allows team members to benefit from mistakes, helps team members to repeat successes, and mandates time for the team to learn.
The resources expended in a project, multiplied by the duration of the project.
work breakdown structure (WBS)
A deliverable-oriented group of project elements that organizes and defines the total work scope of the project. Each descending level represents an increasingly detailed definition of the project work.
Provides coordination within a department. The work order indicates which function must carry out which action, in which order, and when.
The personnel and equipment required to perform project activities.
A method of avoiding an incident or problem, either from a temporary fix or from a technique, that means the customer is not reliant on a particular aspect of a service that is known to have a problem.
A type of scenario that includes communication and coordination of discrete work processes.
A MOF service management function in the optimizing quadrant. It recommends best practices to recruit, retain, maintain, and motivate the IT workforce.
The first release to testing after all active bugs have been resolved.
A best practice or principle of a successful team. It describes a commitment by the project team to do work at the highest quality possible at the time it is being done, and a commitment by each team member to individually help achieve the desired level of quality. As a practice, the zero-defect mindset does not require that deployed solutions be perfect with literally no defects; rather, it establishes perfection as a consistent goal for which to strive. It is important because it increases product stability, schedule predictability, and accountability.