This is sprint 2 . the work done by the individual Members
| Personnel |
Completed tasks |
| Haisong Ding |
Research and use of the Nokia Image SDK The effect of completing the render module, such as move, color filter Improvements and refinements to the MVVM UI |
| Qing Li |
Preliminary research on the render module Complete the zoom In/out effect based on the Nokia SDK |
| Xufang Luo |
Complete the selection of music, pre-defined work for clipping point extraction Deploy the SDK for face detection into the project |
| Dengpan Fu |
Parse files and functions required to implement all processes of the algorithm module Implement all interfaces to the render module |
| Fangzhou Luo |
Assist in researching the SDK of the render module Define the effect of the color filter |
| Yuchan Liu |
Scrum Master APP UI Design |
In the first sprint we set up a good app framework, algorithm part of the more complete research and code reading, the render part did some basic research and try on the basis of Our progress in this sprint is mainly due to the fact that the algorithm has completed all the basic functions envisioned, and can be connected to other parts of the operation; after a week or so of exploration and trial-and-error, the render module finally chose the Nokia Image SDK for a more reliable solution. Some of the effects of the definition are now implemented, and MVVM can also be successfully docked; The sprint does not focus too much on the UI beautification and tweaking of the sprint when it is more lean.
Now that we start postmortem and talk about the project Management Section, as the sprint pm, I think we have more experience with WorkItem's management than the previous sprint, so the burndown figure looks normal (for example, PS. It seems that TFS was hung up in the last Saturday, after a long period of time not to see the report, now can see the report but the two days of data has not been updated, in the first half of the sprint because the render part of the technical choice of many difficulties so increased workitem, progress is very slow, the latter half The progress is more ideal. In fact, now look at our WorkItem and the actual work situation, will find and can not be fully corresponding, the reason should be too much uncertainty in the early stage, the division of WorkItem is also very uneven granularity, so the more backward, the direction of development and expectations of the more deviated, There are many parts of the work content is not added to the item, a few days to finish a content only one item, and a short time to fix the item is also an item and so on, reflected in the report data is not too much rationality. Overall, this sprint is acceptable for our team to devote time and development to the project, and of course many technical issues have to be expanded.
Next, we'll talk about the technical part, and at the end of the sprint, there are still a lot of problems with our application and something that we expect to achieve but too late to implement:
The MVVM section also has video preservation, and the one or two lower priority interface implementations are not completed; algorithm now out of the effect is not as beautiful as we think, the distinction between style is not big; render now does not achieve the effect of the transition between pictures, The method of direct hard cutting is still used. Three parts Now there is a serious memory management, computing speed problem, rendering five or six images of memory exploded, these defects directly affect the quality of our application and user experience.
In the feature of this Sprint's inception, our mission is complete, with three different style image rendering videos (of course, this feature is really too coarse, and a lot of details are not defined, but also an experience and lesson).
in the next sprint, our goal is to complete the above mentioned content, focus on performance optimization issues, and strive to release our applications as soon as possible. Details of the WorkItem planning to be discussed .
"Review" postmortem of Sprint 2 and next planning