Microsoft Frameworks Integrated GlossaryThe Microsoft Integrated Glossary contains terms for: MSF - Microsoft Solutions Framework MOF - Microsoft Operations Framework MSPMO - Project Management Office
Actions relating to the coordination and organization of work (in progress). Decisions on the tactical level influence the procedures employed in the various departments. Tactical management is responsible for translating the separate management sectors into actuality as well as all equipment needed for this (hardware and software) and personnel.
A generic term for work that is not included in the work breakdown structure, but potentially could be a further decomposition of work by the individuals responsible for that work. It is also the lowest level of effort on a project.
A type of scenario that includes detailed steps for required activities.
team goals for success
A set of principles for successful teaming that focus on giving customers what they want, on time and within budget.
The manager of a project subteam that collectively represents a team role or team role cluster within a MOF or MSF project.
An organizational work model that emphasizes the use of small, cohesive teams of interdependent, multidisciplinary role specialists who communicate on an equal basis in the accomplishment of their individual and group tasks. In MOF, the team role clusters are release, operations, support, partner, infrastructure, security. In MSF, the team role clusters include are program management, product management, development, test, logistics, and user education.
team model for application development
A small team of peers working in interdependent, multidisciplinary roles. The team model is a starting point, not the final answer, for good project management, emphasizing a flexible approach, dependent on project scope, team size, and team member skills.
team of peers
An organizational work model that emphasizes the use of small, cohesive teams of role specialists who communicate on an equal basis in the accomplishment of their individual and group tasks. This work model contrasts to that of the traditional top-down, linear-structure work model, and has been functionally proven in a variety of different organizations, cultures, and project sizes.
The six divisions of the MSF team model, including product management, program management, development, user education, test, and logistics.
Synonym for MSF development lead within an engagement.
A technology perspective views the enterprise architecture from the perspective of the technological infrastructure that supports the business processes of the enterprise architecture.
technology validation complete interim milestone
The point during the developing phase at which the project team has evaluated the technology against the functional specification in an isolated, clean environment.
An environment that corresponds as closely as possible to the production environment and within which system and user acceptance tests can be carried out.
A plan developed by the testing role that outlines how testing plans to maintain the reliability of the product and to ensure that all issues are known.
Ensuring that the right things are done right at the right time.
Deliverables of the developing phase that outline what testing plans to do (including the test plan) and are baselined at the scope complete milestone.
testing results and testing tools
One of the deliverables leading to the release milestone. They capture the bug database and test materials for future reference.
One of six MSF team roles. The testing role's responsibility is to accurately portray the status of the product or solution at any time by clearly documenting what is currently wrong and what is currently right with the product. It develops testing strategy, plans, and scripts to ensure all issues are known; manages the build process; conducts tests to determine the status of production development accurately; and participates in setting the quality bar.
top 10 risk list
An identification of the 10 top priority risks, taken from the risk assessment document.
The person who tracks progress on a service incident to ensure service levels are not violated. In most cases, the tracking owner is the person who registers a service incident, although tracking ownership can be transferred in rare cases.
Monitoring the risks and their mitigation plans.
A technique for managing project trade-offs by portraying them in a matrix that reflects the three project variables in the context of three decisions-whether to optimize, constrain, or accept a given variable.
A triangle of project variables whose three sides are resources (people and money), schedule (time), and features (the product and its quality). It is used to make project trade-offs. A change to one of its sides requires that the team make a correction on one of the three sides to maintain project balance, including potentially the same side on which the change first occurred. For example, a decision to add a feature to a product may require that other features be removed if sufficient time and resources are unavailable to support their development.
A team based on a hierarchical organization chart, with a manager at the top and subordinates below.
In the MOF risk model, a measurement threshold that indicates that the condition is about to occur. It is a value that is either true or false. When it shifts from false to true, the team executes the contingency plan.
Indications that a risk has occurred or is about to occur. They sometimes are called risk symptoms or warning signs. Triggers may be discovered in the risk identification process and watched in the risk monitoring and control process.
trigger, risk contingency
The criterion for executing a contingency plan.
Technology strategy consultant