Shulou(Shulou.com)06/03 Report--

Introduction:

For agile software development, it is very important to keep up with the progress of the project, because you can keep abreast of the team's health and deal with all kinds of emergencies at all times. so as to ensure that our project can be delivered on time at the end of each iteration.

Implementation method:

Of course, the best tool to see the progress of the project is burndown chart, we use Jira as a project management tool, there is a Report view in Jira, which can directly display the burndown curve of story, so that the team can intuitively understand how the sprint is going.

Of course, this is from the story level, it measures the change curve of story point over time, such as the figure above, we can see that the development speed of our project is first slow and then fast, that is because multiple story are carried out at the same time, but they are not finished yet, so our time is invested, but there is no corresponding story shut down in the early stage. 2. We added a new story in the middle of sprint, which led to the rise of story point ordinates.

It is not right to have a burn down diagram alone. We also have to track the progress of each story, which requires us to update the status of each sub-task in a timely manner. Generally, story/sub-task has 4 statuses: Backlog (not yet started), Work In Progress (doing), Ready For Review (finished, waiting to be review), Done (review is finished and determined to be valid, so the story/sub-task is really turned off) In order to enable the team to update the status more actively, we used white-board track. First of all, on the first day, when everyone had set up the corresponding sub-task, I printed everything out, and then posted it all on the whiteboard in the form of a small note, and put it on the Backlog. If the team members made any progress, they would move the note forward (such as moving the note from the Backlog column to Work In Progress).

Then, in our daily report, we will describe the progress of the Sprint project in two large blocks, one in Story and the other in team members.

For example, the table in units of Story in the report is as follows:

The report in the project from the perspective of Resource is as follows:

Summary:

My experience is that tracking the progress of a project requires a combination of tools / practices.

(1) if there is too much difference between the actual curve and the ideal benchmark curve, team leader needs to find out the cause of the problem and solve it in time. This is also one of the advantages of burn down chart, "facing change".

(2) use dashboard to maintain everyone's project activities, on the one hand, to improve everyone's enthusiasm, because every time the note moves forward can bring a small sense of achievement, and second, let everyone have the feeling of competition, race, we do not lag behind, so as to ensure the health of the project.

(3) use daily report to provide snapshot of daily operation, which is also to provide strong factual basis and material for process improvement in the future.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.