S.H.I.E.L.D Midterm Wiki
Revision as of 19:09, 2 January 2019 by Sygan.2016 (talk | contribs)
Contents
Project Progress Summary
Project Management
Project Status
Project Schedule (Plan Vs Actual)
Planned | Actual |
Project Metrics
Post-Acceptance Burndown Charts
Burndown analysis:
Although our number of story points decreased post-acceptance, we were still able to complete the tasks we set out to do at the beginning of each sprint. With the exception of refining our analytics model which is a recurring task, our user stories and tasks were all completed on time. Our burndown values only decrease when a full user story or task is completed, which is why our values decrease sharply and at the end of a sprint.
Project Risks
Technical Complexity
Quality of Product
Intermediate Deliverables
Stage | Specification | Modules |
Project Management | Minutes | Internal: Minutes 4 - 11 Sponsor: Minutes 4 - 5 Supervisor: Minutes 5 - 7 |
Metrics | Midterm Bug Metrics Midterm Sprint Velocity | |
Analysis | Use case | Midterm Use Case |
Design | ER Diagram | Midterm ERD |
Architecture Diagram | Midterm Architecture | |
Testing | User test plan | User Test Design Document |
Deployment
Deployed Dashboard: azulguard.fun
Login Credentials:
Username: carrie
Password: 789encrypt
Testing
User Testing | Date & Time | Venue | Number of Participants |
---|---|---|---|
User Testing 1 | 13 November 2018, 0900-1000 | NTUC Health Cluster Support @ Bukit Merah | 8 Case Managers |
Reflection