HeaderSIS.jpg

IS480 Team wiki: 2015T2 6Sigma final wiki

From IS480
Jump to navigation Jump to search
6Sigma Logo.png

Home

About Us

IS480 Management System

Project Management

Project Documentation

Home Midterm Finals

Documents

In A Nutshell

Project Management

Functions achieved


Iteration Module Function Description Confidence Comments
1 Student Module CRUD Student Profile Allows students to CRUD their profiles. 1 -
Team Module CRUD Team Profile Allows a student to CRUD a team profile. 1 -
CRUD Team member Allows a student to CRUD team members. 1 -
General Module SSO Allows all users with SMU domain credentials to login to the system. 1 Some faculty members were still unable to SSO into our application due to the different user groups assigned to each faculty. We quickly resolved this by liaising with IITS to obtain all SIS faculty user groups
2 Faculty Module CRUD Faculty Allows faculty to CRUD their profiles. 1 -
Sponsor Module CRUD Accounts Allows new sponsors to request an account and propose a project. 1 -
Login Allows external sponsors to login as they do not have SSO accounts. 1 -
3 Project Module CRUD Projects Allows sponsors to CRUD projects for students to take 1 -
4 Project Module CRUD Project Teams Allows sponsor to approve or reject teams for their projects. 1 -
Team Module CRUD Project Status Allows the course coordinator/supervisor to update the status of the team’s project. (i.e. accepted or rejected) 1 -
Coordinator Module CRUD Term Allows the Course Coordinator to CRUD terms in the system. 1 -
5 Faculty Module Assign Supervisor/Reviewer to Team Allows Course Coordinator to a specific supervisor and assign him to a specific team manually. 1 -
Coordinator Module Suspend Team Suspend the team users so that they will not be a nuisance to the other users. Team will be unsuspended once the Course Coordinator deemed its ok. There is a user status attached to all the users (active/ suspended) which is only viewable by the admin. 1 -
Coordinator Module Assign Sponsor Role Course coordinator can assign sponsor roles to faculty. 1 -
6 Project Module Request Project Approval Allows students to request the sponsor to accept the team for the project. 1 -
Team Module CRUD Proposal/Mid- Term/Final Review Allows course coordinators, supervisors, reviewers and sponsors to add their proposal/mid-term/final reviews 1 -
Project Module CRUD Project Details/Documents Allows team to use the website as a replacement for wiki for their project. 1 -
7 General Module Download statistics User must be able to download IS480 statistics. 1 -
Search Module Search Student / Faculty / Project / Sponsor / Team Search for Student / Faculty / Project / Sponsor / Team based on what user entered into the search bar so that he can retrieve the information 1 -
8 General Module Generation of Email to Sponsors Generate an email to sponsor upon signing up for the system 1 -
9 Analytics Module Cosine Similarity Index Use of algorithm to find out the similar teams in IS480 based on Technologies Used, Industries and Project Type. 1 -
10 General Module View Statistics Displaying of statistics through the use of NVD3 Charts 1 -
Logging Logging of important information for accountability purposes 1 -
11 Scheduling Module Generating of CSV File format to suit scheduling system. Generating of CSV File format to suit scheduling system for integration purposes. 1 -
General Module Send notifications to users Generates a list of email via the system when there are important announcements to make. 1 -




Planned Schedule during Mid Terms

6Sigma Midterm Schedule.png

Actual Schedule

6Sigma Timeline.png

Issues Faced And Reasons for Change in Schedule

User Tests

User Tests
Event Previous Date Re-scheduled to Re-scheduled date
Sponsor Test 1 2 Jan 2015 Faculty Test 30 Jan 2015
Student Test 1 12 Jan 2015 Student Test 30 Jan 2015
Student Test 2 2 Feb 2015 User Test 2 12 Feb 2015
Faculty Test 2 9th Feb 2015

Changes in Scope

Removal

Function Mitigation towards schedule
Manipulate Statistics
View notifications


After our mid term presentation, our sponsors suggested that more emphasis should be placed on the grading function as the faculty members would be using the grading functionality for grading in the final presentations.

Due to our tight schedule, we felt that more time should be allocated to the enhancement and fixing of the grading module such that it is well tested and usable enough for faculty members to adopt the IS480 Management System II for grading. As such, we have decided to drop the manipulate statistics and view notification functions as our team perceived this to be of little value add to our sponsors.
During our 11, 12 and 13th iteration, extensive user tests would be conducted on the faculty members and the grading module would be improved as well.
Audit to Logging

We've also scaled down the Audit functionality to logging. This is also done to cater more time for extensive testing and enhancement of the grading functionality. The logging function would only log important tasks performed by users for accountability purposes.
During our 11, 12 and 13th iteration, extensive user tests would be conducted on the faculty members and the grading module would be improved as well.

Project Metrics

Schedule Metrics

We've adopted the following schedule metrics guidelines to help us track the progress of our project.
6Sigma Schedule Metrics.png


6 Sigma Schedule Metrics timeline.png
Iteration Planned Days Actual Days Score Actions Taken
1 14 14 100% None. We are on schedule
2 14 14 100% None. We are on schedule
3 14 13 107% Add one day to buffer
4 14 14 100% None. We are on schedule
5 14 16 87.5% As we previously had an increase in buffer day from iteration 3, this resulted in a deduction of 1 day from our buffer. For more information on the problems and solutions for this iteration, refer to the "Issues Faced" tab.
6 14 14 100% None. We are on schedule
7 14 14 100% Decided to push Manipulate Statistics to further iterations. For more information on the problems and solutions for this iteration, refer to the "Issues Faced" tab.
8 14 14 100% We completed the sending of email notification to sponsors. However, other notifications would be pushed to further iterations such that we can focus on Angular Material. For more information on the problems and solutions for this iteration, refer to the "Issues Faced" tab.
9 14 14 100% None. We are on schedule. However, it is important to note that there were still many bugs in this iteration, which is due to the Angular Material UI change

Bug Metrics

6Sigma Bug Metrics.png
Iteration Score Notable reasons Actions Taken
1 26 - Stop current development and resolve the bug immediately. However, as we completed the functionalities early, we managed to solve the bugs before the end of iteration. Hence, project was not rescheduled
2 6 - Use scheduled debugging time for debugging
3 30 - Stop current development and resolve the bug immediately. However, as we completed the functionalities early, we managed to solve the bugs before the end of iteration. Hence, project was not rescheduled
4 35 - Stop current development and resolve the bug immediately.We managed to solve the bugs before the end of iteration. Hence, project was not rescheduled
5 95 Previously, we had resource files (File containing end points) which groups all business functions together, regardless of the role of the executor. Our team foresaw that maintainability was going to be a problem in the long run with the adoption of this structure.

A major overhaul of codes was done in this iteration, and hence, the high bug count.
Stop current development and resolve the bug immediately. We are unable to complete bug fixing on time, and hence, we decided to use up 2 days of our buffer. Currently, we are left with 5 days of buffer after this iteration.
6 30 - Stop current development and resolve the bug immediately. We managed to solve the bugs before the end of iteration. Hence, project was not rescheduled.
7 42 It was evident that the basic core functionalities of our application was still not up to standard, and the basic functionalities require more work to be added on. Apart from that, the user test was to be conducted 2 weeks’ time, on Jan 30th. Stop current development and resolve the bug immediately. As too many funactionalties was breaking at this point in time, we decided to reschedule "Manipulate Statistics" to later iterations. Click HERE to find out more
8 75 We decided to revamp our UI to adopt the best practices and principles of design through the use of Angular Material. As such, there were many UI bugs which were discovered with the re-designing of our UI. Stop current development and resolve the bug immediately. Click HERE to find out more about the change management plan for Angular Material
9 80 We decided to revamp our UI to adopt the best practices and principles of design through the use of Angular Material. As such, there were many UI bugs which were discovered with the re-designing of our UI. Stop current development and resolve the bug immediately. Click HERE to find out more about the change management plan for Angular Material

Risks

Risks

6Sigma Risk Table.png


We've classified the risks we've identified into 3 categories: A, B and C.

'A' risks need the most attention and most well developed mitigation or recovery strategies,

'C' risks can occur but deserve the least amount of planning.


Top 3 risks identified
Risk Type Risk Event Occurrence Impact Category Mitigation
Adoption Risk Our system might not be well received by the IS480 Community for usage and efforts to capture user's data for analytics might fail High High A We intend to roll the system out in week 7, such that the next IS480 Batch can start using our system. Also, our team would be conducting numerous user tests and survey to improve usability.
Regulatory Risk Analytics and statistics used in this project may require the use of personal data and may violate the Personal Data Protection Act (PDPA). High High A The use of any personal data will be declared to the sponsor and all data will be protected from unauthorized access/use.
Technology Risk As mediawiki is highly unfavorable to crawling, crawling efforts might fail High High A The development for learning analytics is kept to the end so as to cater time to manually extract data in the event the wiki is uncrawlable.


Mitigation

6Sigma Risk mitigation.png

Technical Complexity

6Sigma Technical Complexity.png

Learning Outcomes

Link to our Knowledge Based Contribution :here

6Sigma Learning outcomes.png