Difference between revisions of "IS480 Team wiki: 2012T2 Team Chm MidTerm Wiki"
Jump to navigation
Jump to search
Line 14: | Line 14: | ||
There are several key accomplishments since the project inception on 26 Oct 2012: | There are several key accomplishments since the project inception on 26 Oct 2012: | ||
*Write here<br><br> | *Write here<br><br> | ||
− | + | The project schedule is shown below: | |
|} | |} | ||
[[Image:Schedule2.jpg|1000px]] | [[Image:Schedule2.jpg|1000px]] |
Revision as of 20:48, 31 January 2013
MID-TERM WIKI |
Project Progress Summary
Overview
Team Chm has completed Sprint 10 on date.
The project schedule is shown below: |
Project Highlights
EVENT | HIGHLIGHT / ISSUE |
---|---|
Event 1 | Write Here
|
Event 2 | Write here
|
Event 3 | Write here
|
Technical Complexity
The technical complexity are listed in order of the highest complexity
COMPLEXITY | DESCRIPTION |
---|---|
Event 1 | Write Here
|
Event 2 | Write here
|
Event 3 | Write here
|
Project Management
Project Status
Chapters | Status | Confidence Level (0-1) | Member In-Charge |
---|---|---|---|
Authentication | 90% developed and deployed | 1 | Joseph |
Manage Campaign | 100% developed | 1 | Leonard |
Manage Hooks - Coupons | 90% developed | 1 | Rachel |
Manage Hooks - Social Messages | 50% developed | 1 | Max |
Manage Purchases | 100% developed and deployed | 1 | Leonard & Rachel |
Manage Insights | Not Started | 0.9 | Max |
Project Scope
1. Project scope hasn't changed since inception
- Chapters are categorized in priority circles:
- Core, Secondary and Tertiary Features: Developed by Team Chm during IS480
- Good-to-have Features: Features of lower priority; can be implemented in future beyond this project
Schedule (Planned vs Mid Term)
Project Metrics
Schedule Metric
Bug Metric
Risk Management
Added new Risks as at mid-term. Full entries are shown under the Project Management in the Risk Management Table.
S/N | ||||
Technical | ||||
---|---|---|---|---|
5. | Go Daddy Server Fails | Project cannot be deployed and thus take a longer time to complete | Project Manager to obtain working copy from repository and redeploy | |
6. | Project Repository unavailable due to technical faults | Project cannot continue | Project team members to obtain last known working copy from teammates |
Product Quality
Intermediate Deliverables
Stage | Specification | Modules |
---|---|---|
Project Management | Minutes | |
Metrics | ||
Requirements | Product Backlog | |
UI Mockups & Videos | ||
Analysis | Use Case | |
Design | ER Diagram | |
Testing | User Test Plan |
Deployment
- Staging & Development Environment: deployed on GoDaddy server
- Database: Magento EAV database
- Web Links:
Usability Test 1
Objectives
Scope of Test
Session 1
Session 2
Reflections
Member | Reflections | Member | Reflections |
---|---|---|---|
|
| ||
|
| ||
|