-
Notifications
You must be signed in to change notification settings - Fork 3
Iter4 Release
This iteration is intended to create the final version of the product - which means that the product if finished and has passed successfully the public testing phase
- Test the application with real users
- Upload the application to the app store and google play
- Fix bugs that the users found
- Add notification for new events
The areas in the product are distributed as follows:
- Eliyah Weinberg will be responsible for iOS testing and bug
- Odelia Ivginehaz will be responsible for bugs in theinformation page and all its inner tabs
- Chanan Merari will be responsible for bugs in the home page and the admin panel and general management
- Daniel Lifshitz will be responsible for bugs in the gallery page
- Lior Vaknin will be responsible for all server side and general ionic bugs
The project tasks and their matching iterations and priority can be found in the issues page The current iteration issues can be found here and here
The main project Kanban board can be found here
The iteration estimation is set in the milestone
The product at this point includes all the features for the final product after they have been tested and remastered:
- All the features from the previous iteration
- Notifications for events
- Bug fixes
- The application appears on Google Play
The product can also be seen in our live deployment
The overall work with the organization was very productive and the Beta testing held with their assistance was a success. Minimal fixes were discussed and integrated to the product during the testing phase, mainly in the information page area. Problems were encountered in the iOS area of the application due to Apple refusal to acknowledge the application as an NGO organization product. The organization was provided with the necessary information to handle the publish process to the app store since the developer team will no longer support the product from this point. The open source code was also presented to the organization in case they wish to further develop it independently.
The iteration generally didn't require any big code changes and the team was passively monitoring user feedback, thus the iteration didn't require much work from the team and any retrospective conclusions will be rather irrelevant due to the nature of the iteration. Broadly speaking the iteration went smoothly and the Beta testing provided the needed feedback to perfect the product.
Code review is shared across team members both verbally and on each issue (if needed), any remark that was made during the iteration on the quality of the code can be tracked in the iteration issues
© Copyright 2018 TeamAwesome | Privacy