-
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
The product will be delivered in two forms:
- The actual product will be delivered as an in store application
- The code and comprehensive documentation will be delivered in this GitHub repository
In this project, the team learned a few lessons to implement further in life in other projects and in work environments
- Solutions found in contradiction to the project director can be better than solutions provided by the director, and the team should always rely on their own intuitions as the actual developers.
- Limitation should always be presented to the organization at each meeting since as non-developers the client usually doesn't understand the difficulties present to the team
- Documentation is important only to a point at which no one will need it. The project documents should always be concise and accurate to the nature of their purpose.
Overall, the project worked very well and communicatios both inside the team and with the organization were good. The code was written professionally and the product was delivered with high standards. Improvements could have been made by including all the team members in even minor decisions for comprehensive feedback. Challenges were encountered in the form of external services integration such as Facebook and Firebase, but all challenges were consequentially resolved. The risk management table was accurate from the start and due to the risks being thought for the difficulties made by them were easier to handle. Tools such as Ionic and VS Code were very helpful for the ongoing development of the product. Work with the client was very productive and each meeting led to major improvements in the product. At this point, no further support for the product has been discussed.
Security concerns in the product were addressed by the team. for examples, security breaches in the admin panel were resolved and now editing the information is impossible for fake users by a server-side checkup. Also the Facebook API key for the gallery page is hidden in the server side and cannot be accessed for harmful operations.
The work process through the project was done in Agile. each iteration was 2 weeks and a meeting with the client was held at the end of each iteration. Commits were done to master branch to avoid big merges across the team and because of that some extreme programming principles were applied in the way of continuous integrations and frequent commits. This work process was perfect for the team n the way that it both set a boundary for features development time and gave us a feedback from the client every two weeks.
A full iteration was devoted for testing to make sure the product is delivered in the best form. Since two members of the team work in the industry as Automation Engineers and one member as an Embeded Developer testing was considered a crucial part of the development process and therefor was dedicated a full iteration. Testing was done both internally and externally as a Beta phase for the product.
The values of full communication among the team members were applied throughout the entire development process. Though some discussions should have been made more openly and grudges among the team should have not been bottled to the point of frustration the overall team work was done in a good respective way.
© Copyright 2018 TeamAwesome | Privacy