HeaderSIS.jpg

IS480 Team wiki: 2015T2 6Sigma Issues Faced

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

Home

About Us

IS480 Management System

Project Management

Project Documentation

Schedule Metrics Task List Risks Issues Faced User Tests & Surveys


Iteration 5


Iteration 5 : 8 December 2014 to 23 December 2014
Issues Solution Mitigation towards schedule
Previously, we had resource files (File containing end points) which separated the different roles from their business functions (Eg: Faculty's business functions on teams were classified into FacultyTeamResource). this did not conform the the REST API standards, and resulted in repeated codes.

This resulted in many different resource files, and it was difficult to trace code and fix bugs, resulting in delay. This has also frustrated a lot of teammates.
Our team foresaw that maintainability was going to be a problem in the long run.

It was decided for all business functions to be grouped together under a same resource file, with different roles executing different tasks through the use of If-Else blocks. Eg: Functionalities involving teams would be classifed under TeamResource. This resulted in a delay of 3 days. As we previously had an increase in buffer day from iteration 3, this resulted in a deduction of 2 days from our buffer.
Our team was still new to the technology of JPA, and we developed our business logics in the resource files.
This resulted in repeated codes.
After researching on the best practices online, we discovered that business logics were best to be encapsulated in the service files, in order to achieve a Service Oriented Architecture. This resulted in refactoring of business logics into the service files.

Iteration 7


Iteration 7 : 9 Jan 2015 to 24 Jan 2015
Issues Solution Mitigation towards schedule
After much discussion with sponsors during the sponsor test on 16th Jan 2015, Fiona has suggested to the team that it would be advisable for the team to remove functions which are of less priority and without much value add such that more can be achieved by focusing on the core functionalities / functionalities with the most value add. in order to find out whether this would be much of a value add to our main target users (Students), our team has actually conducted a survey and we’ve summarized the results in the surveys page HERE 6Sigma has decided to remove CRUD Comments, iterations and the blue front page implantations from our project scope.
After the last sponsor meeting which was held on 16th Jan 2015, 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.

Our team felt that it would be wiser to prioritize on fixing the basic core functionalities of our application before moving on to tackle secondary functionalities.

Therefore, our team felt that more effort should be dedicated to the core functionalities to ensure the application is stable enough for user testing on 30th Jan. As a result, our team has decided to postpone manipulate statistics to further iterations. Audit Trail, View Statistics (Previously scheduled in iteration 8) and Manipulate Statistics (Scheduled in Iteration 7) would be spread across the remaining iterations with learning analytics removed from the scope. Also, the extra 5 days of buffer would be used, if there's a need.