1, the scope of the project baseline is an approved project scope statement, WBS and WBS dictionary.
2, to determine the scope of the project has been completed, to a range benchmark to measure. Product is complete, according to whether the product meets the description of the product is determined.
3, range management plan is to develop the project management plan process and other major input range management processes, including the following
(1) how to formulate instructions project scope.
(2) How to create WBS The specification range.
(3) how to maintain and approved WBS.
(4) How to confirm and formal acceptance of the completed project deliverables.
(5) How to deal with changes to the project scope statement, the whole work change control process is directly linked embodiment.
4, project scope management plan may be in the project management plan, or as a separate one. Depending on the project, it can be detailed or general, can be formal or informal.
5, demand management throughout the process, its most basic task is clear demand, and project teams and users agree that the need to establish a baseline. Also, the demand to establish traceability link chain to ensure that all customer needs are properly applied, and when demand is changed, can completely control their sphere of influence, and always maintain the consistency of product and demand.
6, demand management plan describes how to analyze the entire project life cycle, and records management needs. Including the following.
(1) how to plan, track and report on the activities every need.
(2) resource management needs to be used.
(3) Training Program
Strategy (4) stakeholder participation in demand management
(5) determine the scope of the project is inconsistent with the requirements of the correct procedures and guidelines
(6) tracking the demand structure, that is, which requirements attributes will be included in tracking matrix, and can be traced to these requirements in which other project documents
(7) configuration management activities
7, classification requirements (1) business requirements (2) the needs of stakeholders (3) excess demand (4) quality requirements, QFD for quality requirements have been subdivided into basic needs, expectations, unexpected demands.
8, requirements gathering tools and technologies include interviews, focus groups, guided seminars, group of innovative technologies, group decision-making techniques, questionnaires, observation, prototyping, benchmarking control system interaction diagram, document analysis.
9, focus groups: the pre-selected stakeholders and subject matter experts together to understand their expectations and attitudes towards products, services, or results of the proposed. By a trained moderator bow I guide you conduct interactive discussions. Focus groups tend to be more enthusiastic than the one on one interviews. Focus group interviews with a group instead of one pair - interviews, may have been participating in a 6~10 interviewee. For questions raised by the interviewer, was to carry out an interactive discussion between the interviewer, in order to get more valuable advice.
10, guided seminars: meetings together by inviting major cross-functional stakeholders. Guided Seminar demand for products focused discussion and definition. Rapid technological seminar is an important cross-functional needs and coordination of stakeholders difference in definition. Because group interaction characteristics, are effectively guide the seminar will help to build trust and promote relations, improve communication, which will help participants reach consensus. Another benefit of this technology is the ability to identify and solve problems faster than a single meeting.
11, groups of innovative technology of wood means that you can organize a group activity to identify projects and product demand, population innovations include brainstorming, nominal group technique, Delphi technique, concept / mind maps, affinity diagrams and multi-criteria decision analysis Wait.
(1) brainstorming: to express their views
(2) nominal group technique: to arrange the most useful ideas by voting for further brainstorming or prioritized. Nominal group technique is to deepen the application of brainstorming, it is more structured brainstorming
(3) Delphi technique: personal views can be prevented from being incorrectly amplified
(4) the concept / mind mapping: is obtained from brainstorming ideas with a simple link diagram to reflect the similarities and differences between these ideas to guide new ideas.
(5) affinity diagram, also known as KJ method, a response to a question, the full collection of all kinds of experiences, knowledge, ideas and opinions languages, text data, aggregated by way of illustration, according to their mutual affinity collate these data make clear up the problem, seek common understanding, a way to facilitate settlement. Affinity core figure is brainstorming is to look for reasons based on the results.
(6) multi-criteria decision analysis by means of decision matrix, the establishment of a variety of criteria such as the level of risk, uncertainty and value with gains and other systems analysis, thus many programs a technology assessment and sorting.
12, group decision is to achieve some desired result and evaluate multiple future course of action. Group decision-making techniques used to develop product requirements, and demand for products classified and prioritized.
13, the actual control or benchmark programs and other similar practices tissue practices (e.g., process, operation, etc.) are compared in order to identify best practices, improvements are formed, and to provide a basis for performance evaluation "benchmark control employed "similar organizations" may be an internal organization or external organizations.
14, the system is interactive visual depiction of FIG product, showing the interaction between the system and the participant (process, equipment, information systems, etc.) (user, independent of the other systems of the present system). The system interaction diagram shows the output and the receiver input output service system, input providers, business systems.
15, file analysis is by analyzing existing documents, identification information associated with the demand to tap demand. Lot for analysis of documents, including business plans, marketing documents, agreements, bidding documents, request for proposal, business processes, logical data models, business rules database application software documentation, use case documents, other requirements documents, issue logs, policy , procedures and regulatory documents
16, the main output of the process of gathering requirements demand documents and requirements traceability matrix. Demand document describes how the various individual needs related to the project will meet the business needs.
17, the file content requirements include (but are not limited to) the following: (1) business requirements (2) stakeholder requirements (3) solution requirements (4) project requirements (5) Transition requirements. (6) the assumptions and requirements related dependencies and constraints.
18, including demand management needs to maintain consistency and accuracy of all activities in the product development process, including control requirements baseline, consistent project planning and requirements, version control individual needs and circumstances demand document management needs and linkages between the chains contact, or manage individual project requirements and other deliverables dependencies between objects, track the status of the baseline requirements.
19, traceability is an important feature of the project requirements, requirements traceability and dependencies is a logical connection between the individual and the needs of other trace elements in the establishment of these elements include various types of requirements, business rules, system components, and to help documents. Verifiability is the most basic characteristics of demand
20, each configuration item needs to relate to the product which (or member) needs to be bi-directional traceability. The so-called two-way tracking, including forward and reverse tracking tracking, tracking forward refers to each requirement needs to check whether the file can be found in the corresponding point in the follow-product (the outcome); the reverse is also known as reverse track to track, check the results of the work refers to the design documents, product components, such as whether the test documentation requirements can be found in the source file. In particular, requirements traceability involves five types. Figure:
21, can be traced back to the original requirements from the user requirements document forward, so that we can distinguish the course of the project or after the end of the project due to changes in demand are affected, but also the need to ensure that the file includes all user needs. Similarly, you can demand back from the original files to the appropriate user needs to confirm the source of each requirement. Distinction traceability and backtracking.
22, since the project implementation process, product requirements into design and testing to achieve the elements, so by contacting the chain between individual needs and define specific elements of the product, the product can be traced elements from the requirements document. Contact this chain so that the project team members know the product element corresponding to each demand to ensure product elements to meet every need. The fourth category is back from the chain link elements to the product requirements document, the project team members know the reason for the existence of each element of the product. If you can not design element or test cases back to a requirements document, it is gold-plated behavior may occur. Of course, if a product in isolation elements show a legitimate function, then missed a requirements document needs.
23, the fifth class track chain link between the requirements document, such tracking processing logic facilitates a better correlation between the various needs, requirements decomposition check possible errors or omissions.
24, represents the most common way of chain link between product demand and other elements are tracking needs (capacity) matrix, requirements traceability matrix is a demand for products linked to a table to meet the needs of deliverables from its source.
25, shall be recorded in the requirements traceability matrix-related properties for each demand of these properties help identify key information for each requirement. A typical property requirements tracking matrix record includes a unique identification requirements described in the text, included the reason for the demand, the owner, source, priority, version, current status (for example, in progress, canceled, has been postponed, the new increase, approved, distribution has been completed, etc.) and the status date.
26. The product analysis is an effective tool. In general, for the product and answer questions form the use of the product to be developed, features and other aspects of the description.
27, the range of the specification includes the following items: (1) product description (2) acceptance criteria (3) Exclusion deliverables (4) of the item (5)
Constraints (6) assumptions.
28, marking a milestone deliverables or outcome of the formal completion of phase. The checkpoint is an important milestone, an important milestone in the baseline.
29, WBS work package is located in the bottom of each branch of the deliverable or project work component of the size of the work packages need to follow the principle of 8/80.
30, control account is a management control point. WBS elements are on one level, either work packages, it can be on a higher level than the work packages
One element. In the latter case, the control account including a plurality of work packages, but only a part of a work package account control.
31, the planning package is under the control of accounts known work content but still lack a detailed schedule of activities WBS components. Is under the control of the account, workers
For WBS elements on the package, it is being used to make plans. With the gradual clear case, planning packet will eventually be broken down into work packages and the corresponding
Specific activities.
32, also referred to WBS WBS vocabulary dictionary, which is the profile of the components of WBS
33 Create WBS process tools and technologies are mainly decomposition and expert judgment, usually need to carry out the following activities:
17
(1) identification and analysis deliverables and related work.
(2) The method of determining the structure and layout of the WBS.
(3) from top to bottom layer thinning decomposition.
(4) the development of WBS and dispensing assembly identifier code.
Degree (5) verify deliverables decomposition is appropriate.
34, the principle of decomposition
(1) function or technical principles. When you create a WBS, consider the need to separate the work of different people.
(2) Structure. For the type of project organizational functions, WBS structure must adapt to the organization of the project
(3) system or subsystem. The overall system is divided into several major subsystems, each subsystem then further decomposed
35, during WBS decomposition, there may be three ways noted that, if that is the first layer, also
(1) The life cycle of each phase of the project as a second layer Decomposition
(2) major deliverables as the decomposition of the second layer
(3) a second sub layer as a decomposition
36, WBS is not the responsibility of a project team members should work together to complete the project and unanimously confirmed by all team members, users and stakeholders.
37, more usually WBS hierarchical representation of the main tree structure (Scheme Organization) and tables (tabular).
38, the tree structure of FIG WBS is clear and intuitive and structural strength, but not easy to modify, to a large, complex projects difficult items shown
The whole picture. For small and medium sized projects. Table intuitive form of relatively poor, but reflect all elements of the project work for large-scale projects.
39, in the process of decomposition, it should be noted that the following eight aspects.
(1) WBS must be oriented deliverables. The project aims to provide a product or service, just a series of special events.
(2) WBS must comply with the scope of the project. WBS must be included, and only for activities including deliverables of completed projects
The bottom layer (3) WBS should support planning and control. WBS is a bridge between the project management plan and project scope, not only to support the bottom of the WBS items
Project management plan, schedule and budget and to let the management to monitor and control projects.
(4) WBS elements must be someone in charge of, and responsible for only one person, although it may in fact require more than one person involved
(5) to guide the WBS. As a guide rather than a principle, WBS should be controlled at 4 ~ 6 layers. Of course, large projects can be more than 6 layers.
(6) WBS should include project management, but also including subcontracted work.
(7) WBS preparation needs of all stakeholders (mainly) involved in the project, the project team members need to be involved.
(8) WBS is not static "in the work after the completion of the WBS, WBS still may need to be modified.
40, when a project WBS decomposition is complete, stakeholders should be given to the completion of the WBS confirmation, and this consensus.
41, the main tools and techniques is to check and confirm the scope of group decision-making techniques. Check also referred to the examination, evaluation, audit, walkthrough, inspection, testing and so on.
42, the range should be confirmed throughout the project, the following general procedure
(1) determine the time required to confirm the scope.
(2) identifying the need to confirm which input range.
(3) determine the criteria and elements range officially accepted.
(4) the step of determining a range to confirm the organization of the session.
(5) Organization confirmed the meeting.
43, confirm and verify product range: verifying whether the product is a product for the completion of the project (or phase) at the end to verify by the sponsor or client, strong
Adjust product is complete; the range is confirmed for the project deliverables, validation process and acceptance by the customer at the end of stage or sponsor.
44, to determine the extent and quality control, it was confirmed except that the range and quality control:
Confirm range (1) the main emphasis obtain customer acceptance of deliverables or sponsors; emphasis on quality control of the correctness of deliverables, and consistent with its
The development of specific quality requirements (quality standard).
(2) Quality control is generally performed before the confirmation band, may be performed simultaneously; determine the extent of the end stage is generally carried out, but not necessarily in quality control
Stage was not performed.
(3) the case of internal quality control inspection, the quality provided by the appropriate department of the organization performed; range is confirmed by the external stakeholders (client or originator) of
Project deliverables inspection and acceptance.
45, with the end of the project to determine the extent, scope and confirmed except that the end of the project:
(1) While recognizing the scope and project closeout work is not carried out in stages, but the emphasis is to confirm the scope of the verification and acceptance of deliverables, and project closure
It emphasized that the end of the project (or phase) to do the process work.
(2) to confirm the scope of the project closeout have acceptance, confirm acceptance of the project scope emphasize deliverables, project closeout emphasis on product acceptance.
46, Requirements Engineering: demand-related activities are called requirements engineering, divided into two categories: one is the development of demand, one is demand management.
47, the main development needs include: requirements capture (capture the user's needs), demand analysis (analysis of the demand for information, an abstract description, the concept of establishment
Model), requirements definition (preparation of "Requirements Specification"), requirements validation (for the needs of the document review, identify needs.) On the demand development, completion
After the verification process needs to determine requirements baseline.
48, demand management include: Develop Requirements Management Plan (how demand management), and seek understanding of the requirements (to ensure that stakeholders demand positive
Really understand), obtained promises on demand (to achieve consensus and build commitment) between the activities of personnel needed requirements, management requirements change (by changing the flow
Cheng manage demand and prevent the spread of demand), maintain two-way traceability to requirements (two-way track between requirements and product documentation), project identification work
Inconsistency between work and demand (identify inconsistencies between the project plans and work products and demand).
