IS480 Team wiki: 2015T2 Starteur Midterm Wiki
Main Wiki | Midterm Wiki | Final Wiki |
---|
|
Planned | Actual |
---|---|
Major Changes
- Removal of Sort & Filter Students function from Batch Report module after evaluation and comments from educators
- Changed Automated Email Test Reminder as educators prefer to control the function rather than preset the number of days
View our Change Management Here!
Project Schedule
Schedule Highlights
There are no major changes to the project schedule. Functions were shifted around within the schedule due to difficulties faced at the middle of the project (Iteration 9), required inputs from Starteur developers were not provided in time. The team postponed testing for Student & Batch Report functions to after Mid Terms Presentation as User Testing 3 due to changes in project schedule. Focus of User Testing 2 was changed to Client Administrator Module, with Reactor Industries' management team as target end-users.
Project Metrics
Schedule Metrics
View our Schedule Metrics Here!
Schedule Metric Highlights
Iteration | Planned Duration/days | Actual Duration/days | Schedule Metric Score | Action | Status |
---|---|---|---|---|---|
5 | 10 | 11 | 0.91 | Our estimates are fairly accurate. Project schedule is on track. Difficulty in setting up email server for Starteur and it was exams period for SMU Term 1. As such, project was delayed. 1 buffer day used. | Completed |
9 | 14 | 11 | - | Batch report module was pushed back due to client's inability to provide algorithm on time. Supervisor was informed of change in schedule. | Incomplete |
Project Risks
Technical Complexity
Quality of Product
Deliverables
Deployment
View our architecture diagram for deployment to production server here!
Testing
User Testing 1
Locations: CHIJ St Nicholas Girls' School, SMU Admin Building, Raffles Institution
Date & Time: 1st week of December 2015
No. of Participants: 4
Objectives:
1. Verify that functionalities built are in line with user requirements
2. Determine if the user interface is intuitive
3. Gather feedback on current functionalities
4. Identify usability problems
User Testing 2
Location: Reactor ARC
Date & Time: 13 February 2016
No. of Participants: 4
Objectives:
1. Verify that functionalities built are in line with user requirements
2. Determine if the user interface is intuitive
3. Gather feedback on current functionalities
4. Identify usability problems
Reflections
Team's Reflections
Team Reflection
- Deeper insights of the behind-the-scenes in a learning management web application and the difficulties teachers and educators face when getting students to complete their assignments on time.
- Gained real-life experience of a commercial project from scratch
What have we done well so far?
- Focused a lot on providing convenience and ease of use to our end-users when we design and build the app
- As a result, both our client and the actual users like the product and gave us positive feedback
- Kept close and constant contact with our end-users. Resulting in most of them agreeing to be participants for our User Testings or recommending other educators to be a part of our User Testings.
What can be improved?
- Be more assertive when seeking understanding from Starteur developers when requesting for inputs and integration efforts.
- Do more in-depth research for front-end design and seek feedback from all stakeholders before moving ahead with changes.
How will we do better?
- Managing our schedule and Starteur's development schedule closely while constantly reminding everyone of the tasks at hand and ahead.
- For any design implementations that we are unsure of, must come up with a few design and seek approval and feedback from relevant stakeholders before moving ahead.