M1 post-mortem analysis report and summary

The M1 phase is over, we have done a whole group discussion on the M1 stage, and we summarize it here.

First, Imagine

Our vision is to develop a quick and easy Notepad app. From the user experience point of view, in the General Notepad app based on innovation, give users a different experience.

Of course, the idea of the emergence of a certain process. We had brainstorm ideas during the discussion, such as making a nostalgic game of snake, doing a common bookkeeping software. Finally, we choose from a convenient writing and practical point of view, we have chosen a quick Notepad app that everyone recognizes.

After deciding on the direction, we expanded some features for this idea, with the idea of allowing the app to include a shortcut button for the hover and lock screen interfaces.

Second, the design

After proposing this idea, we immediately began the design of the app. At that time, the task was handed over to two students, let them together to complete. They discussed the decision that one person is responsible for the general framework of the interface and the other is responsible for designing the details of each interface.

Two students spent nearly a week designing, followed by the second plenary meeting of our entire team. There was a small problem, because the design of the two students for the interface design have their own ideas, and not timely communication, resulting in some inconsistent design. After a discussion, we decided that we should first implement some of the most useful functions of the app, so we chose a more concise interface design. And for the slightly more complex design, we also recorded, ready for later to enrich the details. After the design of the interface was finalized, we discussed the design of the function and finally agreed on the team.

Third, the plan

We completed the preliminary design, we divided the various modules, and made the corresponding plans. M1 Stage Our plan revolves around "make a full-featured app" Unfold, want to realize the function is: text note, voice note, picture note, hover window function, search function. From the results, the planned work is basically completed, but it is a little pity that the function of the picture note is still in the debugging.

After a panel discussion to analyze the reasons, we believe that the problem mainly occurs in the high estimate of our development efficiency. When making a plan, we only separate the beautification interface from the production utility, without carefully pursuing the time required to develop, debug, and refine each function. For our app, each note is a separate module, with no reusable code between the modules, and no experience to follow. Production of each module should be from scratch data, knock code, out of the bug has no experience to follow, can only check information, try to modify, and then continue to debug, until the completion of this function. In this way, the production of each module is a challenge for us, which leads to too much of our task.

The main reason for this unscientific program is that we are unfamiliar with the development of Android, and now, after two weeks of development, we have come to understand the ease of the various functions of Android, and I believe the next stage will be able to develop a more reasonable plan.

Iv. Resources

The resources we need are mainly various pictures. Based on some previous experience in software development, we realized that it was not easy to get the picture resources, so we gave the work as a separate part to a team member. Now we think this is necessary because it saves the rest of our crew time so that they can devote themselves to the work of writing code.

V. Changes

After a team discussion, we realized that we did not manage changes to the software during the M1 phase, and when the developers made new features, they did not inform others in time. This also results in the release of our test reports with the latest version of the software. After discussion, we think we need to strengthen communication in the next phase of our work, paying particular attention to this change management to prevent the same situation from happening again.

VI. TEST Plan

In the M1 phase, we also have some shortcomings in the testing aspect. In the final test, we considered more functional tests to find bugs that were not found, and the tests for compatibility issues were not exhaustive. After observing the test results of the Sixsix team, we learned some experience. In the next phase we will use a number of test tools to perform a comprehensive and holistic test of the software.

Vii. model of the team

The size of our app's main code is similar to that of other modules, and there's a lot of work to be done in detail. For each of these modules, they are connected to the main code. Based on this feature, we have developed a special mode of work--to complete team tasks in pairs. Early, by a person to write the main code, others communicate with him to write the module code (hover window, search, new notes, set interface, etc.). Now that the main code is complete, the next stage we will convert the way, write the main code of the person in turn and other people to communicate more. This mode of work makes the management of the whole team easier, the responsibilities clearer, and the integration of all modules at a later stage can be done easily.

M1 post-mortem analysis report and summary