Goodmix Final Wiki
Main Page: IS480 Team wiki: 2010T2 Good Mix
Project Progress Summary
Project Highlights:
This section is about sudden requirement changes or requests since midterm which we took up. More information on how requirement changes are handled here.
S/N | Event | Evaluation | Action | Result |
---|---|---|---|---|
1 | User request customizing symbols by choosing from a list of images | Impact: high as it affects many other functionality Difficulty: high as no research about this is done before. |
Team consulted sponsor with the following options:
1. Implement change but outcome is not the responsibility of Goodmix a. Might have major bugs that cannot be solved and have to revert b. Less time to work on existing bugs but able to pass UAT 2. Do not implement change and focus on debugging Sponsor chose option 1. |
Team split into coding team (Bernard, Shazlee and George) and project management team (Naresh and Jess) to work concurrently.
Scenario 1(b) occurred. |
2 | New “find coordinates” function requested on 8th November to be up by 10th November for UAT | Impact: low because it is a standalone function
Difficulty: low because similar techniques are used before |
Went ahead with the request but tight deadline is a challenge so collaboration is critical. Bernard had to finish the coding and UI before passing it to Naresh to update Test Plan and Shazlee to update User Guide. | Request completed and RIBA tested before UAT |
3 | Client failed the spatial error handling for the UAT conducted on 10 November 2010. If this is not addressed, it means that the UAT failed. | Impact: low because it does not implicate other codes
Difficulty: medium as previous attempts to give specific errors had failed. |
Team is offered 2 options from sponsor
1.Fix it 2.Not fix it and write a statement as explanations which will be submitted back to the client who graded fail for approval. |
Jess thought of an idea and managed to accomplish the specific error handling. |
Project Challenges:
1) Expectations of end users from different departments in biodiversity center
|
Project Achievements:
Scheduling the project is the most complex task for this project. Due to the nature of our development process, we design our own method to mitigate the disadvantage of adopting this process which we called it dynamic scheduling. This method was effective as it successfully helped us overcome many milestones to satisfy our stakeholders.
|
Project Management
Project Schedule (Plan vs. Actual):
Changes to project schedule were elaborated up to midterm. Therefore this section will start at phase 6.
Although there are many changes to the requirements, schedule is well on track. This is because while we added change to the requirements, we also removed some that were planned but got prioritized lower after the change request. Hence, the net effect is neutralized and we increased our “working hours” when time seems tight. For example, we met up for all weekdays from 10am to 6pm during week 8 midterm break which allowed us to bring some tasks forward.
table here
Project Metrics:
Technical Complexity:
GoodMix has ranked the technical complexity by functions:
Rank | Function |
---|---|
1 | Symbol Customization |
2 | Layer Control Manager |
3 | Spatial Search |
4 | Attribute Search |
5 | Highlight |
6 | Heatmap |
7 | Data Loading |
8 | Dynamic Legend |
9 | Area Calculation |
10 | User Interface |
11 | Map Export to Images (Snapshot) |
12 | Distance Calculation |
13 | Find Coordinates |
14 | Navigation Pack |
15 | Map Scale |
16 | Map Provider |
However, we feel that the ranking is largely affected by time:
The time that it is expected to be delivered the time that the team decided to work on the function and the time that the request is made. For example, Layer Control Manager might have ranked lower if the team is to develop this function later in the project when our skills are cultivated. This is because our skills improved, tools are more familiarized and schedule changes over the months.
Quality of Product
Project Deliverable:
Stage | Specification | Modules |
Project Management | Minutes | 123 |
Metrics | Bug metrics | |
Requirements | Story cards | crud, trend analytics |
Analysis | Use case | 123 |
System Sequence Diagram | ssd | |
business process | Here | |
Screen Shots | CRUD Customer, Trend Analysis | |
Design | er diagram | 1, 2, 3 |
class diagram | 123 | |
Testing | Test plan | 123 |
Handover | Manuals | User tutorial, Developer manual, Setup manual |
Code | client server | |
deployment diagram | 123 |
Quality:
Deployment:
Testing:
Reflection
Jess:
Naresh:
Bernard:
Shazlee:
George:
Disclaimer: All images and content on this page are done by Good Mix and should not be published without their permission.
Main Page: IS480 Team wiki: 2010T2 Good Mix