Difference between revisions of "IS480 Team wiki: 2015T1 Codex Midterm Wiki"
Jump to navigation
Jump to search
Currently At: Iteration 7
Line 89: | Line 89: | ||
<center>[[File:Timeline_codex_v3.png|1000px]]</center><br> | <center>[[File:Timeline_codex_v3.png|1000px]]</center><br> | ||
− | ==<div style="background: #A6CE39; padding: 12px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em;font-size:20px"><font color=#FFFFF>Project Metrics</font></div>== | + | ==<div style="background: #A6CE39; padding: 12px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em;font-size:20px"><font color=#FFFFF>Project Metrics</font></div> |
+ | |||
+ | {| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; background-color:#FFFFFF;" | ||
+ | |- | ||
+ | ! style="color:white; background-color:#45812B; width:50px" | Iteration | ||
+ | ! style="color:white; background-color:#45812B; width:150px" | Period | ||
+ | ! style="color:white; background-color:#45812B; width:100px" | Task Metric Score | ||
+ | ! style="color:white; background-color:#45812B; width:150px" | Actions | ||
+ | |- | ||
+ | | <center>1</center> | ||
+ | | <center>4 October 2015 - 13 Oct 2015</center> | ||
+ | | <center>100%</center> | ||
+ | | <center>As planned.</center> | ||
+ | |- | ||
+ | | <center>2</center> | ||
+ | | <center>13 Oct 2015 - 26 Oct 2015</center> | ||
+ | | <center>100%</center> | ||
+ | | <center>As planned. </center> | ||
+ | |- | ||
+ | | <center>3</center> | ||
+ | | <center>26 Oct 2015 - 12 Nov 2015</center> | ||
+ | | <center>92.30%</center> | ||
+ | | <center>A part of Order Management - Payment Process - Paypal function was delayed and moved to Iteration 7 because our coder used the time to do bugs squashing for User Management until it was at an acceptable bug score instead. </center> | ||
+ | |- | ||
+ | | <center>4</center> | ||
+ | | <center>12 Nov 2015 - 4 Dec 2015</center> | ||
+ | | <center>100%</center> | ||
+ | | <center>As planned.</center> | ||
+ | |- | ||
+ | | <center>5</center> | ||
+ | | <center>4 Dec 2015 - 20 Jan 2016</center> | ||
+ | | <center>93.75%</center> | ||
+ | | <center>Human risk happened. Team member has to go back to china earlier than planned, hence, we decided to move the Inventory Management - Low Stock Warning to Iteration 7</center> | ||
+ | |- | ||
+ | | <center>6</center> | ||
+ | | <center>20 Jan 2016 - 10 Feb 2016</center> | ||
+ | | <center>100%</center> | ||
+ | | <center>As planned.</center> | ||
+ | |- | ||
+ | | <center>7</center> | ||
+ | | <center>10 Feb 2016 - 28 Feb 2016</center> | ||
+ | | <center>100%</center> | ||
+ | | <center>As planned.</center> | ||
+ | |} | ||
+ | |||
+ | |||
+ | [[Image: Codex_Bug_Metrics.png|700px|center]]<br> | ||
==<div style="background: #A6CE39; padding: 12px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em;font-size:20px"><font color=#FFFFF>Project Risk</font></div> | ==<div style="background: #A6CE39; padding: 12px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em;font-size:20px"><font color=#FFFFF>Project Risk</font></div> | ||
Line 161: | Line 207: | ||
|} | |} | ||
− | |||
==<div style="background: #A6CE39; padding: 12px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em;font-size:20px"><font color=#FFFFF>User Testing</font></div>== | ==<div style="background: #A6CE39; padding: 12px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em;font-size:20px"><font color=#FFFFF>User Testing</font></div>== |
Revision as of 14:44, 17 February 2016
Project Summary
Project Management
Module | Status |
---|---|
User Management Module | Completed |
Product Management Module | Completed |
Order Management Module | Completed except for "Print label address for shipping" |
Inventory Management Module | Completed |
Customer Relationship Management Module | Completed except "Email Coupon" function |
Cross Marketing Management Module | Not Completed |
Sales Performance Management Module | Not Completed |
Project Schedule
==
Project Metrics
Iteration | Period | Task Metric Score | Actions |
---|---|---|---|
==
Project Risk
# | Risk Type | Risk Event | Likelihood | Impact | Category | Mitigation |
---|---|---|---|---|---|---|
1 | Technical Risk | Overall, the team is not familiar with the technologies/resources used for developing the project (i.e. PHP.) | High | High | A | We will conduct peer teaching and sharing to help each other. |
2 | Project Management Risk | Team’s lack of experience might cause delays in the iterations due to underestimate or overestimate of a programming task. | Medium | High | A | Regular meetings to update on progress. If necessary, we will re-plan task(s) for the next iteration. |
3 | Client Management | Client is unable to give us the relevant data for us, causing a delay in our project schedule. | Medium | Medium | C | We will try to make do with sample data first, so that as soon as we get the relevant data from our client, we can integrate into our system straightaway. |
4 | Client Management Risk | Client has not fully decided upon the range of functions in her application as she is new to a e-commerce web application; may eventually lead to big scope changes. | Medium | Medium | B | Regular meet up with our client to update her on our current progress and ask for incremental feedbacks. |
5 | Client Management Risk | Client has not host an e-commerce or a website before and is not IT savy, she may experience some difficulty with using our system. | Medium | Medium | B | We try to maintain simplicity in our design but we might compile a user guide for her future reference. |
6 | Resource Risk | Unforeseeable problems with technology that could cause loss of data. | Low | High | B | Make sure that files are always updated in the dropbox, such that the loss of a local hard drive will not affect the project greatly. |
7 | Human Risk | Team members become unavailable due to sickness or other unavoidable circumstances, as we have only 4 members. | Low | Medium | C | Code sharing session, so another coder can take over the coding task from the sick member. |