IS480 Team wiki: 2018T2 The Sailors MidTerms
Jump to navigation Jump to search
Project Progress Summary
1. Configured Bluehost Staging and Production Server, with SSL set up for both servers
2. Completed UAT 1 with 4 users in Sprint 10
3. Completed UAT 2 with 1 user who plays multiple roles (Super Admin, Admin, Surveyor) in Sprint 11
Project Schedule (Plan Vs Actual)
Planned Project Timeline
Actual Project Timeline
The Sailors Metrics - Refer to this site for Metric
|Risk Type||Risk Event||Likelihood||Impact||Mitigation||Learning Points & Remarks|
|Client Management Risk||There may be major changes in client requirements that require re-prioritisation and cause a drastic change in our planned schedule.||Medium||High||Our team will meet our client regularly to ensure that we are always on top of our client’s requirements to lower the risk and impact of future changes to requirements. We should be transparent with the client on the project’s progress and ensure the client remains up to date with the project progress.||This continues to be a risk because the Client requirements may be subjected to change in any stage of project phase. The changes would be less major and less frequent as the project draws closer to the end. However this means that changes should still be anticipated, and hence the team’s mitigation strategy is to meet the client regularly to ascertain that expectations and project requirements are aligned.
|Project Management||Team may perform inaccurate estimations on the efforts and time taken to complete functionality, due to inexperienced and inadequate knowledge in implementing new technologies. As such, time is allocated for research and learning new technologies before implementation of the functionality can be performed. Team members may have other commitments outside of their studies during school term.||Medium||High||Team should appropriately plan for buffer and review task regularly to ensure that the project is on schedule. The Project Manager must be duly notified if the deadline needs to be extended and re-prioritise.||This continues to be a risk because new requirements from the client may pose changes in our planned timeline and we will have to re-estimate and re-prioritise to ensure we can meet the client's expectation as well as the required deliverables for the module.
|Technical Risk||Team may be unfamiliar and inexperienced with implementing new technologies in the project.||Medium||Medium||Research will be carried out to understand how to implement new technologies appropriate for the project. Team members doing the research are expected to conduct share the knowledge session to educate everyone in the team.||This continues to be a risk because there is also a learning curve. Learning new technologies requires time before implementing it in the project.
|User Testing with Domain Experts||The users using the application require specialised domain knowledge about bunker surveying jobs, and thus adhere to strict standards of maritime industry practices in terms of form filling data and etc.||Medium||Medium||User Acceptance Testings should be carried out with these domain experts e.g. Lighthouse Marine Staff, Surveyor, Chief Engineer and etc to obtain qualitative and quantitative feedback.||This continues to be a risk, as there is a limited of domain experts which we can conduct user testing with.
Quality of Product
|Project Management||Project Timeline|
|Risk & Mitigation|
|Testing||User Acceptance Testing|
|Internal Regression Testing|
The Sailors Test Plan - The Sailor's testing session across all past sprints.
The Sailors Bug Log - List of bugs found across all past sprints through the Test Plan.