HeaderSIS.jpg

Difference between revisions of "2012T2 Team Chm: Project Management"

From IS480
Jump to navigation Jump to search
 
(180 intermediate revisions by 5 users not shown)
Line 5: Line 5:
  
  
<div style="text-align: left;"><span style="font-family: 'Verdana'; font-size: 33pt; letter-spacing:-0.1em; line-height:80%; color:black; text-transform:uppercase">&nbsp;Project Management</span></div><br>
+
<center><div style="text-align: center;"><span style="font-family: 'Trebuchet MS'; font-size: 48pt; letter-spacing:-0.1em; line-height:80%; color:black;">&nbsp;[[Image:chmlogo.jpg|75px]]  "because there is no <span style="font-size: 64pt; font-family:'Times New Roman'">I</span> in the team"</span></div><br></center>
  
 
<div style="border-bottom: #ffffff solid 12px; padding: 0px 0px 0px 0px;">
 
<div style="border-bottom: #ffffff solid 12px; padding: 0px 0px 0px 0px;">
Line 14: Line 14:
 
| style="border-bottom:2px solid  #2d2d2d; border-top:2px solid  #2d2d2d; background:none;" width="2%" | &nbsp;
 
| style="border-bottom:2px solid  #2d2d2d; border-top:2px solid  #2d2d2d; background:none;" width="2%" | &nbsp;
  
| style="padding:0 .3em;font-face:Verdana;  font-size:110%; border-bottom:2px solid  #2d2d2d; border-top:2px solid  #2d2d2d; text-align:center; background-color:#ffffff; " width="12%" | [[2012T2 Team Chm: Team & Stakeholders |<font color=" #2d2d2d">Team & Stakeholders</font>]]
+
| style="padding:0 .3em;font-face:Verdana;  font-size:110%; border-bottom:2px solid  #2d2d2d; border-top:2px solid  #2d2d2d; text-align:center; background-color:#ffffff; " width="11%" | [[2012T2 Team Chm: Team & Stakeholders |<font color=" #2d2d2d">Team & Stakeholders</font>]]
 
| style="border-bottom:2px solid  #2d2d2d; border-top:2px solid  #2d2d2d; background:none;" width="2%" | &nbsp;
 
| style="border-bottom:2px solid  #2d2d2d; border-top:2px solid  #2d2d2d; background:none;" width="2%" | &nbsp;
  
| style="padding:0 .3em;font-face:Verdana;  font-size:110%; border-bottom:2px solid  #2d2d2d; border-top:2px solid  #2d2d2d; text-align:center; background-color:#ffffff; " width="12%" | [[2012T2 Team Chm: Project Definition |<font color=" #2d2d2d">Project Definition</font>]]
+
| style="padding:0 .3em;font-face:Verdana;  font-size:110%; border-bottom:2px solid  #2d2d2d; border-top:2px solid  #2d2d2d; text-align:center; background-color:#ffffff; " width="11%" | [[2012T2 Team Chm: Project Definition |<font color=" #2d2d2d">Project Definition</font>]]
 
| style="border-bottom:2px solid  #2d2d2d; border-top:2px solid  #2d2d2d; background:none;" width="2%" | &nbsp;
 
| style="border-bottom:2px solid  #2d2d2d; border-top:2px solid  #2d2d2d; background:none;" width="2%" | &nbsp;
  
| style="padding:0 .3em;font-face:Verdana; background-color:#ffffff; font-size:110%; border-bottom:2px solid  #2d2d2d; border-top:2px solid  #2d2d2d; text-align:center; color:#000000" width="12%" | [[2012T2 Team Chm: Project Design |<font color=" #2d2d2d">Project Design</font>]]
+
| style="padding:0 .3em;font-face:Verdana; background-color:#ffffff; font-size:110%; border-bottom:2px solid  #2d2d2d; border-top:2px solid  #2d2d2d; text-align:center; color:#000000" width="11%" | [[2012T2 Team Chm: Project Design |<font color=" #2d2d2d">Project Design</font>]]
 
| style="border-bottom:2px solid  #2d2d2d; border-top:2px solid  #2d2d2d; background:none;" width="2%" | &nbsp;
 
| style="border-bottom:2px solid  #2d2d2d; border-top:2px solid  #2d2d2d; background:none;" width="2%" | &nbsp;
  
| style="padding:0 .3em;font-face:Verdana; background-color:#2d2d2d; font-size:110%; border-bottom:2px solid  #2d2d2d; border-top:2px solid  #2d2d2d; text-align:center; color:#2d2d2d" width="12%" | [[2012T2 Team Chm: Project Management |<font color=" #ffffff">Project Management</font>]]
+
| style="padding:0.3em;font-face:Verdana; font-size:110%; background-color:#2d2d2d; border-bottom:2px solid  #2d2d2d; border-top:2px solid  #2d2d2d; text-align:center; color:#000000" width="11%" | [[2012T2 Team Chm: Project Management |<font color=" #ffffff">Project Management</font>]]
 
| style="border-bottom:2px solid  #2d2d2d; border-top:2px solid  #2d2d2d; background:none;" width="2%" | &nbsp;
 
| style="border-bottom:2px solid  #2d2d2d; border-top:2px solid  #2d2d2d; background:none;" width="2%" | &nbsp;
  
| style="padding:0 .3em;font-face:Verdana; background-color:#ffffff; font-size:110%; border-bottom:2px solid  #2d2d2d; border-top:2px solid  #2d2d2d;  text-align:center; color:#000000" width="12%" | [[2012T2 Team Chm: Progress Summary |<font color=" #2d2d2d">Progress Summary</font>]]
+
| style="padding:0 .3em;font-face:Verdana; background-color:#ffffff; font-size:110%; border-bottom:2px solid  #2d2d2d; border-top:2px solid  #2d2d2d;  text-align:center; color:#000000" width="11%" | [[2012T2 Team Chm: Progress Summary |<font color=" #2d2d2d">Progress Summary</font>]]
 
| style="border-bottom:2px solid  #2d2d2d; border-top:2px solid  #2d2d2d; background:none;" width="2%" | &nbsp;
 
| style="border-bottom:2px solid  #2d2d2d; border-top:2px solid  #2d2d2d; background:none;" width="2%" | &nbsp;
  
| style="padding:0.3em;font-face:Verdana; font-size:110%; background-color:#ffffff;  border-bottom:2px solid  #2d2d2d; border-top:2px solid  #2d2d2d; text-align:center; color: #000000" width="12%" | [[2012T2 Team Chm: Learning Outcomes |<font color=" #2d2d2d ">Learning Outcomes</font>]]
+
| style="padding:0.3em;font-face:Verdana; font-size:110%; background-color:#ffffff;  border-bottom:2px solid  #2d2d2d; border-top:2px solid  #2d2d2d; text-align:center; color: #2d2d2d" width="11%" | [[2012T2 Team Chm: Learning Outcomes |<font color=" #2d2d2d ">Learning Outcomes</font>]]
 +
| style="border-bottom:2px solid  #2d2d2d; border-top:2px solid  #2d2d2d; background:none;" width="2%" | &nbsp;
 +
 
 +
| style="padding:0.3em;font-face:Verdana; font-size:110%; background-color:#ffffff;  border-bottom:2px solid  #2d2d2d; border-top:2px solid  #2d2d2d; text-align:center; color: #2d2d2d" width="11%" | [[2012T2 Team Chm: Photos |<font color=" #2d2d2d ">  Photos  </font>]]
 
|}
 
|}
 
 
<div style="border-left: #ffffff solid 12px; padding: 0px 0px 0px 0px;">
 
<div style="border-left: #ffffff solid 12px; padding: 0px 0px 0px 0px;">
 
<div style="border-right: #ffffff solid 12px; padding: 0px 0px 0px 0px;">
 
<div style="border-right: #ffffff solid 12px; padding: 0px 0px 0px 0px;">
  
 +
<br>
  
 +
<big><p style="text-align: left; font-size: 150%;"><center>
 +
[[IS480_Team_wiki:_2012T2_Team_Chm_MidTerm_Wiki|<font color="#000000" face=""><ins>''' MID-TERM WIKI'''</ins></font>]]   
 +
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 +
[[IS480_Team_wiki:_2012T2_Team_Chm_Final_Wiki|<font color="#000000" face=""><ins>''' FINAL WIKI'''</ins></font>]]
  
 +
</center></p></big>
  
===<div style="font-family:'Century Gothic'; font-size:20px; background: #2d2d2d; padding:14px; font-weight:bold; line-height:0.1em;"><font color = "white">Project Management</font></div>===
+
==Schedule==
 +
<div>'''Version 3 (Current as at 17 APR 2013):'''<br style="clear:both" />
 +
[[Image:Schedule9.png|1000px|center]]</div>
  
 +
===Versions===
 +
'''<font color="##FE2E2E"><big>Project Schedule</big></font>''' earlier versions:
 +
*'''[https://wiki.smu.edu.sg/w/is480/images/4/4f/Chm_sch_18012013.png Detailed Version]'''
 +
*'''[https://wiki.smu.edu.sg/w/is480/images/4/4e/ChmSchedule1.jpg Version 1]'''
 +
*'''[https://wiki.smu.edu.sg/w/is480/images/1/1a/Schedule4.jpg Version 2]'''
 +
<br>
  
==Risks==
+
== Schedule Metric ==
 
+
The schedule will be complemented with the burn-down chart of each sprint, calculating the schedule ratio and adhering to the response actions of each ratio value.
{| class="wikitable"
+
<center>
!colspan="5" | Risks Involved
+
{| class="wikitable" style="text-align: center; height:50px"
 +
|+
 
|-
 
|-
| <b>S/N</b>
+
! scope="row"  width="800" style="text-align: center; background: #F52887"|FORMULA:
| <b><center>Risk</center></b>
+
Schedule Ratio
| <b><center>Impact</center></b>
+
= Remaining Time / Remaining Effort<br>
| <b><center>Level of Impact (out of 10)</center></b>
+
Remaining Time
| <b><center>Mitigation Strategy</center></b>
+
= Number of hours that developer would spend * Days left in SPRINT * No. of Personnel Available
 
|-
 
|-
| 1.
+
|}
| Written codes are not usable with the newer updates
+
</center>
| Too much time spent on designing codes appropriately
+
{| class="wikitable" style="text-align: center; height:200px"
| <center>5</center>
+
|+
| Lead developer to ensure that all committed codes adhere to stated guidelines & PM to ensure that schedule is kept to closely.
 
 
|-
 
|-
| 2.
+
! scope="col"  width="100"| Schedule Ratio
| Business Rules do not adhere to marketing practices as we are unfamiliar with it
+
! scope="col" width="200" | Description
| Misunderstanding business rules resulting in an inaccurate result
+
! scope="col" width="600" | Response
| <center>4</center>
 
| Meet up regularly with marketing professors and users testing
 
 
|-
 
|-
| 3.
+
 
| Members unfamiliar to technologies used like AJAX, JavaScript, D3
+
! scope="row" style="background: #FF00FF" |'''> 1.2'''
| Project would take longer to complete due to learning curve
+
|style="text-align: center;"|Ahead of Schedule
| <center>4</center>
+
|style="text-align: left;"|Redefine Sprint backlogs
| Start learning technologies now and practice on dummy sites
 
 
|-
 
|-
| 4.
+
 
| User interface may not be intuitive
+
! scope="row" style="background: #F433FF"|'''0.8 - 1.2'''
| Developers innovate and play with ideas, resulting in a delay in schedule (as user-testing is time consuming)
+
|style="text-align: center;"|Within healthy schedule range
| <center>5</center>
+
|style="text-align: left;"|No actions required if ratio is about 1. Monitor tasks closely if ratio is below 1 and prepare to re-allocate the following tasks for the following sprint.
| Adhere to user testing phases, else PM will reschedule certain tasks and encourage the team to be be responsive to change.  
 
 
|-
 
|-
| 5.
+
 
| Disagreement amongst team mates
+
! scope="row" style="background: #E238EC"|'''< 0.8'''
| Unable to come to common consensus, resulting in time wastage and inefficiency
+
|style="text-align: center;"|Team is behind schedule
| <center>7</center>
+
|style="text-align: left;"|Project Manager identifies the root cause and impact of the delay. Communicate with the team and client(if necessary). Set up more working meetings and discuss with lead developer for more pair-programming sessions.
| Selected mediator to step in and have a time out period
 
 
|}
 
|}
  
==Deliverables==
+
===Documentation===
 +
{| class="wikitable" style="text-align: center; height:100px"
 +
|+
 +
|-
 +
! scope="col"  width="300" style="background-color:#000000" colspan="2"| <font color="#ffffff"><big>Schedule Ratio for each sprint </big><br></font>
 +
|-
 +
 
 +
!scope="row" style="background-color:#ffffff" width:300px|
 +
 
 +
<big>
 +
 
 +
[https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=32 Sprint 13]<br>
 +
 
 +
[https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=31 Sprint 12]<br>
 +
 
 +
[https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=29 Sprint 11]<br>
 +
 
 +
[https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=28 Sprint 10]<br>
 +
 
 +
[https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=24 Sprint 9]<br>
 +
 
 +
[https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=23 Sprint 8]<br>
 +
 
 +
[https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=21 Sprint 7]<br>
 +
 
 +
</big>
 +
|style="background-color:#ffffff; text-align: center;"width:300px; |
 +
<big>
 +
 
 +
 
 +
'''[https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=22 Sprint 6]'''<br>
 +
 
 +
'''[https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=20 Sprint 5]'''<br>
  
{| class="wikitable"!span="10"
+
'''[https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=12 Sprint 4]'''<br>
!border="0"|
 
|-
 
| <p>A Magento-based online e-commerce store, coupled with social media platforms (Facebook) that is developed along with an Business Intelligence (BI) tools application. This application allows marketing professionals and students to analyze the effectiveness of marketing strategies and campaigns being launched in the Magento e-commerce online store.
 
  
 +
'''[https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=13 Sprint 3]'''<br>
  
LARC would be able to use this application mainly as an education / learning tool for Singapore Management University (SMU) marketing majors students.
+
'''[https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=11 Sprint 2]'''<br>
</p>
 
  
<p>
+
'''[https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=26 Sprint 1]'''<br>
The project deliverables would be two-fold: a plug-in for the Magento eCommerce store, and the other is a Business Intelligence (BI) tool that will be developed on top of the existing Magento Admin
 
</p>
 
  
| <p>
+
'''[https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=2 Product Backlog]'''<br><br>
[[Image:Magento.PNG|250px|right]]
+
</big>
</p>
 
  
 
|}
 
|}
{| class="wikitable" style="text-align: center; height:150px"
 
  
 +
<br>
 +
 +
==Bug Metric==
 +
 +
Our Objective is to ensure the quality of our project through minimising the number of bugs present.
 +
<br>A bug is defined as an error/s in a line of code, resulting in an anomaly in the functioning of the application.
 +
<br>Refer to the Bug Metric [https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=4 Documentation].
 +
<br>
 +
<center>
 +
{| class="wikitable" style="text-align: center; height:50px"
 +
|+
 +
|-
 +
! scope="row"  width="800" style="text-align: center; background: #F52887"|'''Formula''':
 +
Bug Ratio
 +
= (2 X No. of low severity bugs) + (4 X No. of medium severity bugs) + (10 X No. of high severity bugs)
 +
|}
 +
</center>
 +
{| class="wikitable" style="text-align: center; height:50px"
 
|+  
 
|+  
 
|-
 
|-
! scope="col" width="75" style="background-color:#000000"| <font color="#ffffff">S/N</font>
+
! scope="col" style="background-color:#000000" width="100"| <font color="#ffffff">Severity Score</font>
! scope="col" width="250" style="background-color:#000000"| <font color="#ffffff">Deliverables</font>
+
! scope="col" style="background-color:#000000" width="120" | <font color="#ffffff">Severity Level</font>
! scope="col" width="300" style="background-color:#000000"| <font color="#ffffff">Supporting Documents</font>
+
! scope="col" style="background-color:#000000" width="700" | <font color="#ffffff">Description</font>
 
|-
 
|-
  
! scope="row" style="background: #C0C0C0"| 1
+
! scope="row" |'''2'''
|style="text-align: center;"|Project Proposal
+
|style="text-align: center;"|'''LOW'''
|style="text-align: center;"|-
+
|style="text-align: left;"|Errors with page aesthetics. Feature/story can still work, but at a sub optimum level
 
|-
 
|-
  
! scope="row" style="background: #C0C0C0"| 2
+
! scope="row" |'''4'''
|style="text-align: center;"|Project Acceptance
+
|style="text-align: center;"|'''MEDIUM'''
|style="text-align: center;"|-
+
|style="text-align: left;"|Errors that prevent an entire feature/story from working
 
|-
 
|-
  
! scope="row" style="background: #C0C0C0"| 3
+
! scope="row" |'''10'''
|style="text-align: center;"|Usability Test 1
+
|style="text-align: center;"|'''HIGH'''
|style="text-align: center;"|-
+
|style="text-align: left;"|Errors that prevent more than 1 feature/story from working
 +
|}
 +
 
 +
{| class="wikitable" style="text-align: center; height:50px"
 +
|+
 
|-
 
|-
 +
! scope="col"  style="background-color:#000000"  width="120"| <font color="#ffffff">Bug Ratio</font>
 +
! scope="col" style="background-color:#000000"  width="850" | <font color="#ffffff">Response</font>
  
! scope="row" style="background: #C0C0C0"| 4
 
|style="text-align: center;"|Mid-Term
 
|style="text-align: center;"|-
 
 
|-
 
|-
  
! scope="row" style="background: #C0C0C0"| 5
+
! scope="row" style="background: #00FF00" |'''less than 6'''
|style="text-align: center;"|Usability Test 2
+
|style="text-align: left;"|Developers resolve issues within the Sprint on their own accord
|style="text-align: center;"|-
 
 
|-
 
|-
  
! scope="row" style="background: #C0C0C0"| 6
+
! scope="row" style="background: #FFA500" |'''7 - 9'''
|style="text-align: center;"|Final Presentation
+
|style="text-align: left;"|If bug is discovered in a feature that is not a core feature, Project Manager to schedule debugging during buffer.
|style="text-align: center;"|-
+
|-
 +
 
 +
! scope="row" style="background: #FF0000" |'''10 or more'''
 +
|style="text-align: left;"|Developers attempt to resolve bug immediately. Project Manager to relieves member of his current task and set him in charge to resolve bug
  
 
|}
 
|}
<p>
+
<br />
For more details about the project schedule, please click [[https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=11 here]]
+
 
More details coming your way...
+
==Regressive Testing==
</p>
+
Regression testing is any type of software testing that seeks to uncover new software bugs, or regressions, in existing functional and non-functional areas of a system after changes, such as enhancements, patches or configuration changes, have been made to them<br><br>
  
== Project Scope ==
+
The intent of regression testing is to ensure that a change such as those mentioned above has not introduced new faults. One of the main reasons for regression testing is to determine whether a change in one part of the software affects other parts of the software.<br><br>
  
 +
Team Chm uses regressive testing to ensure the quality of our product - Mobisupermarket, and each testing is done after each sprint as documented below;<br><br>
 +
 +
<big>'''Documentation'''</big>
 
{| class="wikitable" style="text-align: center; height:50px"
 
{| class="wikitable" style="text-align: center; height:50px"
 
|+  
 
|+  
 
|-
 
|-
! scope="col"  width="200"| Sceenshots
+
! scope="col"  width="300" style="background-color:#000000" colspan="2"| <font color="#ffffff"><big>Regressive Testing for each sprint </big><br></font>
! scope="col" width="200"| Storypoints
 
! scope="col" width="400" | Description
 
 
|-
 
|-
  
!scope="row" colspan="3" style="background-color:#000000; text-align: left;"|
+
!scope="row" style="background-color:#ffffff" width:250px|
'''&nbsp;<font color="#FFFFFF">CORE STORIES</font>'''
+
 
|-
+
<big>
 +
 
 +
[https://docs.google.com/spreadsheet/ccc?key=0AhROcvfMz_rddDBzZFViUmVfcm1lZWJCb0p4S0dRNGc#gid=11 Sprint 12]<br>
 +
 
 +
[https://docs.google.com/spreadsheet/ccc?key=0AhROcvfMz_rddDBzZFViUmVfcm1lZWJCb0p4S0dRNGc#gid=10 Sprint 11]<br>
 +
 
 +
[https://docs.google.com/spreadsheet/ccc?key=0AhROcvfMz_rddDBzZFViUmVfcm1lZWJCb0p4S0dRNGc#gid=9 Sprint 10]<br>
 +
 
 +
[https://docs.google.com/spreadsheet/ccc?key=0AhROcvfMz_rddDBzZFViUmVfcm1lZWJCb0p4S0dRNGc#gid=8 Sprint 9]<br>
 +
 
 +
[https://docs.google.com/spreadsheet/ccc?key=0AhROcvfMz_rddDBzZFViUmVfcm1lZWJCb0p4S0dRNGc#gid=7 Sprint 8]<br>
 +
 
 +
[https://docs.google.com/spreadsheet/ccc?key=0AhROcvfMz_rddDBzZFViUmVfcm1lZWJCb0p4S0dRNGc#gid=6 Sprint 7]
 +
 
 +
</big>
 +
 
 +
|width:250px; style="background-color:#ffffff; text-align: center;"|  
 +
 
 +
<big>
 +
<br>
 +
'''[https://docs.google.com/spreadsheet/ccc?key=0AhROcvfMz_rddDBzZFViUmVfcm1lZWJCb0p4S0dRNGc#gid=5 Sprint 6]'''<br>
 +
 
 +
'''[https://docs.google.com/spreadsheet/ccc?key=0AhROcvfMz_rddDBzZFViUmVfcm1lZWJCb0p4S0dRNGc#gid=4 Sprint 5]'''<br>
 +
 
 +
'''[https://docs.google.com/spreadsheet/ccc?key=0AhROcvfMz_rddDBzZFViUmVfcm1lZWJCb0p4S0dRNGc#gid=3 Sprint 4]'''<br>
 +
 
 +
'''[https://docs.google.com/spreadsheet/ccc?key=0AhROcvfMz_rddDBzZFViUmVfcm1lZWJCb0p4S0dRNGc#gid=2 Sprint 3]'''<br>
 +
 
 +
'''[https://docs.google.com/spreadsheet/ccc?key=0AhROcvfMz_rddDBzZFViUmVfcm1lZWJCb0p4S0dRNGc#gid=1 Sprint 2]'''<br>
 +
 
 +
'''[https://docs.google.com/spreadsheet/ccc?key=0AhROcvfMz_rddDBzZFViUmVfcm1lZWJCb0p4S0dRNGc#gid=0 Sprint 1]'''
 +
 
 +
 
 +
|}
 +
 
 +
<br>
  
! scope="row" |[[Image:Addimage.jpg|300px]]
+
==Risks Analysis==
|style="text-align: center;"|'''Type Chapter Name here'''
 
|style="text-align: left;"|
 
*Type description here
 
  
 +
{| class="wikitable"
 +
|-
 +
| <b>S/N</b>
 +
| <b><center>Risk</center></b>
 +
| <b><center>Impact</center></b>
 +
| <b><center>Level of Impact (out of 10)</center></b>
 +
| <b><center>Mitigation Strategy</center></b>
 +
|-
 +
!colspan="5" | '''Project Management'''
 +
|-
 +
| 1.
 +
| The estimation of story points by the team for each storyboard is not accurate, resulting in an inaccurate gauge of the planned sprint backlogs
 +
| Schedule will be severely affected. Storyboards may have to be pushed back to the next iteration
 +
| <center>7</center>
 +
| Project Manager to re-plan the resource and schedule allocation
 +
|-
 +
| 2.
 +
| The developed product is not able to be installed like a plugin, as per requested by the client.
 +
| Too much time spent on designing codes appropriately
 +
| <center>5</center>
 +
| Lead developer to ensure that all committed codes adhere to stated guidelines & PM to ensure that schedule is kept to closely.
 +
|-
 +
!colspan="5" | '''Stakeholder Management'''
 +
|-
 +
| 1.
 +
| Due to personal reasons, client Prof Shim may have to make short trips back to Korea
 +
| Prof Shim may not be contactable at times when we have urgent matters
 +
| <center>7</center>
 +
| Set up regular meeting time slot with the client
 +
Email the client when we are not able to talk to her personally
 +
|-
 +
!colspan="5" | '''Technical'''
 +
|-
 +
| 1.
 +
| Members unfamiliar to technologies used like AJAX, JavaScript, D3
 +
| Project would take longer to complete due to learning curve
 +
| <center>4</center>
 +
| Start learning technologies now and practice on dummy sites
 +
|-
 +
| 2.
 +
| Business Rules such as creating of campiagns and designing of [[https://wiki.smu.edu.sg/is480/2012T2_Team_Chm:_Project_Definition#Common_Terms_Used_in_This_Project hooks]] do not adhere to marketing practices as we are unfamiliar with it
 +
| Misunderstanding business rules resulting in an inaccurate result
 +
| <center>4</center>
 +
| Meet up regularly with marketing professors and users testing
 +
|-
 +
| 3.
 +
| Users may not know how to use the software the first time they use the application
 +
| Users may have a difficult time adapting to the new software
 +
| <center>5</center>
 +
| Have a soft copy of a user manual or incorporate a guide in the software to guide the users
 +
|-
 +
| 4.
 +
| The steep learning curve for magento may prevent us from progressing according to our schedule
 +
| Project would be difficult to integrate and code and thus take a longer time to complete
 +
| <center>5</center>
 +
| Project Manager to schedule more time for Magento workshops and peer learning
 +
|-
 +
| 5.
 +
| Go Daddy Server Fails
 +
| Project cannot be deployed and thus take a longer time to complete
 +
| <center>8</center>
 +
| Project Manager to obtain working copy from repository and redeploy
 +
|-
 +
| 6.
 +
| Project Repository unavailable due to technical faults
 +
| Project cannot continue
 +
| <center>5</center>
 +
| Project team members to obtain last known working copy from teammates
 
|-
 
|-
 
+
!colspan="5" | '''Team Management'''
!scope="row" colspan="3" style="background-color:#000000; text-align: left;"|
+
|-
'''&nbsp;<font color="#FFFFFF">ADDITIONAL STORIES'''</font>
+
| 1.
 +
| Lack of manpower because it is expected that Leonard is required to go over a competition (unable to predict as the dates are not confirmed yet)
 +
| Productivity of the team may decrease
 +
| <center>6</center>
 +
| Ensure that everyone stays healthy by planning sufficient rest time for the team
 
|-
 
|-
 
+
| 2.
! scope="row" |[[Image:Addimage.jpg|300px]]
+
| As this is the first time the team members are working together, different working styles of the team members may clash with each other.
|style="text-align: center;"|'''Type Chapter Name here'''
+
| Productivity of the team may be severely affected.
|style="text-align: left;"|
+
| <center>6</center>
*Type description here
+
| Set common ground rules to ensure transparency amongst the team.
 +
Have bonding time to understand more about each team member and strengthen the bonds within the team.
 
|-
 
|-
 +
|}
  
!scope="row" colspan="3" style="background-color:#000000; text-align: left;"|
+
==Deliverables==
'''&nbsp; <font color="#FFFFFF">PROPOSED STORIES ''<small>*not implemented in project''</small></font>'''
 
|-
 
  
! scope="row" |[[Image:Addimage.jpg|300px]]
+
{| class="wikitable"!span="10"
|style="text-align: center;"|'''Type Chapter Name here'''
+
!border="0"|
|style="text-align: left;"|
+
|-  
*Type description here
+
| <p>A Magento-based online e-commerce store, coupled with social media platforms (Facebook) that is developed along with an Business Intelligence (BI) tools application. This application allows marketing professionals and students to analyze the effectiveness of marketing strategies and campaigns being launched in the Magento e-commerce online store.
|-
 
  
|}
 
  
 +
LARC would be able to use this application mainly as an education / learning tool for Singapore Management University (SMU) marketing majors students.
 +
</p>
  
 
<p>
 
<p>
For more detailed information regarding the various project tasks, please click [[https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=2]]
+
The project deliverables would be two-fold: a plug-in for the Magento eCommerce store, and the other is a Business Intelligence (BI) tool that will be developed on top of the existing Magento Admin
More details coming your way...
 
 
</p>
 
</p>
  
 +
| <p>
 +
[[Image:Magento.PNG|250px|right]]
 +
</p>
  
<!--
 
{| class="wikitable"
 
!colspan="5" |Project Scope
 
|-
 
| <b>Chapters</b>
 
| <b>Chapter Name</b>
 
| <b>Description</b>
 
|-
 
| colspan= "4" style="background: Black; color: white" style="text-align:left|'''Core Features'''
 
|- |
 
| Picture
 
| Manage Campaign
 
| dsf
 
|-
 
 
|}
 
|}
-->
 
  
==Milestones==
+
<p>
asd
+
For more details about the project schedule, please click [[https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=11 here]]
<br />
+
More details coming your way...
<br />
+
</p>
 +
 
  
== Project Framework ==
+
== Project Management Framework ==
<br><p>Scrum is an iterative and flexible software development method for the management of software projects and product or application development.. The process is explained by the following flow chart and SCRUM terminology list. For a more visual description click [http://www.youtube.com/watch?v=XU0llRltyFM here] for a youtube video, otherwise the following describes the process;</p>
+
<br><p>SCRUM is an iterative and flexible software development method for the management of software projects and product or application development.. The process is explained by the following flow chart and SCRUM terminology list. For a more visual description click [http://www.youtube.com/watch?v=XU0llRltyFM here] for a youtube video, otherwise the following describes the process;</p>
  
 
<br><p>'''1. Roles & Responsibilities'''
 
<br><p>'''1. Roles & Responsibilities'''
 
[[Image: Scrumframework.jpg|thumb|650px|right|'''SCRUM process flow of events''']]
 
[[Image: Scrumframework.jpg|thumb|650px|right|'''SCRUM process flow of events''']]
 
*The Product Owner (Prof Kyong Jin Shim) is responsible for the business interest and value of the project.
 
*The Product Owner (Prof Kyong Jin Shim) is responsible for the business interest and value of the project.
*The Scrum Master (Project Manager) takes charge of managing the product backlog and the team’s productivity.
+
*The SCRUM Master (Project Manager) takes charge of managing the product backlog and the team’s productivity.
 
*The team is a self-managed entity that ensures that the work gets completed.</p>
 
*The team is a self-managed entity that ensures that the work gets completed.</p>
  
Line 232: Line 384:
  
 
<br><p>'''3. Sprint Planning / Sprint Backlog'''
 
<br><p>'''3. Sprint Planning / Sprint Backlog'''
*Next, Team Chm pulls out a list of to-do items from the product backlog and places it in the sprint backlog.  
+
*Next, Team Chm pulls out a list of to-do items from the [[https://docs.google.com/spreadsheet/ccc?key=0AgEVT7COZGKGdDA5cFlXVEMxZVY3Qjc4R29kbnRlTkE#gid=2  product backlog]] and places it in the sprint backlog.  
 
*Each story of a sprint has an in charge, and he shall see through the development and testing of the story.  
 
*Each story of a sprint has an in charge, and he shall see through the development and testing of the story.  
 
*He needs to update the status of the story in the product backlog.</p>
 
*He needs to update the status of the story in the product backlog.</p>
Line 238: Line 390:
 
<br><p>'''4. Sprint'''
 
<br><p>'''4. Sprint'''
 
*A sprint is a duration that the team takes to complete the tasks selected in the sprint backlog.  
 
*A sprint is a duration that the team takes to complete the tasks selected in the sprint backlog.  
*Team Chm sprint duration is 3 weeks.  
+
*Team Chm sprint duration is can vary from 4 to 27 days.  
 
*Once the Sprint Backlog is up, the team scrambles to work on the sprint.  
 
*Once the Sprint Backlog is up, the team scrambles to work on the sprint.  
  
Line 258: Line 410:
 
<br>The SCRUM process then repeats itself until the product backlog is cleared.  
 
<br>The SCRUM process then repeats itself until the product backlog is cleared.  
  
<br><br>Further your knowledge of SCRUM via [http://www.scrumalliance.org/learn_about_scrum Scrum Alliance], '''where Team Chm has referenced the contents of this section from.'''</p>
+
<br><br>Further your knowledge of SCRUM via [http://www.scrumalliance.org/learn_about_scrum Scrum Alliance], '''where Team Chm has referenced the contents of this section from.'''

Latest revision as of 22:47, 17 April 2013


 Chmlogo.jpg "because there is no I in the team"

Home   Team & Stakeholders   Project Definition   Project Design   Project Management   Progress Summary   Learning Outcomes   Photos


MID-TERM WIKI            FINAL WIKI

Schedule

Version 3 (Current as at 17 APR 2013):
Schedule9.png

Versions

Project Schedule earlier versions:


Schedule Metric

The schedule will be complemented with the burn-down chart of each sprint, calculating the schedule ratio and adhering to the response actions of each ratio value.

FORMULA:

Schedule Ratio = Remaining Time / Remaining Effort
Remaining Time = Number of hours that developer would spend * Days left in SPRINT * No. of Personnel Available

Schedule Ratio Description Response
> 1.2 Ahead of Schedule Redefine Sprint backlogs
0.8 - 1.2 Within healthy schedule range No actions required if ratio is about 1. Monitor tasks closely if ratio is below 1 and prepare to re-allocate the following tasks for the following sprint.
< 0.8 Team is behind schedule Project Manager identifies the root cause and impact of the delay. Communicate with the team and client(if necessary). Set up more working meetings and discuss with lead developer for more pair-programming sessions.

Documentation

Schedule Ratio for each sprint

Sprint 13

Sprint 12

Sprint 11

Sprint 10

Sprint 9

Sprint 8

Sprint 7


Sprint 6

Sprint 5

Sprint 4

Sprint 3

Sprint 2

Sprint 1

Product Backlog


Bug Metric

Our Objective is to ensure the quality of our project through minimising the number of bugs present.
A bug is defined as an error/s in a line of code, resulting in an anomaly in the functioning of the application.
Refer to the Bug Metric Documentation.

Formula:

Bug Ratio = (2 X No. of low severity bugs) + (4 X No. of medium severity bugs) + (10 X No. of high severity bugs)

Severity Score Severity Level Description
2 LOW Errors with page aesthetics. Feature/story can still work, but at a sub optimum level
4 MEDIUM Errors that prevent an entire feature/story from working
10 HIGH Errors that prevent more than 1 feature/story from working
Bug Ratio Response
less than 6 Developers resolve issues within the Sprint on their own accord
7 - 9 If bug is discovered in a feature that is not a core feature, Project Manager to schedule debugging during buffer.
10 or more Developers attempt to resolve bug immediately. Project Manager to relieves member of his current task and set him in charge to resolve bug


Regressive Testing

Regression testing is any type of software testing that seeks to uncover new software bugs, or regressions, in existing functional and non-functional areas of a system after changes, such as enhancements, patches or configuration changes, have been made to them

The intent of regression testing is to ensure that a change such as those mentioned above has not introduced new faults. One of the main reasons for regression testing is to determine whether a change in one part of the software affects other parts of the software.

Team Chm uses regressive testing to ensure the quality of our product - Mobisupermarket, and each testing is done after each sprint as documented below;

Documentation

Regressive Testing for each sprint

Sprint 12

Sprint 11

Sprint 10

Sprint 9

Sprint 8

Sprint 7


Sprint 6

Sprint 5

Sprint 4

Sprint 3

Sprint 2

Sprint 1



Risks Analysis

S/N
Risk
Impact
Level of Impact (out of 10)
Mitigation Strategy
Project Management
1. The estimation of story points by the team for each storyboard is not accurate, resulting in an inaccurate gauge of the planned sprint backlogs Schedule will be severely affected. Storyboards may have to be pushed back to the next iteration
7
Project Manager to re-plan the resource and schedule allocation
2. The developed product is not able to be installed like a plugin, as per requested by the client. Too much time spent on designing codes appropriately
5
Lead developer to ensure that all committed codes adhere to stated guidelines & PM to ensure that schedule is kept to closely.
Stakeholder Management
1. Due to personal reasons, client Prof Shim may have to make short trips back to Korea Prof Shim may not be contactable at times when we have urgent matters
7
Set up regular meeting time slot with the client

Email the client when we are not able to talk to her personally

Technical
1. Members unfamiliar to technologies used like AJAX, JavaScript, D3 Project would take longer to complete due to learning curve
4
Start learning technologies now and practice on dummy sites
2. Business Rules such as creating of campiagns and designing of [hooks] do not adhere to marketing practices as we are unfamiliar with it Misunderstanding business rules resulting in an inaccurate result
4
Meet up regularly with marketing professors and users testing
3. Users may not know how to use the software the first time they use the application Users may have a difficult time adapting to the new software
5
Have a soft copy of a user manual or incorporate a guide in the software to guide the users
4. The steep learning curve for magento may prevent us from progressing according to our schedule Project would be difficult to integrate and code and thus take a longer time to complete
5
Project Manager to schedule more time for Magento workshops and peer learning
5. Go Daddy Server Fails Project cannot be deployed and thus take a longer time to complete
8
Project Manager to obtain working copy from repository and redeploy
6. Project Repository unavailable due to technical faults Project cannot continue
5
Project team members to obtain last known working copy from teammates
Team Management
1. Lack of manpower because it is expected that Leonard is required to go over a competition (unable to predict as the dates are not confirmed yet) Productivity of the team may decrease
6
Ensure that everyone stays healthy by planning sufficient rest time for the team
2. As this is the first time the team members are working together, different working styles of the team members may clash with each other. Productivity of the team may be severely affected.
6
Set common ground rules to ensure transparency amongst the team.

Have bonding time to understand more about each team member and strengthen the bonds within the team.

Deliverables

A Magento-based online e-commerce store, coupled with social media platforms (Facebook) that is developed along with an Business Intelligence (BI) tools application. This application allows marketing professionals and students to analyze the effectiveness of marketing strategies and campaigns being launched in the Magento e-commerce online store.


LARC would be able to use this application mainly as an education / learning tool for Singapore Management University (SMU) marketing majors students.

The project deliverables would be two-fold: a plug-in for the Magento eCommerce store, and the other is a Business Intelligence (BI) tool that will be developed on top of the existing Magento Admin

Magento.PNG

For more details about the project schedule, please click [here] More details coming your way...


Project Management Framework


SCRUM is an iterative and flexible software development method for the management of software projects and product or application development.. The process is explained by the following flow chart and SCRUM terminology list. For a more visual description click here for a youtube video, otherwise the following describes the process;


1. Roles & Responsibilities

SCRUM process flow of events
  • The Product Owner (Prof Kyong Jin Shim) is responsible for the business interest and value of the project.
  • The SCRUM Master (Project Manager) takes charge of managing the product backlog and the team’s productivity.
  • The team is a self-managed entity that ensures that the work gets completed.


2. Product Backlog

  • The process is first triggered with a wish list of requirements drawn up by the product owner (Client).


3. Sprint Planning / Sprint Backlog

  • Next, Team Chm pulls out a list of to-do items from the [product backlog] and places it in the sprint backlog.
  • Each story of a sprint has an in charge, and he shall see through the development and testing of the story.
  • He needs to update the status of the story in the product backlog.


4. Sprint

  • A sprint is a duration that the team takes to complete the tasks selected in the sprint backlog.
  • Team Chm sprint duration is can vary from 4 to 27 days.
  • Once the Sprint Backlog is up, the team scrambles to work on the sprint.


5. Weekly meetings

  • Instead of having daily meetings as depicted in the original SCRUM process, Team Chm has a weekly SCRUM meeting instead to customise to its current needs.


The SCRUM process then repeats itself until the product backlog is cleared.

Further your knowledge of SCRUM via Scrum Alliance, where Team Chm has referenced the contents of this section from.