Construction of the Law 9th 10 7 Chapter Summary and feeling

Nineth Chapter Project Manager

What's 9.1PM?

Project Manager: PM

9.2 History of Microsoft PM

Microsoft's manager is called: Program Manager

In 1981, Charles Simone found two questions as Microsoft's business grew:

1. The cost of communication between team members has increased sharply

2. There are a lot of open laws and other things outside the test, need someone responsible

The cost of communication is too high.

What programmers don't want to do: 1. Communicate with customers, organize user surveys, and discover user needs.

2. Understand and compare competitor's products.

3. How to make the software usable, useful.

4. How to improve the team's process.

9.3PM do everything except development and testing

Program Manger

Work equally with everyone and push the team to complete the functionality of the software

A team can have a lot of PM

Forming a resolution with other team members

Steward, no one.

Be sure to do a specific job

9.4PM and Risk Management

Categories of risk: personnel, processes, technology, environment

Source of risk: customer, end customer, stakeholder, project member, partner

Project budget, cost, demand

Development and testing tools, platforms, security, technology for releasing products, technology related to our products

Laws, regulations, market competition environment, economic situation, technology trends, business model

9.5PM Capability requirements and tasks

1. Observation, understanding and rapid learning ability

2. Analytical management Capabilities

3. A certain degree of professional competence

4. Ability to Introspect

Tenth. Typical users and scenarios

10.1 Typical users and typical scenarios

A typical user's template can include the following:

1. Name

2. Age and income

3. Proportion and importance of the users represented in the market

4. Typical scenarios for using this software

5. Environment in which the software is used

6. Living and Working conditions

7. Knowledge levels and competencies

8. Motivation, purpose and difficulty of the user

9. User Preferences

10.2 Use Cases

Title: Describe the purpose for which this use case is to be achieved

Roles: Roles that interact with software systems, such as users, other entities, and even time

The main success scenario: A series of steps that describe how the role interacts with the system to achieve the goal

Extended scenario: Describes some extended interactions, such as some unexpected situations

10.3 Spec Sheet

function manual

First, define the relevant concepts.

Second, standardize some assumptions.

Thirdly, avoid some misunderstandings and define some boundary conditions

Describe the mainstream user

Five, some good features will have side effects

Six, the quality of service description

10.4 Function-driven design

First step: Construct the overall model

Step two: Construct a list of features

Step three: Develop a development plan

Fourth step: Functional design phase

Fifth step: Achieve specific functions

Chapter Seventh MSF

7.1MSF history

7.2MSF Basic Principles

1. Promote information sharing and communication

2. Working for a common vision

3. Full Empowerment and trust

4. Co-responsible for the project

5. Value of delivery increments

6. Keep agile, anticipate and adapt to change

7. Quality of investment

8. Learn all the experience

9. Working with customers

7.4MSF Process Model

7.5MSF support for Agile and CMMI

Construction of the Law 9th 10 7 Chapter Summary and feeling