HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2012T2 Team Chm Final Wiki"

From IS480
Jump to navigation Jump to search
Line 65: Line 65:
 
! scope="col" width="820" style="background-color:#4E4E4E"| <font color="#ffffff">HIGHLIGHT / ISSUE</font>
 
! scope="col" width="820" style="background-color:#4E4E4E"| <font color="#ffffff">HIGHLIGHT / ISSUE</font>
 
|-
 
|-
! scope="row" style="background: #C0C0C0"| '''Sprint 2 <br/>20 Nov 2012 <br/>-<br/> 04 Dec 2012'''
+
! scope="row" style="background: #C0C0C0"| '''Developing Social Influence Quantification Algorithm'''
 
|style="text-align: left;"|  
 
|style="text-align: left;"|  
 
'''Incorrect commits to the repository altered files that were meant to be machine-specific ''' <br /><br />
 
'''Incorrect commits to the repository altered files that were meant to be machine-specific ''' <br /><br />
Line 73: Line 73:
 
|-
 
|-
  
! scope="row" style="background: #C0C0C0"| '''Sprint 5'''
+
! scope="row" style="background: #C0C0C0"| '''User Acceptance Testing'''
 
|style="text-align: left;"|  
 
|style="text-align: left;"|  
 
''' No transactional data for Insights ''' <br /><br />
 
''' No transactional data for Insights ''' <br /><br />

Revision as of 17:03, 16 April 2013

FINAL WIKI

MAIN WIKI            MID-TERM WIKI


Team Chm1.jpg

Project Progress Summary

View our one minute pitch HERE

   Final Presentation Slides

   Team Chm Deployed Site Link



  • Team Chm has completed 13 sprints in total and is now finishing its final milestone.
  • This is where we are on the timeline:
FinalSchedule.png

Project Highlights

EVENT HIGHLIGHT / ISSUE
Sprint 2
20 Nov 2012
-
04 Dec 2012

Incorrect commits to the repository altered files that were meant to be machine-specific

It was not only impractical to commit the entire working folder to our repository because it amounted to 109 megabytes, but also because certain files that resided in the working folder were machine-specific. Minimal documentation by Magento exacerbated the problem and hence the eventual solution only came about with advice from various tech sites (stackoverflow, roseindia, tech blogs) after 2 weeks of trial and error.

Due to the integration with Magento and its database, the team had some problems committing and updating the project repository. Hence, the project wasn't able to continue and development had to be put on hold so as to address the project repository issue. The issue was then solved, and only certain major files were committed. The new risk and the risk mitigation plan was then recorded so as to prevent such problems from happening again.

Sprint 5

No transactional data for Insights

In the course of developing our BI tool during Sprint 5, the team was advised by our supervisor that we do not have any meaningful transactional data in our project. Hence, upon discussion with our sponsor, the team and the sponsor decided to to have a data gathering cum user testing session. Over 30 friends were invited so shop online using Magento E-commerce website, and they were each given $1000 virtual money to spend.

Sprint 7

No realistic data in our project

As the project progressed, the team was advised by our supervisor to try to make the spending behaviour slightly more genuine by means of incorporating real products that existed into the platform's catalog of products, which would in turn be more realistic during our User Tests. This rang true amongst the team because the products in the default catalog provided by Magento was either outdated or fictitious. Thus, both the sponsor and the team has been on the search for the products and their products' description to be input into our catalog. The team found the Yellow Mushmellow online blogshop, and the owner was willing to allow her products to be input into our catalog.

Project Challenges

EVENT HIGHLIGHT / ISSUE
Developing Social Influence Quantification Algorithm

Incorrect commits to the repository altered files that were meant to be machine-specific

It was not only impractical to commit the entire working folder to our repository because it amounted to 109 megabytes, but also because certain files that resided in the working folder were machine-specific. Minimal documentation by Magento exacerbated the problem and hence the eventual solution only came about with advice from various tech sites (stackoverflow, roseindia, tech blogs) after 2 weeks of trial and error.

Due to the integration with Magento and its database, the team had some problems committing and updating the project repository. Hence, the project wasn't able to continue and development had to be put on hold so as to address the project repository issue. The issue was then solved, and only certain major files were committed. The new risk and the risk mitigation plan was then recorded so as to prevent such problems from happening again.

User Acceptance Testing

No transactional data for Insights

In the course of developing our BI tool during Sprint 5, the team was advised by our supervisor that we do not have any meaningful transactional data in our project. Hence, upon discussion with our sponsor, the team and the sponsor decided to to have a data gathering cum user testing session. Over 30 friends were invited so shop online using Magento E-commerce website, and they were each given $1000 virtual money to spend.

Project Achievements

Project Management

Project Schedule (Planned VS Actual)

Metrics

Schedule Metrics

Bug Metrics

Technical Complexity

Quality of Product

Project Deliverables

Quality

Deployment

User Acceptance Test (UAT)

Objectives

Test Details & Outcome

Reflections

Team Reflection

Individual Reflections