5) Determine the functional range of the solution
I. Function range
Range: Visions of the idea of the solution that can be completed under the constraints of a given version
l Solution Scope: The sum of the products and services provided in a version of the solution
l Functional range of the project: Items submitted by the team within the scope of the solution
Multiple items may be done for completing a holistic solution
II. By versioning constraint function range
task:
l Determine its functionality by dividing solutions into a series of published versions.
l Determine the content of the current solution and the next solution
l Create multi-version plan
l Sets the function range for version 1
III. Function Range Management
Focus management
l Avoid the spread of the functional range
l Clearly define the boundaries of the functional range
Functional range management technology
l Balanced triangle
l balance matrix
definition:
l The spread of the function range: the expansion of the function range of management
IV. Use balance triangles to manage function range
Triangle represents variable relationship between resources, schedule and characteristics
V. Using the project balance matrix to manage function range
Microsoft Solution Architecture is an agreement between team and users
The resource is fixed, the schedule is optional, the feature is adjustable
VI. Drafting Function
Functional documents include:
l problem description
l idea
l initial demand
l user file
l function range
l concept
l Function of the project
Remember: Imagine a process of iteration
Temporary milestone: baseline of the function range is defined
VII. Evaluation Risk
task:
l Start in the project startup stage
l The core team is assembled together to discover the risk of project through the brainstorm.
l Continue the risk assessment process to:
N analysis and arranging risks
n Create a risk assessment document
important:
l In the initial assessment of project risk
l Provide the foundation for the ongoing risk management
l is used to arrange schedules and make decisions
2) Establish a review and change
I. Establish traceability
Make sure the final result meets the initial business goals and needs
Ii. Traceability benefits
Contact characteristics with business needs
Combined with change control
Promote the consistency of formal quality management standards
Iii. Establish change control
important:
l Applicable to all changes
l Simple combination of driving changes
l On the basis of establishing the core creation of the Microsoft Solutions Architecture
l As early as a document baseline, but you can keep your team's flexibility as night.
definition:
l Change control: a process of requiring, review, adopting, building documentation, and issuance
IV. Establish configuration management
important:
l Push early regeneration or rollback
l Requires team to configure documentation to database or other tools
definition:
l Configuration Management is a formal process for tracking and controlling the status of different solutions
V. Imagine milestones and delivery items
Group core team / for functional range
Submitted items
l Function range documentation
l project structure documentation
l initial risk assessment documentation
Vi. Its success standards
Investors and project teams have been consistent with the following aspects:
l motivation
l Solution to the idea
l Solutions functional range
l concept
l project team and structure
Constraints and goals have formed a document
Be initial risk assessment
The process of establishing changes control and configuration management
Sponsor or key investors formally approved the idea
3) Summary of modules
The goal of the idea is to create a view of the initial concept of a high-level project goal and solution.
Key Steps to optimize team preparation are metrics, analyze gaps, create a learning plan and implement a learning program.
A common idea makes the team adapts to a common direction, strengthens the goal of the program, and maintains the quality of the focus.
