HeaderSIS.jpg

IS480 Team wiki: 2017T1 Renew Midterm Wiki

From IS480
Revision as of 22:48, 27 September 2017 by Tessatan.2015 (talk | contribs)
Jump to navigation Jump to search
Renew.png


HOME

ABOUT US

PROJECT OVERVIEW

PROJECT MANAGEMENT

DOCUMENTATION


Project Progress Summary

Deployed Site Link

Link here!

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

Midterm Scope Old.png


Actual

Midterm Scope New.png


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 Changes

Planned (from Acceptance)
Renew Timeline 10Aug Ver 3.png
Actual
Renew ScheduleChangesHighlighted.png
Changes since Acceptance:

Change(s) Reason(s)
♦ Midterms date is finalised

♦ Date where website goes live was pushed forward.

♦ Third party module is being replaced by Blog module
♦ Booking of midterms was opened.

♦ This is suggested during the acceptance presentation to ensure more data can be collected.

♦ Change in sponsor's needs and decided to remove the idea of a third party module, and instead add a blog module.


Project Metrics

Task Metrics:
Renew MidtermTaskMetrics.png

Bug Metrics:
Renew MidtermBugMetrics.png

Project Risks

Technical Complexity

Quality of Product

Intermediate Deliverables

Deployment


Testing

Reflections


Team Reflection

Individual Reflection