Difference between revisions of "IS480 Team wiki: 2013T2 Tappers/Midterm Wiki"
Jump to navigation
Jump to search
Planned vs Actual
Mtphung.2011 (talk | contribs) |
Mtphung.2011 (talk | contribs) |
||
Line 401: | Line 401: | ||
<h4>1. Email Customisation</h4> | <h4>1. Email Customisation</h4> | ||
− | [[Image:Screen Shot 2014-02-21 at 4.45.38 am.png | 600px]] | + | [[Image:Screen Shot 2014-02-21 at 4.45.38 am.png | 600px|center]] |
<br> | <br> | ||
<h5> | <h5> |
Revision as of 05:12, 21 February 2014
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 | 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/2013 | 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/2013 | 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/2013 | 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 |
Project Management
Project Status
Module | Feature | In charge | Confident Level (0-1) | Status |
---|---|---|---|---|
Administration | Login / Log Out | Xiu Hao | 1 | Completed and deployed |
Create Account | Thu | 1 | Completed and deployed | |
Edit Account Details | Hannah | 0.9 | In Progress | |
Forget Password | Vu | 1 | Completed and deployed | |
Contact Management | Add a Contact | Vu | 1 | Completed and deployed |
In-Line Editing of Contact | Xiu Hao | 1 | Completed and deployed | |
Remove a Contact | Trinh | 1 | Completed and deployed | |
Filter | Vu | 1 | Completed and deployed | |
Customisable Report Generation | Vu | 1 | Completed and deployed | |
Sort | Hannah | 1 | Completed and deployed | |
Contacts Summary | Thu | 1 | Completed and deployed | |
Name Card Reader | Vu | 0.5 | Not started | |
Tagging | Trinh | 0.8 | Not Started | |
Contact Profile | Thu | 1 | Not started | |
Upload a photo | Vu | 1 | Completed and deployed | |
Events Management | Add an Event | Thu | 1 | Completed and deployed |
In-line Editing of Event | Trinh | 1 | Completed and deployed | |
Remove an Event | Xiu Hao | 1 | Completed and deployed | |
Filter | Vu | 1 | Completed and deployed | |
Sort | Vu | 1 | Completed and deployed | |
Event Invitation | Vu | 1 | Completed and deployed | |
Event Details Summary | Hannah | 0.8 | In Progress | |
Event Registration | Trinh | 1 | Completed and deployed | |
Attendance Forecast | Vu | 1 | Completed and deployed | |
Attendance Tracking | Thu | 1 | Completed and deployed | |
Event Summary | Xiu Hao | 0.8 | In Progress | |
Customisable Report Generation | Vu | 0.9 | Completed and deployed | |
Survey Tagging to Event | Vu | 0.8 | Not started | |
Tagging | Vu | 0.8 | Not started | |
Feedback Management | Create a Survey | Hannah | 1 | Completed and deployed |
Edit Survey | Trinh | 1 | Completed and deployed | |
Remove Survey | Thu | 1 | Completed and deployed | |
Customisable Survey with Drag & Drop | Vu | 1 | Completed and deployed | |
Survey Responses Overview | Vu | 1 | Completed and deployed | |
Create Email | Thu | 1 | Completed and deployed | |
Customised template with customised messages | Trinh | 1 | Completed and deployed | |
Send to Selected List | Vu | 0.8 | In Progress | |
Email Statistics Overview | Vu | 0.8 | In Progress |
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. |
Project Metrics
Schedule Metric
Summary Table
Task Planned | Task Completed | Metric for Task Completed | Days Planned for all Tasks | Days Used | Metric for Days Used | Actions Taken | |
---|---|---|---|---|---|---|---|
Iteration 1 | 20 | 20 | 1 | 41 | 39 | 0.95 | Schedule went as planned. No actions were taken. |
Iteration 2 | 19 | 19 | 1 | 34 | 34 | 1 | Schedule went as planned. No actions were taken. |
Iteration 3 | 27 | 27 | 1 | 44 | 48 | 1.09 | Schedule went as planned. No actions were taken. |
Iteration 4 | 17 | 11 | 0.65 | 24 | 4 | 0.17 | Much lesser tasks were completed than planned due to heavy workload in school. PM reschedule tasks to future iterations, mainly iteration 6. |
Iteration 5 | 6 | 6 | 1 | 16 | 14 | 0.88 | Lesser time used than planned. PM considers better allocation of time for next iteration. |
Iteration 6 | 15 | 15 | 1 | 28 | 27 | 0.96 | Schedule went as planned. No actions were taken. |
Iteration 7 | 22 | 22 | 1 | 30 | 50 | 1.67 | Actual time used for tasks were much more than expected due to complexity of features. PM review time given to tasks in future iteration. |
Iteration 8 | 26 | 26 | 1 | 64 | 52 | 0.81 | Lesser time used than planned. PM considers better allocation of time for next iteration. |
Iteration 9 | 9 | 9 | 1 | 14 | 22 | 1.57 | Actual time used for tasks were much more than expected due to complexity of features. PM review time given to tasks in future iteration. |
Iteration 10 | 20 | 20 | 1 | 41 | 44 | 1.07 | Schedule went as planned. No actions were taken. |
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
to be updated
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 |
Deployment
Description | Link |
---|---|
Deployment Site Link | Link |
Testing
User Testing 1
Details
|
Description | Link |
---|---|
User Testing Details | Link |
Heuristic Testing
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 adopt to the changes along the way, and tried my best to contribute ideas to satisfy client's needs. |
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 | I had the opportunity to facilitate a user testing in real business setting, through this, I have came to realize that a User Interface which we think is prefect, may not be what the client is looking for. On top of that, I have learned to more graciously accept comments on the application and come to terms with it. In this lap of the project, I have not only learned how to properly facilitate a user testing, but more importantly, learned to take in suggestions, improve them and add additional value to them. |