Content deleted Content added
→Envisioning phase: Remove <font face> per WP:FONTFAMILY and fix up the mess |
m →Envisioning phase: convert html to wikicode |
||
Line 40:
''Figure 2: Envisioning phase process/data model''
{| WIDTH=581 BORDER=1
|- VALIGN=TOP
| WIDTH=194 |
Activity
||
Definition (source)
|-
|
Analyze requirements
|
During the envisioning phase, business requirements must be identified and analyzed.
“These are refined more rigorously during the planning phase.”
(MSF Process model)<ref name="ReferenceA">Microsoft Solutions White Paper June 2002</ref>
|-
| Define Goals and Constraints
|
“Envisioning, by creating a high-level view of the project’s goals and constraints.”
(MSF Process model)<ref name="ReferenceA"/>
|-
|Form Team
|
Formation of the core team.
|-
| Create Vision/scope
| “The preparation and delivery of a vision/scope document.”
(MSF Process model)<ref name="ReferenceA"/>
|-
| Create Risk assessment
| “During the envisioning phase, the team prepares a risk document and presents the top risks.”
(MSF Process model)<ref name="ReferenceA"/>
|}
''Table 1: Envisioning activities''
Line 106 ⟶ 81:
The basic activities performed in the envisioning phase are analyzing the requirements, forming the team for the project, determining the risks and the scope of the project. From the requirements and the goals of the project a Vision/Scope document is created. This document describes what the product is to be when it is delivered. It does not contain very detailed functionalities of the product.
| WIDTH=329 | Definition (source)
|-
| VISION/SCOPE DOCUMENT
| “Document defining the Vision and Scope.”
(MSF Process model)<ref name="ReferenceA"/>
|-
| VISION
| “''Vision''is an unbounded view of what a solution may be.”
(MSF Process model)<ref name="ReferenceA"/>
|-
| SCOPE
| “''Scope'' identifies the part(s) of the vision can be accomplished within the project constraints.”
(MSF Process model)<ref name="ReferenceA"/>
|-
| RISK ASSESSMENT DOCUMENT
| “Standardized document for Risk Assessment”
(MSF Risk Management Discipline)<ref name="ReferenceB">Microsoft Risk Management Discipline White Paper</ref>
|-
| PRIORITIZED RISK LIST
| “Detailed risk information including project condition, context, root cause, and the metrics used for prioritization (probability, impact, exposure) are often recorded for each risk in the risk statement form.”
(MSF Risk Management Discipline)<ref name="ReferenceB"/>
|-
| RISK PLANNING
| “Translation of the prioritized risk list into action plans.”
(MSF Risk Management Discipline)<ref name="ReferenceB"/>
|-
| PROJECT STRUCTURE DOCUMENT
| “The project structure document includes information on how the team is organized and who plays which roles and has specific responsibilities. The project structure document also clarifies the chain of accountability to the customer and designated points of contact that the project team has with the customer. These can vary depending on the circumstances of the project.”
(MSF Process model)<ref name="ReferenceA"/>
|-
| TEAM ORGANIZATION
| “Information on how the team is organized.”
(MSF Process model)<ref name="ReferenceA"/>
|-
| CONTACT POINTS
| “Designated points of contact that the project team has with the customer.”
(MSF Process model)<ref name="ReferenceA"/>
|-
| TEAM ROLES
| “Definition of who plays which roles and has specific responsibilities.”
(MSF Process model)<ref name="ReferenceA"/>
|}
''Table 2: Concepts in the envisioning phase''
| |||