First knowledge of agile development

# Agile development #User stories can be expressed in 3C, including card, conversation, and confirmation ). The card is a text description of the story. However, the requirement details are obtained through the conversation, and The requirements confirmed by the conversation are recorded on the card. Note: Cards represent customer/user needs rather than requirements recorded. Developers communicate with customer teams (testers, product managers, actual users, etc)

# Agile development # Write Excellent user stories with six features: Independent, negotiable, valuable to purchasers or users), estimatable, small, and testable ).

# Agile development #When writing user stories, developers assist in writing and communicate with the customer team. The customer team is responsible for writing and communicating with developers. When developers are asked about the technical or framework information for implementing the story, they should answer the question from the user's perspective, rather than the technical term.

# Agile development ## User Role Modeling # identify the users in the project, integrate users, refine users, Virtualize users, and write the descriptions of Virtual Characters on paper, hanging on the walls, for the team to understand.

# Agile development # Collect stories. You only need to use the stories. The process of collecting stories is the process of "fishing for Fish. Different Sizes of network capture needs.

Agile development #The fishing net cannot capture all the fish, so it cannot capture all the needs. The captured fish may also be dead fish or waste, and the ineffective demand expands the demand. First, the overall feeling of the software is formed by using the big network to find the big demand. The medium demand is captured by the Chinese network, so there is no need to worry about small demands for the moment.

# Agile development # The best way to collect stories is to interview users, communicate face-to-face with users, and obtain useful requirements through open-ended questions that are irrelevant to the background. For example, "could you tell me how you want to search for a hotel ?" Better than "do you want to search for a hotel by region ?"

# Agile development # In project development, there are generally no real users, so there is a role such as a user proxy, and domain experts can assume the user proxy role, which may lead to complexity.

# Agile development # User story acceptance test, two procedures, the first step is to write the test points on the back of the card, if the demand is updated, there is a new test point, the tester updated the back of the card and Step 2 turned the test point into a comprehensive test. The test passed, which indicates that the story has been correctly and completely implemented.

# Agile development #User story Acceptance Test, test point is writtenCodePreviously, a customer team wrote this article. The purpose of the test is to locate the defect, rather than for coverage.

# Agile development #Estimate the story point. The story point is the complexity of the story and the relative workload estimation. The whole team estimates the story, not a person. Generally, a story is about an ideal person's day's work or an ideal day's work. Developers should take into account all the things to be done in the story, test code and customer communication into full consideration, assist testers or acceptance tests, and learn the story as much as possible during estimation.

# Agile development #Iteration plan meeting, 1. Discuss the story based on priority; 2. Split the story by developers; 3. Estimate and confirm the size based on the characters.

# Agile development # The srummaster's power comes from the team and is only responsible for process-related tasks and cannot exceed the scope of the process. Similar to the Relationship Between Fitness coaches and athletes.

# Agile development #Test-driven development, refactoring, collective ownership, continuous integration, Pair programming, and other technical practices improve the team's comprehensive capabilities.

# Agile development #The potential deliverable software of each iteration can be provided in advance and feedback on progress can be encouraged, and can be released as soon as necessary. Potential Deliverable means testing, means integration is complete, and does not mean functional integrity.

# Agile development # Product owners need to provide the team with two things: Vision and boundaries. Vision: The product vision, product uniqueness, and competitors, or what competitors are doing. Boundary: product development time, speed, and so on.