Release 2 review
We arranged a review meeting after the presentation video was posted, and the main purpose was that did everyone was satisfied with the work we did in last release.
In general, we had a good practice as an agile team and got a good presentation. Besides, we set a huge scope of release 2 and that was stressful to everyone and had less passion after the release. Finally, we got replies from the customer.
At the end of the meeting we discussed commits on GitHub: how frequently should we push commits to the branch, we decided to commit frequently includes small changes but push to the branch if necessary.
Phase 2 (Alpha release) Sprint 5 & 6 conclusion
We did have a good performance during the sprint 5, but not in sprint 6, everyone needs time to adjust themselves and came back to work, and learn how to manage time especially during the exam period. But the result is positive, we got full AI mode, the online server is working, hardware can talk to the server.
Phase 2 (Alpha release) Sprint 3 & 4 conclusion
The second overview, the conclusion of sprint 3 and 4.
- Did we achieve the improvements which were clarified in the last review meeting?
- What went well in the sprint 3 & 4?
- Anything we did not good?
- What could be improved in the next two sprints?
Based on the performance of the last two sprints, we nearly reached improvements which were defined in last overview meeting but sub-tasks for each backlog still unclear in this two sprints, so in next sprint, it still needs to be improved.
Phase 0 & 1 conclusion
Phase 0 & phase 1 conclusion results:
Did well: what did team or individuals does well in phase 1?
Anything bad？what team or individuals does not well in phase 1?
What did you learn? what did you learn in phase 1?
Improvement in the next two sprints: what should we improve in the next two sprints?
| Did Well | Anything bad？ | What did you learn? | Improvement in the next two sprints |
| Nothing did well | we didn’t apply the skill we learn from ASDP & ASMP | using Adobe xd | Work hard and Try hard to cover the stuff we didn’t cover in last phase |
| Good present, good job during phase 1 | Tunjing didn’t heard wenyu advice and draw the db schema | Planning release is a huge problem | user friendly UI ? |
| Tough phase 1 was gone | self learning and research we do is not enough | I learn we will fail this module | React native |
|
Zero knowledge on react native | How Arduino works | Plaing sptints sub-tasks |
| Slides, didn't include the requirements and too many words | i learn react native is a good framework | YOLOv3 | |
| We didn’t clarify the requirements and distribute to MoSCoW as soon as possible | GIS, EPA infor | ||
| hard to get together after the daliy meeting, sometimes the meeting is too late | Comparing story point is difficult | ||
| Did not make the UI user friendly enough | planning sprint is a disaster | ||
| some times we got less passion when we discussed something | building Mahara collections | ||
| Can't get components at time due to some component out of stock | How to use YOLOv3 and it's advantages and disadvantages |
Release Journals RSS
Release Journals start from 15/10/2020
Start from 09/04/2021 to 22/04/2021
Sprint Achievements:
1. Mobile Application: Reset/Retrieve password, display sample history by date, show distance between river and user current location, add team logo
2. APIs: Reset password, modify sample history, add the distance of river API
3. Testing: Deploy Application on Google play (open testing)
Start from 29/03/2021 to 07/04/2021
Sprint Achievements:
- Mobile Application: Review Sample Screen Update, fix duplicate Insect Input, Retrieve/reset the password, fix infinite Loop In Home Screen
- 2. APIs: Change The Model and API accept current location
- 3. Web site for admin: Adding a filter to the admin site data, Produce CSV file to select data
- 4. Testing: Deploy Application on Google play (still in internal testing phase)
Start from 12/03/2021 to 24/03/2021
Sprint Achievements:
- UI Bug fixed: back button alert bug, empty sample score, the show method of selection of uploading image to ai model
- UIs: display weather, terms and policy conditions, modify UI layout, upload insect photo by users
- APIs: API for environment image and insect image which are uploaded by users
- AI: Let AI Model Recognize Number and Length of Tail
- Web site for admin: apply user group to Activity Map, improve UI of admin web, Showing Image Gallery
Start from 05/03/2021 to 10/03/2021
What we have done?
1.Mobile UI:
- New screen: Report Problem let the User Able to Modified AI Model Feedback Result
2. Hardware: PowerSupply for Hardware
3. Server：Set CD for server on GitHub action
4. AI Model: AI training image
5. Admin website: Putting the data on the map in the Admin website, and toggle display style
6. APIs testing && User testing: Continues API test, non-professional users phone call interview (Feedback from testers)
Sprint 9 starts from 12/02/2021 to 17/02/2021 we planed Beta release with new features and backlogs with scores in Scrumwise.
Sprint 10 Starts from 18/02/2021 to 25/02/2021
Sprint Goal: Changing Whole Taking Sampling Flow
Sprint Achievements:
1. UIs: A new flows and new screens on Mobile app: app introduction->survey page->taking surrounding environment photos, also add safety guide for new register.
2. APIs: Accept River Details API , Modify scoring API to return result for each insects Group
3. Web site for admin: Login Page, hardware Spot Tracing On Google Map
4. Hardware with app: show hardware into Spotting Map
- «Previous page
- 1
- 2
- 3
- 4
- »Next page
Gathering ideas(30/9/20 - 07/10/20)
Geathering ideas from each member, and have a descussion about thoes ideas, including the concept, description, technique,functionalities, target user, advantage, disadvantage/Difficults.
At the same time we also disscused the roles for each member, each member got a main role and 1 or 2 sub-roles.
We arranged 2 meetings during the period, the first meeting we collected ideas and record them into a excel form (ideas sheet in shared link) .
The second meeting we rearrange the roles(roles sheet in shared link) and gave the points(1-5, 1 means do not recommand to do this idea, 5 means strongly reconnamd to do the idea) then got a rank for 9 ideas.
the details can be seen here: CCCMI ideas and roles (the link will keeping updating) or you can download the current version from attachement.