5 real cases of using scrum for project management

Introduction:

I will track and record a series of articles that I am currently working on using a complete scrum management project. There will be some lessons to learn and encourage readers to learn from each other. Hai Han is still recommended for some incorrect or poorly written information. Of course, I hope you can provide more valuable comments. The support of readers is my greatest motivation. (One, two, three, four, five, six)

========================================================== ========================================================== ================

The project was finally settled in a slump. This project is not big. It has a total manpower of 34.2 RMB/month, and the actual manpower investment is about 28 RMB. Because it is an internal project and can also be regarded as a test field for implementing agile methods, the estimation is sufficient. However, whether it is CPI or SPI, the project is relatively successful from various aspects of data. The defect rate is relatively low; The project runs smoothly and saves manpower; the customer is satisfied; basically there is no overtime; in short, I am very satisfied with this project. Of course, I would like to thank every member of the Project for their efforts, especially TM (Technical
Manager) cooperation and support.

Finally, let's review my entire project:

The entire project process is a bit like the fall-scrum-fall process on the Internet, first waterfall-> then agile-> finally waterfall

1. at the initial stage of the project, the sponsor or project creator pre-assigned (not yet authorized) PM follows up on some ideas raised by the customer, communicates with the customer, and proposes a product vision based on the company's existing capabilities or technologies, then generate the feature list and the general business model and architecture of the system.

2. submit the case (authorized by PM), reach a willingness with the customer, and submit the documents mentioned above to the company for filing. At this time, we need to make human estimation and time-range estimation. Of course, this is a rough estimate for filing.

3. market analysis and further planning. At this time, TM will participate and discuss the more detailed feature with the customer, including the modules and functions. PM and TM will make detailed HR estimates together, generate a baseline for manpower and time history.

4. Pre-research, architecture and implementation. For key technical points, we first need to perform risk assessment and do some pre-research work to reduce risks. Design the system skeleton and implement one or two examples. Because we are using agility, we will not do a very detailed design here. We should try our best to do it first and then rebuild and improve it, but remember to rebuild it constantly without accumulating design problems, otherwise, it will be a big disaster.

5. Start to be truly agile. At this time, we have entered the real substantive development work. Throughout the development phase, we are using the agile scrum framework.

5.1. Our product backlog is the refined feature list we mentioned above. First, we will do the release plan and define the iteration cycle.

5.2. Select some feature from Pb to the sprint backlog and start the planning meeting sprint planning meeting. I have already mentioned several scrum meetings in my previous articles. I will not elaborate on them here.

5.3. then generate the task wall dashboard. During the iteration operation period, the project progress will be tracked through daily morning meetings, task walls, and burn-out diagrams to control deviations and risks.

5.4. There will be a demo meeting after the sprint. Let's take a look at the results of this iteration and see if we can deliver it as story. Then, collect feedback records as the tasks that may be completed in the next sprint.

5.5. Next we will hold a reflection meeting to review what we did well in the previous sprint, what we did badly, and what we could do better? Select the two or three most important items, take action plans, and then improve them in the next sprint. (I think we have done a very good job in this regard. I personally think this meeting is also very important, so that we can continue to improve)

Then, one sprint after another is repeated until the development is complete.

6. In the system testing phase, specialized testers will perform testing and acceptance for the entire product. Development and testing are completed together.

7. After the test and acceptance are completed, the final version is submitted to the user for UAT acceptance.

8. Pass the acceptance and complete the work. Summarize projects and collect documents.

The entire project is completed.

I simply listed the entire project process in sequence. If you have any questions, you can leave a message directly or contact me via Weibo, I will do everything I know. Haha

My weibo is: http://weibo.com/lackinpm