CODING provides your enterprise with software development management from concept to software development to product release. It helps your r&d team to clarify requirements, iterate, give feedback quickly and track project progress in real time until completion. At the same time, CODING also sets the corresponding workflow for each role in the R&D team according to the nature of their work, so as to help everyone get started quickly, help the R&D team, improve the r&d efficiency, and deliver software more efficiently and quickly.
Product manager permission Settings
With the beginning of digital transformation, more and more enterprises begin to use information management system to replace traditional office tools. In the process of transformation of one of the biggest challenges is how to set the permissions on the relevant information management, to ensure that employees of different functional departments can only use a specific function, browse the information related to their business, cannot do STH without authorization to view or modify permissions on above content, guarantee the accuracy, confidentiality, security, corporate digital assets.
Product Manager Default rights:
Demand management
Under the background of the age of the Internet, how to fast and efficient product development has become a problem, every company have to consider in the small and medium-sized team, product managers tend to assume the role of project manager for the overall project planning, by CODING the requirements management module and iteration to formulate product planning and responsible for the planning of maintenance and update. Product managers manage the full lifecycle of product requirements by creating projects on CODING. Through the visual presentation of the list, members can clearly understand the current status of the requirements collection task, such as “requirements collection”, “Evaluation”, “not adopted”, “design”, “development”, “testing” and “online”, etc.
Collect and manage requirements
The product manager will sort out the planned online functions, user feedback and market research results, and form a demand pool through unified induction of demand forms in demand management. At the same time, the product owner further analyzes the requirements in the demand pool and divides the requirements into technical problems, design problems and product problems according to the team habits. A series of sub-tasks are created for each requirement based on the complexity of the requirement. The more important the requirement, the more complete the requirement description. Requirements The collected requirement information can be customized based on the requirements. The product manager can add requirement type, Deadline, and Estimated Working hours to the requirements as the requirements change in the whole life cycle. You can also tag requirements with “features,” “Bugs,” “research,” and so on.
Make comprehensive statistics of key indicators to facilitate product managers to understand the overall progress of the project.
Requirements documents and prototype files
After the iteration planning is complete, the product manager can write a complete product feature document in the Wiki based on the requirements in the iteration. You can also upload and share prototypes using CODING’s file function. CODING’s file functionality and Wiki functionality provide r&d teams with built-in tools for document collaboration and team knowledge deposition.
Develop a release iteration plan
After the requirements are analyzed, the iteration feature in CODING is used to develop a release plan. At this point, the product team needs to hold product meetings with the R&D and design teams, during which the product manager prioritizes requirements, identifies requirements and defect tasks that need to be included in each release iteration, and sets the iteration cycle. A project can be divided into different iterations in the order of development.
Transactions contain requirements, tasks, and defects, and iterations provide complete overview capabilities that clearly show how transactions are progressing and distributed within each iteration.
Product acceptance
After features are developed and designed, they are functional tested by a test engineer and the relevant requirement/defect status is changed to “under test”. If the test fails, you can comment directly under the relevant requirements, give specific error messages, and forward the requirements to the product manager or development for processing.
If the test passes, it can be updated to the Staging environment, where the product manager can conduct acceptance of the product according to requirements. If the acceptance fails, the product will be sent back to the responsible person for negotiation on whether to roll back or resend the version. After the product manager accepts the test successfully, the product manager will inform the group that the test acceptance is complete, and the test notification o&M is officially launched.
Defect management
Problems found in the testing process and after the official launch can be summarized and unified in the defect management module of CODING, and priority can be listed as one of the sources of work in iteration. However, this should also be analyzed on a case-by-case basis. Defects with high urgency need to be fed back to the product for repair at the first time, while those with low priority will be arranged for repair in the next iteration. Defect management also has powerful statistical capabilities, including defect type, priority, module, discovery time, and so on.
Click now to start CODING quickly and deliver efficiently!