Difference between revisions of "IS480 Team wiki: 2017T1 Renew Midterm Wiki"
Jump to navigation
Jump to search
Line 218: | Line 218: | ||
<h4 style="background:#CAD4EC; padding: 10px; line-height: 1em; text-indent: 0px; font-size: 18px">Project Metrics</h4> | <h4 style="background:#CAD4EC; padding: 10px; line-height: 1em; text-indent: 0px; font-size: 18px">Project Metrics</h4> | ||
− | For a complete breakdown of how we calculated our metrics, do take a look at [[IS480 Team wiki: 2017T1 Renew Metrics|Renew Metrics]]<br/> | + | For a complete breakdown of how we calculated our metrics as well as for more information pertaining to our metrics, do take a look at [[IS480 Team wiki: 2017T1 Renew Metrics|Renew Metrics]]<br/> |
<b><u>Task Metrics:</u></b> | <b><u>Task Metrics:</u></b> | ||
Line 229: | Line 229: | ||
<br> | <br> | ||
<h4 style="background:#CAD4EC; padding: 10px; line-height: 1em; text-indent: 0px; font-size: 18px">Project Risks</h4> | <h4 style="background:#CAD4EC; padding: 10px; line-height: 1em; text-indent: 0px; font-size: 18px">Project Risks</h4> | ||
− | + | For a full list of our risks their status along with the mitigation strategies employed, do take a at our [[IS480 Team wiki: 2017T1 Renew Risk Management|Risk Management]] | |
<h4 style="background:#CAD4EC; padding: 10px; line-height: 1em; text-indent: 0px; font-size: 18px">Technical Complexity</h4> | <h4 style="background:#CAD4EC; padding: 10px; line-height: 1em; text-indent: 0px; font-size: 18px">Technical Complexity</h4> |
Revision as of 13:19, 28 September 2017
Project Progress Summary
Deployed Site Link
Midterm Slides
Link here!
Deployment Progress
- Current Iteration: Iteration 8
- Iteration Period: 9 October 2017 - 22 October 2017
- Major Milestones: Midterm Presentation (10 October)
- Functions: Blog, Roster
Project Highlights
- Multiple changes in scope since our original start, even after acceptance.
- The design aspect of our public facing website is constantly changing.
- Related to the above point, design is equally important to functionality as our client is a fashion retailer thus necessitating a different approach to building the project.
- Our end client has changed constantly throughout the project from the IT director to the IT department to the HR director to the HR department.
- We had problems deploying to the server provided by the client and learnt about the server provided to us.
- The team is consistently thinking of ways to value add to our project, even up to midterms.
Project Management
Project Status
Module | Status | Confidence Level (0-1) | Comment |
---|---|---|---|
Job | 100% | 1 | Nil |
Admin | 100% | 1 | Nil |
Account | 100% | 1 | Nil |
Welfare | 100% | 1 | Nil |
Engagement | 100% | 0.95 | There are concerns arising from our UAT regarding the design. |
Reward | 100% | 0.9 | There is a need to integrate with an existing POS system we have no control over. |
Reporting | 100% | 0.9 | Suggestions to improve this design-wise was raised in both UAT and supervisor meetings and the design has been altered but has not gone through UAT. |
CMS | 90% | 0.8 | Content is still being changed by the Client. |
Communication | 85% | 0.75 | Not tested in UAT. |
Blog | 0% | 0.5 | Future Development |
Roster | 0% | 0.5 | Future Development |
Project Scope Changes
Planned
Actual
S/N | Function | Module | Function Type | Type of Change | Reason |
---|---|---|---|---|---|
1 | a. Viewing of Exclusive Deals b. Viewing of Leave Entitlement |
Welfare | Secondary | Addition of Function | Request from Client. |
2 | Email Previous Applicants of New Jobs | Communication | Secondary | Removal of Function | Request from Client. |
3 | Beeline | Third Parties | Good-To-Have | Removal of Module | After discussion with the Client, what Beeline can offer does not meet the Client's requirement hence the request to remove it. |
4 | a. Blog for Staff to Upload Newsletters b. Ability to add videos to posts |
Blog | Good-To-Have | Addition of Module | Request from Client. |
Project Schedule Changed
Planned (from Acceptance)
Actual
Changes since Acceptance:
Previous Iteration | New Iteration | Change(s) | Reason(s) |
---|---|---|---|
Iteration 6 | Iteration 7 | Job (III) module was pushed to Iteration 7 | Underestimated the time needed to complete this module due to the notifications task. |
Iteration 7 | Iteration 7 | Date where website goes live was pushed forward | This was suggested during acceptance presentation to ensure more data can be collected |
Iteration 8 | Iteration 8 | Midterms date was finalised | Booking of midterms was opened |
Iteration 8 | Iteration 8 | Third party module was replaced by Blog module | Change in sponsor's needs led to the removal of the planned third party module, and the addition of the blog module |
Project Metrics
For a complete breakdown of how we calculated our metrics as well as for more information pertaining to our metrics, do take a look at Renew Metrics
Task Metrics:
Bug Metrics:
Project Risks
For a full list of our risks their status along with the mitigation strategies employed, do take a at our Risk Management
Technical Complexity
Quality of Product
Intermediate Deliverables
Deployment
Tessa
Reflections
Team Reflections
Individual Reflections