Scrum drill (1)

 

After reading n times, N> 10. The more I think scrum is feasible, I am going to try a small project first.

 

First, this DMM project only has functional requirements and has no operation interface requirements. There are no more than two lines of text provided.

Previous practices: system design, database design, and uidesign.

Scrum practice: Compile the product backlog for a Sprint plan.

Preparing product backlog is a highlight of my reading this book and has been plagued by how to demonstrate it. I don't know how to end the work because I don't know how to end it. It is of course a good wish to be satisfied. However, as a developer, a function can be modified repeatedly without being recognized and lost. How does backlog demonstrate how to solve this problem. A business requirement, coupled with how to demonstrate, has a standard to determine whether development is complete.

Step 1: Compile the product backlog

The backlog reading is so lightweight that the fields are listed. It is still difficult to write a demo. It is a bit like a test case. However, I feel very good when writing it. How to demonstrate it is just like operating on a ready system? Imagine testing various functions. In the process of writing, I still don't think I should start listing some objects and attributes. I don't know if it stays at the business level. Then I listed 12 backlogs. Print it as a card in the book.

Step 2: Sprint plan MEETING

Although the book has been read n times, the Convener Ma has forgotten all about the meeting. I will share the cards on the table for you to see first. Then we discussed the function and made some adjustments to the priority. Then we start to estimate the value. I am familiar with this because I have played several card games in my team. During the estimation process, several backlogs with similar functions and smaller values are merged. Finally, seven backlogs are obtained, with an estimated value of 16.

After that, I announced the meeting. When I came back, I found that the sprint cycle, target, and demo date were not mentioned. Dizzy. Fortunately, I spoke about how to break down tasks next Monday.

After sorting out the data, the 8-day development cycle is obtained based on the calculation of 3 developers and 70% investment. Filtering this project is secondary. You have other important projects in your hands, and the investment level has to be lowered. Next Sunday, I will summarize my comments, set a target, and release the demo date.