0525Scrum Project 7.0

First, SPRING1 review:

In this first sprint, we mainly completed the main interface of the establishment of the process, although some twists and turns, we sometimes find materials, pictures have some conflict, but in the end we still disagree, try to do a good interface!

In this sprint, although we have finished the main interface, but there are many shortcomings, such as the interface is a little too simple, a little bit more space, there is no special effects, just got a dynamic background map.

Improved:

Hope to see more fulfilling things in the interface, add a piece of background music!

can also do more beautiful and generous some!

Second, the review:

　　The eighth chapter: mainly discusses the software requirements analysis, how to accurately find these requirements, mainly: 1. Acquisition and guidance requirements 2. Analyze and define requirements 3. Validation requirements 4. Managing requirements in the SOFTWARE PRODUCT lifecycle when analyzing software, you also need software PRODUCT stakeholders, including: Users, customers, parents, market analysts  , software engineers next we need to obtain user requirements-user survey, the following are several research methods: 1 focus group 2 "in-depth interview 3" card classification 4 "User Survey 5" User log Study 6 "Anthropological Survey 7" Eye tracking Research 8 "Rapid prototype Research 9" A/b test Then it introduced the competitive demand Analysis framework N (need demand) A (approach method) B (benefit Benefits) C (competition competition) D (delivery Promotion) after the need for functional positioning and prioritization, To do this we have to divide the function into four different quadrants: killer function, peripheral function, required demand, auxiliary demand, according to different functions, with different methods to treat them. Then we need to make appropriate plans and projections for our projects. How do we end up with our projects after we've done the work? That is divide-and-conquer, dividing a large deliverable into small, concrete deliverables, which is the right way to handle it.

The Nineth Chapter: This chapter is about the project manager's origin and requirements, the difference between project manager and other managers, PM's professional ability. The ability to act as a pm,pm is important. PM is a good pm that has the ability and is approved by everyone. In this section, the project manager is simply the leader of the project team, and the project manager's primary responsibility is to lead the project team to complete the project work and satisfy the customer in a timely and high-budget manner. For this purpose, the project manager must lead in a series of project planning, organization and control activities to achieve the project objectives.

The Tenth chapter:

1. Typical scenarios and typical users

User awareness, such as the value of the user, how to define the user, the combination of users and scenes, from the scene to the task, as well as the user's template or story.

2. Specification Sheet

(1) Function manual

Define related concepts--specification good hypothesis--avoid misunderstanding, define some of the user/software interaction steps-----some good features and side effects---quality of service

(2) Function specification template

(3) Technical manual

(4) Function-driven design

Build the overall model, build a feature list, develop a development plan, feature design phase, to achieve specific functions

This section teaches us how to define a typical user and provide a template for defining typical users and scenarios that can help us imitate.

0525Scrum Project 7.0