IS480 Team wiki: 2015T1 Codex Midterm Wiki
Our project has 11 iteration.
As of 18 Feb 2016, we have completed 67.9% of our development.
We have conducted 1 user testing before mid terms, which consist of 6 customers of our client.
There was no major changes in requirements throughout this period.
Some major changes in schedule throughout this period involves delaying our User Test 1 to iteration 7(actual) instead of Iteration 4(planned). This change was due to our team wanting to test the system together with our paypal function to give users a complete experience, but paypal function was delayed to Iteration 6.
In addition, we decided to combine the planned iteration 5 and 6 together into one iteration in the midst of our development.
There are also slight re-scoping of our project after meeting with the Supervisor and we have liase with our Client and got her agreement.
These changes include new sub-task (i.e. Auto printing shipping addresses for label and website clicks tracking).
Because of these new changes, we decided to drop sub task Product Comparison and seeked our Client agreement.
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 |
Iteration | Period | Task Metric Score | Actions |
---|---|---|---|
# | 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 | B | 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. |