Difference between revisions of "IS480 Team wiki: 2016T2 Unition midterm"
Jump to navigation Jump to search
|Line 27:||Line 27:|
Revision as of 16:52, 18 February 2016
|Home||About Us||Project Overview||Project Management||Documentation|
- 1 Our Project Process Summary
- 2 Our Project Management
- 2.1 Project Scope
- 2.2 Project Timeline
- 2.3 Project Metrics
- 2.4 Project Risks
- 2.5 Technical Complexity
- 3 Our Quality Assurance
- 4 Our Learning Outcomes
Our Project Process Summary
There are a total of 13 iterations
- Current iteration : 8
- UAT 3 will be tested with actual users and volunteers in iteration 11
- Google Play Deployment to be done by 18 March 2016
Our Project Management
Changes in Project Scope
Highlights of Changes in Project Scope
- Post acceptance, multiple discussions were done between the team and our Sponsors to realign the project scope with their business requirements
- The aspect of "Booking an Appointment" with Clinical services and Therapists was change to email engagement to provide the communication between the user and the service providers
- The email function will be enforced to the Volunteer sign up option as well
- Logs of email engagements and as well as shopping cart logs are to be reflected in user account.
Change in Project Schedule
Highlights of Schedule Metric Scores
- Due to the team unfamiliarity with Wordpress, the initial special account access given to the team was not enough to allow the link between our App and Wordpress's database.
- Upon discussion with Sponsors, the team was granted higher access to tackle the Wordpress database challenge, however, the Wordpress site was down and testing could not be performed.
- Troubleshooting of the Wordpress site took up a lot of time and implementing the techniques from our research on Wordpress database was not smooth sailing.
- The massive delay resulted in the team's decision to re-scope and re-schedule after discussion with both Sponsors and Supervisor.
Highlights of Bug Metric Scores
- Integration of the Events with calendar view UI had contributed to most of the bugs in the iteration.
- Due to the adaptation of external resources on calendar view, developers in the team took some time to understand the codes before implementation, still major bugs occurred which the team took immediate action to rectify them.
|Risk Type||Risk Description||Consequence||Likelihood||Impact||Risk level||Mitigation plan|
|Technical Risk||Project team has no prior knowledge of Android mobile app and need to learn to use Android Studio||Schedule may potentially be delayed due to time spent on learning and our initial deliverables might be buggy||High||High||A||We will have researching and learning sessions before we begin our actual coding tasks and adopts code we learn strategy.|
|Project Management Risk||Requirements may change in the mid or after few iterations||Delay the current process of development and project schedule will be affected||Medium||High||A||Prior agreement with sponsor that major changes will not be addressed after confirmation on the agreement • Team to evaluate changes and to discuss with bother sponsor and supervisor to obtain the best case scenario|
|Project Management Risk||Failed to connect sponsors' WordPress database through Android application||Sponsors need to manage two separate databases with same content which cause extra work||High||Medium||A||Find out a stable way to get data from WordPress database. Get sponsors agreement to build a separate database if failed to use their data eventually|
|Project Management Risk||Difficulties to map all functions on ShenCARE website to mobile app to fulfil the requirement||The team may not deliver a product meet sponsors satisfaction||Medium||Medium||B||We will clearly state the scope of our project that we agreed with our sponsors. The project manager will also monitor the progress of the project closely to ensure that we stick to the agreed scope.|
|Project Management Risk||Unable to find enough users to test the application||Can not get sufficient feedback from users to improve current application||Medium||Medium||B||Contact sponsors and seek for their help to attract more target users to test our project|
|Project Management Risk||Team members unavailable during some development periods due to illness or unforeseen urgent issue||Can not get sufficient feedback from users to improve current application||Low||Medium||C||Deputy person in the specific role take the task first， if not able to complete the task split to other members|
Highlights of Technical Complexity
- Due to the nature of Android development, database connection with Wordpress would require HTTP REST requests to query data from its database
- In order for such HTTP requests to be established, plugins are to be in place in the Wordpress site to allow calling of such APIs
- However, off shelf plugins provide limited functions which may not fully suffice the needs of our App development, therefore, customization of the API was required
- With the instability of the Wordpress site and plugins versions, the team experienced a tough testing phase when establishing the database linkage
- Multiple attempts of editing the customization of the APIs was experienced to cater to the right data query and executions
Our Quality Assurance
|Project Management||Meeting Minutes||Meeting Minutes|
|Project Management||Risk Management||Risk Management|
|Design||Use Case Diagram||Use Case Diagram|
|Design||Architectural Diagram||Architectural Diagram|
|Design||Technology and Tools||Technology and Tools|
|Market Research||Market Research||Market Research|
|Testing||Testing Plan||Test Plan|
|Testing||Test Cases||Test Cases|
|Testing||Test Result||Test Result|