Operation and Maintenance Project Management Essay 1

How to manage an operation and maintenance project reasonably has always been a problem that I often encounter in the process of work and study. Now I start to record some of my thoughts so that I can summarize and correct them in the future.

First talk about how to choose the content of Maintenance Release:

1. Put all DR, ER and Project into the Project Backlog.

2. Communicate with the Product Owner to prioritize all stories. The evaluation criteria are "urgent, important" two-dimensional way. Of course, the story point, that is, the working hours calculated according to the difficulty level, is the standard considered under the same priority.

3. Only select urgent and important stories to put into a Sprint Backlog, and then evaluate the Sprint Backlog to get a rough idea of ​​the impact on the project, resource consumption and risk response.

4. Start the story in the Sprint Backlog.

5. Regularly communicate with the Product Owner to maintain the correctness of the stories in the Sprint Backlog and the evaluation status of the stories in the Project Backlog, and create a new Sprint Backlog (story's that have not been implemented and whose priorities have been reduced can be put back in the Project Backlog).

6. Put the completed Sprint into the scope of the Maintenance Release.

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=326525807&siteId=291194637