IS480 Team wiki: 2015T6 6nificance Midterm Wiki
HOME | ABOUT US | PROJECT OVERVIEW | PROJECT MANAGEMENT | DOCUMENTATION |
Main Wiki | Midterm Wiki | Final Wiki |
---|
Project Progress Summary
Current Iteration : 7
Iteration 7 Dates : 16th Sep 2015 - 29th Sep 2015
- Modules To-Be Done: Recommendation
- Modules In-Progress: User, Social
- Modules Completed: Design, Photo, Concierge, Collection
- Overall Project Progress : 60%
- Team is therefore confident of completing the project and delivering the application on time
- Android Mobile Application to be deployed on Google Play Store on 3rd Oct 2015
- Back-End Website has been successfully deployed on Google App Engine
- Back-End Website Link: http://1-dot-naildeckadminportal-1042.appspot.com/
Project Highlights:
- Sponsor not confident of producing nail polishes within project timeline due to difficulties with sourcing good quality materials
- After selecting a desired color, users now can instead pre-order and receive it once sponsor is ready to deliver
- Team proposed that social module is the first page that users will now see in order to encourage them to actively use application which sponsor agreed and accepted
- Team has decided to expand on the social module to include recommendations and provide metrics for sponsor
- Team has decided to revamp and redesign UI based on feedback
Project Management
Project Timeline
Planned | Actual |
---|---|
Project Status:
Module | Status | Confident Level (0-1) | Comment |
User | 75% | 1 | 2 remaining tasks to be completed after midterms |
Design | 90% | 1 | UI to be revamped |
Photo | 90% | 1 | UI to be revamped |
Concierge | 90% | 1 | UI to be revamped |
Collection | 90% | 1 | UI to be revamped |
Social | 60% | 0.6 | 2 remaining tasks and optimization to be done in Iteration 7 |
Recommendation | 0% | 0.8 | Function to be done after midterms |
View Our Module Descriptions Here!
Schedule Highlights
- Three more tasks such as nail polish recommendations, algorithm to sort social media content and track top posts added in recommendations module
- User Testing 2 scheduled to be on 30th Sept
- Deployment to Play Store on 3rd Oct
- Iteration 9 scheduled to be on 9th Oct instead on 12th Oct due to midterms being confirmed on 8th Oct
Project Metrics:
Schedule Metrics
View our Schedule Metrics Here!
Schedule Metrics Highlights
Iteration | Planned Duration (Days) | Actual Duration (Days) | Schedule Metric Score | Action | Status |
---|---|---|---|---|---|
5 | 14 | 16 | 0.88 | More time needed to complete Update Profile function due to difficulties with uploading images to cloud database Follow up action : Informed supervisor about delay. Re-scheduled the dates and tasks of iteration 6. |
Completed |
6 | 12 | 14 | 0.86 | More time needed to research and complete Social Module due to complexity with creating a new social media platform from scratch Follow up action : Informed supervisor about delay. Re-scheduled the dates and tasks of iteration 7. |
Completed |
Bug Metrics
Bug Score
Bug Distribution based on Severity
Iteration | Bug Score | Bug Summary | Action Taken |
---|---|---|---|
5 | 17 3 High 2 Low |
3 high bugs were due to profile picture not being shown due to problems with uploading images to Cloud Database | Resolve bugs immediately. End date of Iteration 5 is delayed. PM to reschedule end dates and tasks of iteration 6 |
6 | 21 1 Critical 2 High 1 Low |
1 critical bug was due to app cash when newsfeed refresh is attempted without internet connection. 2 high bugs were due to number of likes and color hashtags not being accurately recorded in database | Resolve bugs immediately. End date of Iteration 6 is delayed. PM to reschedule end dates and tasks of iteration 7 |
Project Risks:
Technical Complexity:
Describe and list the technical complexity of your project in order of highest complexity first. For example, deploying on iPhone using Objective-C, customizing Drupal with own database, quick search for shortest flight path, database structure, etc.
Quality of product
Provide more details about the quality of your work. For example, you designed a flexible configurable system using XML.config files, uses Strategy Design Pattern to allow plugging in different strategy, implement a regular expression parser to map a flexible formula editor, etc.
Intermediate Deliverables:
There should be some evidence of work in progress.
Stage | Specification | Modules |
Project Requirements | Market Research | Market Research |
Project Management | Minutes | Minutes |
Metrics | Schedule Metrics | |
Metrics | Bug Metrics | |
Requirements | Story cards | CRUD Customer, Trend Analytic |
Analysis | Use case | overall |
System Sequence Diagram | client, server | |
Business Process Diagram | Here | |
Screen Shots | CRUD Customer, Trend Analysis | |
Design | ER Diagram | 1, 2, 3 |
Class Diagram | 1, 2, 3 | |
Testing | User test plan | instructions |
Not all parts of the deliverables are necessary but the evidence should be convincing of the progress. Try to include design deliverables that shows the quality of your project.
Deployment:
In an iterative approach, ready to use system should be available (deployed) for client and instructions to access the system described here (user name). If necessary, provide a deployment diagram link.
Testing:
Describe the testing done on your system. For example, the number of user testing, tester profile, test cases, survey results, issue tracker, bug reports, etc.
Reflection
In this section, describe what have the team learn? Be brief. Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.
Team Reflection:
Any training and lesson learn? What are the take-away so far? It would be very convincing if the knowledge is share at the wiki knowledge base and linked here.
Individual Reflection:
You may include individual reflection if that make sense at this point.