Preface
MOMO cloud agile project management integrates agile and DevOps ideas, and opens up the entire end-to-end agility from requirements, R&D, testing, operation and maintenance, and operations. In practice, through operation and maintenance automation, the products developed by the Scrum agile team are quickly launched online, and through timely operations, feedback to the agile team for direction adjustment.
Demand collection
Demand collection is mainly through the following channels: brainstorming, user research, user feedback, competitive product analysis and data analysis. Of course, there are also boss needs, operational needs, growth needs... and so on.
Brainstorming
Invite people from different roles in the team such as product, operation, vision, technology, etc. to participate. The number of people should not be too large. Revolve around a core issue, express your opinions freely and not comment on right or wrong. The other is to designate someone to make the minutes of the meeting to facilitate the review after the meeting.
User research
User surveys are generally conducted in three ways: questionnaire surveys, user interviews, and usability tests. Both questionnaires and user interviews require targeted design of questionnaires and search for high-quality users, while feasibility testing requires specific functions to find specific groups of people to test and collect feedback.
customer feedback
Users are generally lazy and will not give us positive feedback. All we reserve a feedback portal in an obvious place on the platform. In addition, we organize reward questionnaires from time to time to collect user feedback.
Competitive product analysis
First, it is necessary to determine the target competing products by analyzing and comparing a large number of competing products, and secondly, comparing the advantages and disadvantages between the products. Compare the target strategic direction, user selection, and product strategy. Compare product feature points. Compare how competing products do user experience, how to deal with logic, interface levels and details, etc.
data analysis
MOMO Cloud has carried out application-level and functional-level burying work for the R&D system, providing a R&D process measurement system, which is convenient for managers to locate problems, analyze problems, and make conclusions by observing data and analyzing data to provide data support.
Preparation Phase
Choose a suitable agile project management tool. We use JIRA for project management, create Scrum process projects, join project members, and create panels and swimlane configurations.
After PO creates requirements collected from online feedback, offline interviews, competitive product analysis, brainstorming and other channels into the product Backlog, the priority of requirements is updated by PO in real time and reviewed regularly to ensure "doing the right thing".
Planning stage
PO will list the reviewed requirements into the product [Demand Kanban], convert the requirements according to the priority and the online plan, and convert the requirements into Epic and Story, prioritize them into R&D [R&D Backlog], and then create it by the Scrum Master This Sprint is divided into tasks and subtasks at the demand kick-off meeting. The estimated R&D time and story points are evaluated and assigned to other R&D personnel in the team. After the team confirms that they are correct, the R&D cycle and R&D goals are determined and the Sprint is opened.
development stage
The Scrum Master is the core role of this stage. It is necessary to ensure that the entire team "does things right" with high quality and efficiency:
Based on the iterative Kanban, the team organizes daily stand-up meetings to update team members' R&D progress and task status to ensure timely delivery and launch.
When developers submit code, they initiate a peer review. Afterwards, the Scrum Master will conduct a code review, confirm that there is no problem, and merge it into the version backbone.
Automated static code inspection tasks are performed regularly every day to check the coding quality, coding problems, cyclomatic complexity, repetition rate and other issues before they are allowed to build packages.
Through automated continuous delivery pipelines, continuous construction, continuous deployment (including automatic scripting, comparison), continuous testing (automation of functions, interfaces, performance, reliability, etc.), continuous monitoring can be realized, and the operation and maintenance end can be manually operated The time is reduced to within 20%, and the full-featured team can focus on business delivery, significantly improving efficiency and product quality.
When the code is submitted, note the Story ID according to the specification, and then the code can be associated with the corresponding requirement. When creating test cases and defects, you also need to associate requirements, so that the two-way traceability of "requirements-code-use cases-defects" is realized.
Feedback phase
The feedback phase is mainly after the iteration goes online, the team will review and summarize internally, and organize the review and summary meeting of the current iteration. Acceptance is carried out by PO to ensure that product functions are consistent with requirements.
If the transfer test returns a failed problem, the Scrum Master needs to coach the person responsible for the problem to backtrack, and the quality backtracking meeting of the entire team is required. The focus of the meeting is to analyze the root cause of the problem and identify the points of improvement that can be implemented in management, process, technology, and tools. And these problems require implementation in the latest iteration to avoid the problem from recurring.
View the progress of demand delivery through iterative demand statistical reports and burndown charts. The retrospective summary will be recorded as a retrospective so as to facilitate improvement in the next period in conjunction with the new plan.
to sum up
Agile demand management is a culture. In agile practice, each team has its own characteristics. You can choose the agile process and practice that suits you according to the actual situation to achieve a high-quality and efficient development collaboration model.