M Product Development log (3)-dashboard, build, template, and presentation

Z Jun soon sorted out the requirement template and put it on the Wiki for your reference. The requirements for each feature in the future should be filled in according to this template, in this way, the demand personnel can easily summarize the requirements when organizing the requirements. Projects on SVN have also been created by Xinbo. For a project on the m product, the sub-projects of the six modules are divided below. The entire R & D process is based on the previously tailored scrum process, which is iterated every two weeks. The presentation is held at nine o'clock every day to move your tasks on the panel, the only difference this time is that there is no test link, because it is only an alpha version, so the test link is weakened.

Build on a daily basis based on SVN. The main content is as follows:

1. CodeQuality Assurance (checkstyle, findbugs check)
2. Build the installation disk (Code installation disk build and script installation disk build <attempt>)
3. The daily environment deployment automatically updates the code disk to the demo environment. The database in the current demo environment directs to the developed database (Dev). After the time is ripe, the demo database will be stripped.

The initial version of the R & D process is as follows:

• First talk about the business (new) or refer to the previously completed functions (transplantation)
• The R & D personnel updated the task of this iteration to the list of tasks to be executed in the dashboard.
• Based on the requirement template, developers can create a function node page on the Wiki.
• R & D personnel move the task to the corresponding location on a daily basis.
• The developer updates the detail of the requirement discussion to the corresponding function page of the Wiki.
• The requirement personnel organize the latest requirements on the Wiki.
• The requirement personnel can log on to the demo environment to learn about the R & D process at any time.