I. R&D Management Lifecycle (SDLC)

How to break the ice when Agile is introduced

III. Project and team

4. Create a project

4.1 Project CreqPool (Business Requirements Pool)

It is used to connect the requirements of business departments, marketing departments and product departments as the requirements pool for iterative requirements review.

4.2 Project CSTC(Iterative Project)

For daily iteration management, after requirements are reviewed, the cleared requirements are transferred to the project Backlog. Create Sprint iteration plans and management based on this project.

How to manage structured requirements

  • A story, also known as a “user story,” is a short request or request from the end user’s point of view.
  • Epics are large works that can be broken down into many smaller tasks (called stories).
  • The Initiative is an epic collection of steps toward a common goal.
  • Topics are key areas of concern for the entire organization.

For example:

6. Requirements decomposition steps

VII. Workflow design

VIII. Iteration mechanism and branching strategy

IX. Based on JIRA agile management practices

9.1 Product Backlog Combing

1) Product Backlog Combing — Create user stories, individual tasks, and subtasks

Create user stories from the corresponding project products, PO and Master; Create your own individual tasks and subtasks by the corresponding agile team members.

【 Key Graphic 】

2) Product Backlog combing — breaking up and estimating user stories

[Summary] The result of breaking down and estimating user stories by PO or Master is entered into JIRA according to the user story “syllogism”. The user stories, tasks, and subtasks that go into the product Backlog need to be estimated (in terms of story points, team estimates) before they go into the iteration.

【 Key Graphic 】

3) Product Backlog sorting — scroll update and sorting

The PO is used to drag and drop the issues in the product Backlog to reorder them, and also to update the priority in the Issue property page. The items are arranged according to the priority, from top to bottom. The order cannot be changed at will. Only the corresponding PO can be modified.

【 Key Graphic 】

9.2 version planning and iteration planning

1) Release Planning and Iteration Planning — Create releases and manage releases

[Summary] Create and manage a version in the project Settings for the project owner or master, preferably the production version.

【 Key Graphic 】

2) Release Planning and Iteration Planning — Create and manage iterations

[Summary] Build an iterative development plan for each release that responds to the page creation iteration and management iteration of the project leader or master in the Agile Kanban.

  • Before the Sprint starts, make sure that the start and end times of the iteration are correct and that there are any missing story tasks.
  • Whether the stories in this iteration are dismantled and estimated story points; Otherwise, after the start of the estimation, it will affect the burnout diagram and speed diagram;

【 Key Graphic 】

3) Version planning and iteration planning — Implement iteration development plans

[summary] corresponding to the agile team members to drag their own tasks, subtasks and so on the specified column, and to update the Issue status; The team Master or test lead will drag and drop the user story to the specified column and close the iteration when it finishes.

  • Iteration tasks are performed in the Active Sprints panel of the Agile Kanban, where each Issue appears as a card in the panel column and can be dragged and dropped to update status;
  • After clicking Finish Sprint, the unfinished Issue will be automatically returned to the Backlog to be processed.
  • You can set the properties to be displayed on the card, such as handlers, test leaders, initial estimates, and so on, using the panels-configutions-card layout.

【 Key Graphic 】

9.3 Daily stops

1) Daily Station Meeting — Use JIRA’s Agile Kanban to support daily Station Meeting

Team members hold daily stops around the contents of the Active Sprints panel, and when an Issue status is updated, it is dragged to the specified column.

  • Iteration tasks are performed in the Active Sprints panel of the Agile Kanban, where each Issue appears as a card in the panel column and can be dragged and dropped to update status;
  • After clicking Finish Sprint, the unfinished Issue will be automatically returned to the Backlog to be processed.
  • You can set the properties to be displayed on the card, such as handlers, test leaders, initial estimates, and so on, using the panels-configutions-card layout.

【 Key Graphic 】

9.4 meeting

1) Summary meeting — Use JIRA statistical reports to support summary meeting

JIRA agile management has a wealth of reports and statistics plug-ins, time and progress tracking, Issue analysis, prediction and management, test reports and other aspects to provide data report display functions. Take burnout diagram and velocity diagram for example, as shown below.

  • The burnout chart shows the progress of the work. Ideally, as the rest of the work is done, the curve burns to zero. It can be presented in terms of remaining time, estimated time, story points, progress, etc.
  • The velocity chart reflects the trends generated by the team, showing the number of story points the team planned to deliver versus the number of story points that were actually completed.

Issue data authenticity is the premise of analysis.

【 Key Graphic 】

9.5 Product quality management

1) Product quality management — Use JIRA’s built-in Dashboard and Applet to support product quality management

[Summary] Create the team’s JIRA Dashboard to manage various problem types during product development and cover all phases of the problem life cycle. Add the Applet, select 2-dimensional Filter Statistics and Pie Chart, and associate the data by setting the filter.

【 Key Graphic 】

Ten, recommended plug-in

  • Tempo – project management plug-in, time statistics, etc.
  • Synapsert – Test Case Management.

Q & A

Q: Is it necessary to adopt standard agile management?

A: The standard agile management members have high quality requirements and can start with part of agile. If it can be applied to the current environment, start implementing it and make it valuable. At first, it doesn’t matter how agile you are, it matters how you solve your team’s problems and status, and deliver on your goals.

Q: What are the obstacles to making the Agile transition?

A: When the traditional waterfall model becomes agile, the way of thinking and working changes. At the beginning there will be a lot of people wondering if Agile is better off than it is now. When Agile is implemented, first of all, it is important to identify the current problems that have been solved, and second, it is necessary to enhance the awareness of team Agile through ongoing training.

Q: How do you create a team atmosphere?

A: At the early stage of the agile transition, select students who are relatively active to participate in the formation of the agile team and do not pursue perfection too much. It is important that the first two iterations succeed, first in shape and then in spirit. Three praise every day, good performance of the students, the station will be timely praise, do poor to guide. Summing up the meeting or technology sharing, you can prepare some gifts, fruits, snacks, etc., to create a relaxed atmosphere, honest feedback, mutual discussion, mutual promotion.

Develop reading: four common development patterns and their advantages and disadvantages of contrast | IDCF

From 3355 to management metrics, learn to practice Scrum, read this article! | IDCF

Source: Cloud stack technology CSTC

Author: Geekwolf