IS480 Team wiki: 2013T2 Tappers/Final Wiki
Home | The Team | Project Overview | Project Management | Project Documentation | Learning Outcomes |
Main Wiki | Midterm Wiki | Final Wiki |
Contents
Project Progress Summary
S/N | Description | Link |
---|---|---|
1 | Proposal | Download |
2 | Presentation Slides | Coming Soon |
3 | Poster | Download |
Project Milestones
Project Highlights
Iteration | Date | Features | Description | Action |
---|---|---|---|---|
4 | 6/11/2013 | Task Management | Lien Centre mentioned that they would not need this feature | Feature removed on 6/11/2013 |
4 | 7/11/2013 - 14/7/2013 | Create Event - Remove Event | Team members were too busy with school work and exams | Features postponed to Iteration 6 |
7 | 3/12/2013 | Name Card Reader | Lien Centre brought up a new idea, hoping to be included into our scope. We evaluated the complexity of the feature | Feature to be put on hold |
7 | 12/12/2013 | -- | Openshift problem. Deployed URL was down quite often | Resolved by redeploying after several attempts |
8 | 31/12/2013 | Email - Survey | Features could not be completed as most of the team members were overseas | Features rescheduled to later iterations |
9 | 28/1/2014 | Email - Feedback | Technology errors, hinders progress of the new features.Email unable to send and survey cant be customised. | PM decided to exclude both features for User Testing 1 |
9 | 28/1/2014 | Name Card Reader Tagging | Lien Centre proposed this feature again, hoping to include this feature in our project scope. Lien Centre proposed another feature, tagging | After consideration and consulting supervisor, PM decided to drop Publicity (Facebook + Twitter) feature, and accepted the 2 new features. Rescheduled |
10 | 4/2/2014 | User Interface | "After User Testing 1, we discovered a lot of problems with our interface | We decided to do a UI revamp. Rescheduled to have iteration 11 focused on UI revamp and integration, in preparation for mid terms |
12 | 21/2/2014 | Namecard Reader | As advised from reviewers on Mid Terms Presentation, and further discussion with supervisor, this feature is dropped for better focus on other features. | Feature dropped. |
12 | 21/2/2014 | Tagging | As advised from reviewers on Mid Terms Presentation, and further discussion with supervisor, this feature is dropped for better focus on other features. | Feature dropped |
13 | 11/3/2014 | User Testing 2 | Team decided to postpone this User Testing 2 to 4 Apr as we were not ready with our development to test. | User Testing 2 postponed to 4 Apr |
13 | 26/3/2013 | Analytics | "Upon discussing with the client, team has decided to place emphasis on the dashboard and analytics, improved the catering of needs to our client | Detailed discussion and concise plan with the client and team to understand their needs and concluding the usefulness of analytics and what is required. |
13 | 28/3/2013 | Internal Testing | Team decided to do an internal thorough testing before the actual user testing, to foresee the problems that might occur or bugs that are unidentified during the large scale User Testing 2 | We found a few friends to do the testing, and did internal review. |
14 | 4/4/2014 | User Testing 2 | A large scale User Testing, involving all our users, from Lien Centre staff to our friends, to facilitate the whole procedure of managing an event, from Registration to Analytical Summary, to gather feedback for the usage of the system LIVE. | User Testing 3 stretched over 8 days, with different activities taking place from first day to the last, ranging from creation of event with Lien Centre, Registration from public, doing survey and also event summary. |
Project Management
Project Schedule
S/N | Description | Link |
---|---|---|
1 | Schedule | Project Schedule |
Changes to Scope
Iteration | Features/Milestones | Planned | Actual | Remarks |
---|---|---|---|---|
2 | Export | 4/10/2013 | 7/10/2013 | Export feature could not work after deployment. Jason rectified it. |
3 | Generation of Graph | 22/10/2013 | 24/10/2013 | Graphical feature requires more research. All team members went to research on this feature. |
4 | Task Management | 6/11/2013 | - | Feature dropped as client do not see the use of this feature. |
4 | Create/Remove Event | 12/11/2013 | 10/12/2013 | Features postponed to Iteration 6. Members could not commit as exams period and members overseas. |
7 | Contact Profile | 19/12/2013 | 19/12/2013 | New feature proposed by client. |
7 | Upload Photo | 19/12/2013 | 19/12/2013 | Feature proposed by Team to complement Contact Profile. |
7 | Create Account | 19/12/2013 | 19/12/2013 | Feature proposed by Team |
8 | Attendance Tracking | 6/2/2014 | 6/2/2014 | Feature proposed by client so that they can track attendance. |
10 | Structural Changes to UI | 20/2/2014 | 20/2/2014 | Decided within the Team after UT1 feedback |
10 | Publicity (Facebook + Twitter) | 28/1/2013 | - | Feature dropped. |
12 | Name Card Reader | 26/2/2014 | - | New feature proposed by client. |
13 | Tagging | 11/3/2014 | - | New feature proposed by client. |
13 | Tagging | 11/3/2014 | - | Feature dropped on advice from Mid Terms Presentation |
12 | Name Card Reader | 26/2/2014 | - | Feature dropped on advice from Mid Terms Presentation |
14 | Analytics | 2/4/2014 | 4/4/2014 | To be elaborated and catered to client's needs, in replace for the dropped features |
Project Metrics
Schedule Metric
Schedule Metrics Formula:
Metrics | Description |
---|---|
Scheduled Tasks Metric | Actual No. of Tasks / Planned No. of Tasks |
Scheduled Days Metric | Actual No. of Days / Planned No. of Days |
Actions Taken
Scheduled Tasks Metric | Action |
---|---|
<= 0.8 | Lesser tasks were completed as planned. PM to review tasks for future iteration and decide if they could be completed in time. |
0.8 > x >= 1 | On schedule. Maintain the pace and monitor progress |
Scheduled Days Metric | Action |
---|---|
<= 0.9 | Ahead of planned schedule as Tasks completed and time spent on tasks were used lesser than expected. Might want to allocate more tasks or lesser time in future iteration |
0.9 > x >= 1.1 | On schedule. Maintain the pace and monitor progress |
> 1.1 | Behind schedule. More time was spent on tasks. Reschedule to see if the features can be done in a shorter amount of time. |
Bug Metric
Project Risks
Current Activated Risks
Risk | Type | Likelihood | Impact | Risk Rating | Mitigation Plans |
---|---|---|---|---|---|
Misunderstanding of Requirements | External | Medium | High | Medium | Interact with the client more often via various platforms like Meetings or Emails to clarify doubts |
Members commitments | External | Medium | Medium | Medium | Inform PM beforehand about his/her upcoming commitments/schedule. PM to plan accordingly. |
Steep learning curve technologically | Technical | Medium | High | Medium | PM to allocate individual members to do research on new technologies and guide the team |
Technical Complexity
1. Email Customisation
Complexity of this feature are shown at the following points:
- Customisable templates: System must allow users to choose and design, customise their own email template. It has to be flexible and interactive
- Sending of bulk emails: Sending of one single email is easy, but sending of bulk emails to large number of receivers might be a problem.
- Get through the spam filters: Nowadays, there are a lot of techniques that have been employed to prevent spam emails. It's getting harder and harder to get through these spam filters
- Multiple automated techniques such as Server black-lists, reverse DNS checking, challenge-response etc.
2. Data quality & analysis
We are striving to provide a system with good quality of data and meaningful analysis in graph display to users.
- Eliminate Data duplication in the database
- Ensure data consistency, accuracy.
- Provide visualisation display of data, data summary and analysis for decision-making.
Quality of Product
Intermediate Deliverables
Deliverable | Link |
---|---|
Minutes | *Click Here |
Metrics | *Click Here |
Mock Up Prototypes | *Click Here |
Diagrams | *Click Here |
User Testing 1 | *Click Here |
Internal Testing | To be updated |
User Testing 2 | To be updated |
Deployment
Description | Link |
---|---|
Deployment Site Link | Work In Progress |
Testing
Internal Testing
Description | Information |
---|---|
Date | 28 March 2014 |
No. of Users | 4 |
User Testing Link Execution Plan | Download |
User Testing 2 Instructions | View |
User Testing 2 Results | View |
User Testing 2
Description | Information |
---|---|
Date | 1 April - 8 April 2014 |
No. of Users | 21 |
User Testing 2 Instructions | View |
User Testing 2 Results | View |
User Testing 2 Results
The event details are clearly stated
The registration process is easy
No problems completing the event survey
Satisfied with the color scheme and UI of the registration page
Satisfied with the color scheme and UI of the survey page
Overall the testing was quick and easy
Reflections
Team Reflection
Team Reflection |
---|
It is definitely a challenge for us in this project so far, considering that we are faced with heavy workloads in school and have quite abit of overseas commitment. We are glad that we have very understanding supervisor and client who are willing to help us and cater to our needs as much as they can provide. Gathering the requirements from the client from the bi-weekly meetings with the client has enabled us to forge even stronger bonds with them and we are dedicated to cater to their needs to the best of our ability. |
Individual Reflections
S/N | Name | Reflection |
---|---|---|
1 | Kuek Xiu Hao | Coordinating between team members and project requirements, as well as managing the clients' requests requires time and patience. Careful planning is also important so that time can be evenly spread out and work can be more productive. We must also be very adaptable to changes that are requested by the client and be always on the ball to react to these changes. At times, we are also required to think on our feets for a solution. |
2 | Phung Minh Thu | Changes might happen unexpectedly during the progress. I have learnt to adapt to the changes along the way, and tried my best to meet the deadlines and also satisfy the new requirements from our clients. |
3 | Nguyen Khac Thien Vu | As the lead developer, I'd better look at the project as the whole, not into single details. Keeping the bird's eye-view helps me facilitate my time and effort, and not waste them into fixing small things every day. |
4 | Le Hoang Trinh | Given the feedback from our clients, I have learnt to be flexible and creative to improve the designing of user interfaces, to help our clients have a better experience with the systems. |
5 | Hannah Luai | Apart from the usual time management and project coordinating, one biggest takeaway will be conducting user testing efficiently. When conducting user testing in big groups, it was important for us to ensure that all participants are clear of their roles and will give useful feedbacks. That aside, time management was extremely critical in this stretch of our project as we have many pressing datelines, while having to consistently work on the FYP. Through these, i was not only able to work more efficiently, but have also learnt to be more independent when doing the project |