HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2013T1 Altitude/Midterm"

From IS480
Jump to navigation Jump to search
(New page: __NOTOC__ {| style="background-color:#000;" width="100%" |- !style="text-align:center" |600px |} <div style="background: #000; padding: 15px; font-weight...)
 
Line 5: Line 5:
 
|}
 
|}
  
<div style="background: #000; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;text-transform:lowercase;letter-spacing:-0.1em;font-size:24px; border-bottom:solid 4px #f0ab00; "><font color= #FFF>Mid-term Project Progress</font></div>
+
<big><p style="text-align: left; font-size: 150%;"><center>
<div style="border-left: #797979 solid 12px; padding: 0px 30px 0px 18px; font-family: Arial, Helvetica; font-size:1.25em;text-align:right">
+
[[IS480_Team_wiki:_2013T1_Altitude|<font color="#000000" face=""><ins>''' MAIN WIKI'''</ins></font>]]  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[IS480_Team_wiki:_2013T1_Altitude|<font color="#000000" face=""><ins>''' FINAL WIKI'''</ins></font>]]  </center></p></big><br>
[[Image:acceptanceTeamPhoto.jpg|border|480px]]
+
[[Image:coverphoto.jpg|650px|right]]  
  
</div>
+
<div style="background: #000; padding: 10px; font-weight: bold; line-height: 0.3em; text-indent: 15px;text-transform:lowercase;letter-spacing:-0.1em;font-size:28px; border-bottom:solid 2px #f0ab00; "><font color= #FFF>Mid-term Project
 +
 
 +
Progress Summary</font></div>
 +
 
 +
===Presentation Materials===
 +
{| class="wikitable" style="text-align: center"
 +
|+
 +
|-
 +
! scope="col" width="50" style="background:#190707; color:#ffffff"| S/N
 +
! scope="col" width="200" style="background:#190707;color:#ffffff"| Description
 +
! scope="col" width="150" style="background:#190707;color:#ffffff"| Link
 +
|-
 +
 
 +
|1
 +
|align="center"| Presentation Slide
 +
|align="center"| [[Media:Presentation Link|Link]]
 +
|-
 +
|}
 +
 
 +
=== Overview ===
 +
{| cellpadding="9" style="border: 1px solid darkgray; text-align:center; height:50px"|scope="row"  width="1000" style="text-align: left; background: #F5F5F5"|
 +
 
 +
Current Project Sprint : <b>7</b><br>
 +
The following features will be presented for our mid term presentation:
 +
{| class="wikitable" style="text-align: center"
 +
|+
 +
|-
 +
! scope="col" width="300" style="background:#190707; color:#ffffff"| Features
 +
|-
 +
|align="left"|
 +
*Login
 +
*Enhance Take in requirements from RFP
 +
*Recommendation Options
 +
*Modify Recommendation Options
 +
*Generate Proposal
 +
*Review and Edit Proposal
 +
* Download PDF
 +
|-
 +
|}
 +
 
 +
 
 +
<br>
 +
=== Project Status ===
 +
[[Image:Currentprogress.jpg|800px|center]]<br>
 +
 
 +
Altitude has completed 6 sprints and there are 5 more sprints to work on.
 +
We are in sprint 7 which started on 16 September and will end on 4th October.
 +
 
 +
 
 +
=== Project Highlights ===
 +
[[Image:Schedule v3.png|650px|center]]
 +
 
 +
{| class="wikitable" style="text-align: center; height:100px"
 +
|+
 +
|-
 +
! scope="col"  width="100" style="background-color:#190707"| <font color="#ffffff">EVENT</font>
 +
! scope="col" width="520" style="background-color:#190707"| <font color="#ffffff">HIGHLIGHT / ISSUE</font>
 +
! scope="col" width="520" style="background-color:#190707"| <font color="#ffffff">MITIGATION/CONTINGENCY PLAN</font>
 +
 
 +
|-
 +
! scope="row" style="background-color:#C0C0C0"|Sprint 2
 +
|style="text-align: left;"|'''Implementation of Take in requirements for proposal took longer than expected'''
 +
The team needs more time to explore on the few unfamiliar technologies therefore the implementation was not able to complete on time
 +
|style="text-align: left;"| PM have to reschedule the sprint and every member have to work hard and completed all the uncompleted tasks by the end of sprint
 +
|-
 +
 
 +
! scope="row" style="background: #C0C0C0"| Sprint 3
 +
|style="text-align: left;"|'''Delay in previous sprint'''
 +
Due to the sprint delay in sprint 2, the team had a shorter period of time to finish match options.
 +
|style="text-align: left;"| After reviewing with the client, we decided to reschedule generate proposal, review and edit proposal to be implemented after acceptance. PM also have to review all the future sprint schedule for the team
 +
|-
 +
 
 +
! scope="row" style="background: #C0C0C0"| Sprint 5
 +
|style="text-align: left;"|'''No domain knowledge for the product catalogue'''
 +
When designing the ontologies, the team realized that there is no domain knowledge in the product catalogue for us to reference from. After a clarify requirements session with one of our end users, we realized that we took a wrong approach to design our ontologies.
 +
 
 +
|style="text-align: left;"| We decided to consult prof Lim Ee Peng for better understanding on how ontologies can be created. The team put on more man hours to make sure that the uncompleted tasks can finished on time. 
 +
<br /><br />
 +
 
 +
|}
 +
 
 +
=== Technical Complexity ===
 +
 
 +
The technical complexities of our tools employed are in the following descending order: <br />
 +
 
 +
{| class="wikitable" style="text-align: center; height:100px"
 +
|+
 +
|-
 +
! scope="col"  width="100" style="background-color:#190707"| <font color="#ffffff">COMPLEXITY</font>
 +
! scope="col" width="900" style="background-color:#190707"| <font color="#ffffff">DESCRIPTION</font>
 +
|-
 +
! scope="row" style="background: #C0C0C0"| '''SAPUI5'''
 +
|style="text-align: left;"|
 +
*'''About this complexity:'''
 +
:*
 +
:*
 +
:*
 +
:*
 +
 
 +
*'''Why is it complex?:'''
 +
:*
 +
:*
 +
:*
 +
|-
 +
 
 +
! scope="row" style="background: #C0C0C0"| ''' <br> Ontologies
 +
 
 +
Framework'''
 +
|style="text-align: left;"|
 +
*'''About this complexity:'''
 +
:*
 +
:*
 +
:*
 +
:*
 +
 
 +
*'''Why is it complex?:'''
 +
:*
 +
:*
 +
:*
 +
|-
 +
 
 +
|}
 +
<br>
 +
<div style="background: #000; padding: 10px; font-weight: bold; line-height: 0.3em; text-indent: 15px;text-transform:lowercase;letter-spacing:-0.1em;font-size:28px; border-bottom:solid 2px #f0ab00; "><font color= #FFF>Project Management</font></div>
 +
 
 +
=== Project Status ===
 +
{| class="wikitable" style="text-align: center; height:200px"
 +
|+
 +
|-
 +
! scope="col" width="200" style="background-color:#190707"| <font color="#ffffff">Features</font>
 +
! scope="col" width="180" style="background-color:#190707"| <font color="#ffffff">Status</font>
 +
! scope="col" width="180" style="background-color:#190707"| <font color="#ffffff">Confidence Level (0-1)</font>
 +
! scope="col" width="180" style="background-color:#190707"| <font color="#ffffff">Member In-Charge</font>
 +
|-
 +
 
 +
! scope="row" style="background-color:#C0C0C0"|Login
 +
|style="text-align: center;"|100% developed and deployed
 +
|style="text-align: center;"|1
 +
|style="text-align: center;"|Justin
 +
|-
 +
! scope="row" style="background-color:#C0C0C0"|Take in Requirements from RFP
 +
|style="text-align: center;"|100% developed and deployed
 +
|style="text-align: center;"|1
 +
|style="text-align: center;"|Kenneth
 +
|-
 +
! scope="row" style="background-color:#C0C0C0"|Download PDF
 +
|style="text-align: center;"|100% developed and deployed
 +
|style="text-align: center;"|1
 +
|style="text-align: center;"|Si min
 +
|-
 +
! scope="row" style="background-color:#C0C0C0"|Design ontology
 +
|style="text-align: center;"|100% developed and deployed
 +
|style="text-align: center;"|1
 +
|style="text-align: center;"|Kenneth
 +
|-
 +
! scope="row" style="background-color:#C0C0C0"|Enhance take in RFQ inputs
 +
|style="text-align: center;"|100% developed and deployed
 +
|style="text-align: center;"|1
 +
|style="text-align: center;"|Yao zong
 +
|-
 +
! scope="row" style="background-color:#C0C0C0"|Generate Proposal
 +
|style="text-align: center;"|100% developed and deployed
 +
|style="text-align: center;"|1
 +
|style="text-align: center;"|Max
 +
|-
 +
! scope="row" style="background-color:#C0C0C0"|Review and Edit Proposal
 +
|style="text-align: center;"|100% developed and deployed
 +
|style="text-align: center;"|1
 +
|style="text-align: center;"|Max
 +
|-
 +
! scope="row" style="background-color:#C0C0C0"|Recommended Options
 +
|style="text-align: center;"|100% developed and deployed
 +
|style="text-align: center;"|1
 +
|style="text-align: center;"|Yao zong
 +
|-
 +
! scope="row" style="background-color:#C0C0C0"|Modify Recommended Options
 +
|style="text-align: center;"|100% developed and deployed
 +
|style="text-align: center;"|1
 +
|style="text-align: center;"|Max and Si min
 +
|-
 +
! scope="row" style="background-color:#C0C0C0"|Dashboard
 +
|style="text-align: center;"|Not Started
 +
|style="text-align: center;"|0
 +
|style="text-align: center;"|Max and Si min
 +
|-
 +
! scope="row" style="background-color:#C0C0C0"|Adjust Pricing
 +
|style="text-align: center;"|Not Started
 +
|style="text-align: center;"|0
 +
|style="text-align: center;"|Kenneth and Yao zong
 +
|-
 +
! scope="row" style="background-color:#C0C0C0"|Enhance Edit Proposal
 +
|style="text-align: center;"|Not Started
 +
|style="text-align: center;"|0
 +
|style="text-align: center;"|Justin
 +
|-
 +
! scope="row" style="background-color:#C0C0C0"|State Save
 +
|style="text-align: center;"|Not Started
 +
|style="text-align: center;"|0
 +
|style="text-align: center;"|Max
 +
|-
 +
! scope="row" style="background-color:#C0C0C0"|Furnish Proposal
 +
|style="text-align: center;"|Not Started
 +
|style="text-align: center;"|0
 +
|style="text-align: center;"|Yao Zong
 +
|-
 +
! scope="row" style="background-color:#C0C0C0"|Delete Proposal
 +
|style="text-align: center;"|Not Started
 +
|style="text-align: center;"|0
 +
|style="text-align: center;"|Si min
 +
|-
 +
|}
 +
 
 +
 
 +
=== Project Scope (Planned Vs Mid Term) ===
 +
 
 +
 
 +
[[Image:PlannedVSactual3.jpg|850px]]
 +
 
 +
{| class="wikitable" style="text-align: center; height:50px"
 +
|+
 +
|-
 +
! scope="row"  width="800" style="text-align: left; background: #F5F5F5; font-weight:normal;padding:4px 4px 4px 4px"|
 +
'''Project Scope''' <br>
 +
''' Since inception, there are two changes in the priority circle:''' <br>
 +
*Version 2 '' <br>
 +
**Approve Proposal, Preserve State and Save Current inputs are added'' <br>
 +
*Version 3: Analytic Based Recommendations is removed'' <br>
 +
 
 +
*Altitude have to developed all the core features and secondary features by the end of IS480'' <br>
 +
*Good-to-have features will only need to be developed if the core and secondary features are completed''
 +
 
 +
|}
 +
 
 +
 
 +
=== Current Scope ===
 +
[[Image:Altitude project scope.png|500px]]
 +
<br />
 +
 
 +
=== Schedule (Planned vs Actual till Mid Term)===
 +
 
 +
<b>Features changes</b>
 +
 
 +
[[Image:PlannedVSActualDiagram1.jpg|1300px|center]]
 +
 
 +
 
 +
 
 +
=== Project Metrics ===
 +
 
 +
==== Schedule Metric ====
 +
{| cellpadding="9" style="border: 1px solid darkgray; text-align: center; height:50px"
 +
|scope="row"  width="1200" style="text-align: left; background: #F5F5F5"|
 +
 
 +
The diagram below shows the burn-down charts of the 7 sprints we have completed thus far: <br />
 +
 
 +
'''Key Issues'''<br><br>
 +
1. '''Sprint 2'''
 +
*
 +
*
 +
*
 +
2. '''Sprint 3'''
 +
*
 +
*
 +
3. '''Sprint 5'''
 +
*
 +
*
 +
<br>
 +
'''Links'''<br>
 +
'''1. [https://wiki.smu.edu.sg/is480/Altitude_Project_Metrics Altitude Metrics|Schedule Metric Calculation]'''<br />
 +
'''2. Schedule Metric Documentation for Sprint Number:
 +
[https://docs.google.com/spreadsheet/ccc?key=0As6DABhgNixcdEY1MFd6REh3RGxMWWNiemZnMDdaN2c#gid=0  1],
 +
[https://docs.google.com/spreadsheet/ccc?key=0As6DABhgNixcdEY1MFd6REh3RGxMWWNiemZnMDdaN2c#gid=1  2],
 +
[https://docs.google.com/spreadsheet/ccc?key=0As6DABhgNixcdEY1MFd6REh3RGxMWWNiemZnMDdaN2c#gid=8  3],
 +
[https://docs.google.com/spreadsheet/ccc?key=0As6DABhgNixcdEY1MFd6REh3RGxMWWNiemZnMDdaN2c#gid=3  4],
 +
[https://docs.google.com/spreadsheet/ccc?key=0As6DABhgNixcdEY1MFd6REh3RGxMWWNiemZnMDdaN2c#gid=14 5],
 +
<br>
 +
<big><big>'''Release Burn-down Chart'''</big></big><br><br>
 +
<br /><br />
 +
 
 +
 
 +
 
 +
 
 +
<big><big>'''Burn-down Charts'''</big></big><br><br>
 +
[[Image:Burndownchart1to4.jpg|525px]]
 +
|}
 +
 
 +
==== Bug Metric ====
 +
 
 +
{| cellpadding="9" style="border: 1px solid darkgray; text-align: center; height:50px"
 +
|scope="row"  width="1200" style="text-align: left; background: #F5F5F5"|
 +
 
 +
 
 +
 
 +
|}
 +
 
 +
 
 +
 
 +
 
 +
==== Risk Management ====
 +
{| cellpadding="9" style="border: 1px solid darkgray; text-align: center; height:50px"
 +
|scope="row"  width="1200" style="text-align: left; background: #F5F5F5"|
 +
 
 +
Prioritised Risks as at mid-term. Full entries as shown under the Project Management and Technological Implementation headings in the '''[[IS480_Team_wiki:_2012T1_Timber_Werkz_Risks| Risk Management Table]]'''.
 +
 
 +
{| class="wikitable" style="text-align: center; height:80px"
 +
|+
 +
|-
 +
! scope="col"  width="50" style="background-color:#19070B"| <font color="#ffffff">S/N</font>
 +
! scope="col" width="350" style="background-color:#19070B"| <font color="#ffffff">Risk Description</font>
 +
! scope="col" width="250" style="background-color:#19070B"| <font color="#ffffff">Impact</font>
 +
! scope="col"  width="120" style="background-color:#19070B"| <font color="#ffffff">Impact Level <br> (High/Med/Low)</font>
 +
! scope="col" width="120" style="background-color:#19070B"| <font color="#ffffff">Likelihood <br> (High/Med/Low)</font>
 +
! scope="col" width="500" style="background-color:#19070B"| <font color="#ffffff">Mitigation Strategy</font>
 +
! scope="col" width="100" style="background-color:#19070B"| <font color="#ffffff">Status</font>
 +
|-
 +
 
 +
!scope="row" style="background-color:#FAFDC3"|
 +
'''1'''
 +
|colspan="6" height:100px; style="background-color:#FAFDC3; text-align: left;"|
 +
'''Project Management'''
 +
|-
 +
 
 +
! scope="row" |
 +
'''1.1'''
 +
|style="text-align: left;"|
 +
*The team required longer period of time to work on the required tasks.
 +
|style="text-align: left;"|
 +
*Scope and schedule of the project affected
 +
|style="text-align: center;"|
 +
High
 +
|style="text-align: center;"|
 +
High
 +
|style="text-align: left;"|
 +
*Frequent trips to consult domain experts from IMC is needed to ensure that all requirements are clarify
 +
|style="text-align: center; color:#D31601"|
 +
'''Mitigation strategy <br> in force'''
 +
|-
 +
!scope="row" style="background-color:#FAFDC3"|
 +
'''2'''
 +
|colspan="6" height:100px; style="background-color:#FAFDC3; text-align: left;"|
 +
'''Client Management'''
 +
|-
 +
 
 +
! scope="row" |
 +
'''2.1'''
 +
|style="text-align: left;"|
 +
*Change requests expected from client as SIS is developed from scratch
 +
|style="text-align: left;"|
 +
*Scope and schedule of the project affected 
 +
|style="text-align: center;"|
 +
High
 +
|style="text-align: center;"|
 +
Medium
 +
|style="text-align: left;"|
 +
*PM have to evaluate the change request and re-adjust the project schedule accordingly
 +
|style="text-align: center; color:#D31601"|
 +
'''Mitigation strategy <br> in force'''
 +
|-
 +
 
 +
!scope="row" style="background-color:#FAFDC3"|
 +
'''3'''
 +
|colspan="6" height:100px; style="background-color:#FAFDC3; text-align: left;"|
 +
'''Team Management'''
 +
|-
 +
 
 +
! scope="row" |
 +
'''3.1'''
 +
|style="text-align: left;"|
 +
*Conflict amongst team members due to different working styles,different commitment
 +
|style="text-align: left;"|
 +
*Project progress will be affected
 +
|style="text-align: center;"|
 +
Medium
 +
|style="text-align: center;"|
 +
Medium
 +
|style="text-align: left;"|
 +
*Project Manager to organize a “Trashing Out” session for the team. Members to come to an understanding for the team to progress forward.
 +
|style="text-align: center; color:#D31601"|
 +
'''Mitigation strategy <br> in force'''
 +
|-
 +
 
 +
!scope="row" style="background-color:#FAFDC3"|
 +
'''4'''
 +
|colspan="6" height:100px; style="background-color:#FAFDC3; text-align: left;"|
 +
'''Team Management'''
 +
|-
 +
 
 +
! scope="row" |
 +
'''4.1'''
 +
|style="text-align: left;"|
 +
*Members unfamiliar with technologies
 +
|style="text-align: left;"|
 +
*Project iteration takes longer to completed which affects the project schedule to be delayed
 +
|style="text-align: center;"|
 +
High
 +
|style="text-align: center;"|
 +
High
 +
|style="text-align: left;"|
 +
*Spend more time on the current sprint and consult external experts for help
 +
|style="text-align: center; color:#D31601"|
 +
'''Mitigation strategy <br> in force'''
 +
|-
 +
 
 +
 
 +
 
 +
 
 +
 
 +
|}
 +
 
 +
 
 +
|}
 +
 
 +
<br>
 +
<div style="background: #000; padding: 10px; font-weight: bold; line-height: 0.3em; text-indent: 15px;text-
 +
 
 +
transform:lowercase;letter-spacing:-0.1em;font-size:28px; border-bottom:solid 2px #f0ab00; "><font color= #FFF>Project Quality</font></div>
 +
 
 +
=== Intermediate Deliverables ===
 +
 
 +
{| class="wikitable"
 +
|+
 +
|-
 +
! scope="col"  width="100" style="background:#190707; color:#ffffff"|Stage
 +
! scope="col" width="300" style="background:#190707; color:#ffffff"| Specification
 +
! scope="col" width="300" style="background:#190707; color:#ffffff"| Modules
 +
|-
 +
!scope="row" rowspan="2" align="center"|Project Management
 +
|align="center"| Minutes
 +
|align="left"|
 +
*[https://wiki.smu.edu.sg/is480/Altitude_Project_Meeting_Minutes#Client_Meeting Client Minutes]
 +
*[https://wiki.smu.edu.sg/is480/Altitude_Project_Meeting_Minutes#Supervisor_Meeting Supervisor Minutes]
 +
*[https://wiki.smu.edu.sg/is480/Altitude_Project_Meeting_Minutes#Group_Meeting Group Minutes]
 +
|-
 +
|align="center"| Metrics
 +
|align="left"|
 +
*[https://wiki.smu.edu.sg/is480/Altitude_Project_Metrics#Schedule_Metric Schedule Metric]
 +
*[https://wiki.smu.edu.sg/is480/Altitude_Project_Metrics#Bug_Metric Bug Metric]
 +
|-
 +
!scope="row" align="center"|Requirements
 +
|align="center"| User Interface Mockups and Videos
 +
|align="left"|
 +
*[https://wiki.smu.edu.sg/is480/Altitude_User_Interfaces#UI User Interface Mockup]
 +
|-
 +
!scope="row" align="center"|Analysis
 +
|align="center"| Use case
 +
|align="left"|
 +
*[https://wiki.smu.edu.sg/is480/Image:Usecases.png#Use_cases Use cases]
 +
 
 +
|-
 +
!scope="row" rowspan="4" align="center"|Design
 +
|align="center"| Deployment Diagram
 +
|align="left"|
 +
 
 +
*[https://wiki.smu.edu.sg/is480/Image:DeploymentDiagram.png#Deployment_Diagram Deployment Diagram]
 +
 
 +
|-
 +
|align="center"| System Architecture Diagram
 +
|align="left"|
 +
*[https://wiki.smu.edu.sg/is480/Image:ArchitectureDiagram1.png#Architecture_Diagram Architecture Diagram]
 +
 
 +
 
 +
|-
 +
|align="center"| ER diagram
 +
|align="left"|
 +
*[https://wiki.smu.edu.sg/is480/Image:ERDiagram.jpg#ER_Diagram ER Diagram]
 +
 
 +
|-
 +
!scope="row" rowspan="2" align="center"|Testing
 +
|align="center"| User Test Plan
 +
|align="left"|
 +
|-
 +
|}
 +
 
 +
 
 +
 
 +
=== Deployment ===
 +
 
 +
{| class="wikitable"
 +
|+
 +
|-
 +
! scope="col"  width="100" style="background:#190707; color:#ffffff"|Area
 +
! scope="col" width="300" style="background:#190707; color:#ffffff"| Details
 +
|-
 +
!scope="row" align="center"|Development Environment
 +
|align="left"|
 +
 
 +
|-
 +
!scope="row" align="center"|Database
 +
|align="left"|
 +
 
 +
 
 +
 
 +
|-
 +
!scope="row" align="center"|Web Services
 +
|align="left"|
 +
 
 +
|-
 +
!scope="row" align="center"|Web Links
 +
|align="left"|
 +
|-
 +
|}
 +
 
 +
 
 +
=== User Testing 1 ===
 +
 
 +
{| class="wikitable"
 +
|+
 +
|-
 +
! scope="col"  width="100" style="background:#190707; color:#ffffff"|Area
 +
! scope="col" width="300" style="background:#190707; color:#ffffff"| Details
 +
|-
 +
!scope="row" align="center"|Objectives
 +
|align="left"|
 +
|-
 +
!scope="row" align="center"|Details
 +
|align="left"|
 +
|-
 +
!scope="row" align="center"|Method
 +
|align="left"|
 +
|-
 +
!scope="row" align="center"|Data Collection
 +
|align="left"|
 +
|-
 +
!scope="row" align="center"|Scope of features tested
 +
|align="left"|
 +
|-
 +
|}
 +
 
 +
 
 +
<br>
 +
<div style="background: #000; padding: 10px; font-weight: bold; line-height: 0.3em; text-indent: 15px;text-
 +
 
 +
transform:lowercase;letter-spacing:-0.1em;font-size:28px; border-bottom:solid 2px #f0ab00; "><font color= #FFF>Reflections</font></div>
 +
<br>
 +
 
 +
[[Image:IMG 1047.JPG|500px|center]]
 +
<br>
 +
{| cellpadding="9" style="border: 1px solid darkgray; text-align: center; height:50px"
 +
|scope="row"  width="1200" style="text-align: left; background: #F5F5F5"|
 +
 
 +
====<font size = 4>'''Team Reflection </font>====
 +
'''1. Due to unfamiliar technologies, schedule is delay and team have to work hard to completed all tasks<br>
 +
 
 +
'''2. There are many unexpected situations that the team have to handle in terms of client and project management<br>
 +
 
 +
<br>
 +
 
 +
[[Image:Reflection3.jpg|600px|centre]]
 +
 
 +
 
 +
 
 +
|}

Revision as of 21:46, 1 October 2013

Altitude logo black.jpg

MAIN WIKI            FINAL WIKI


Coverphoto.jpg
Mid-term Project Progress Summary

Presentation Materials

S/N Description Link
1 Presentation Slide Link

Overview

Current Project Sprint : 7
The following features will be presented for our mid term presentation:
Features
  • Login
  • Enhance Take in requirements from RFP
  • Recommendation Options
  • Modify Recommendation Options
  • Generate Proposal
  • Review and Edit Proposal
  • Download PDF



Project Status

Currentprogress.jpg


Altitude has completed 6 sprints and there are 5 more sprints to work on. We are in sprint 7 which started on 16 September and will end on 4th October.


Project Highlights

Schedule v3.png
EVENT HIGHLIGHT / ISSUE MITIGATION/CONTINGENCY PLAN
Sprint 2 Implementation of Take in requirements for proposal took longer than expected

The team needs more time to explore on the few unfamiliar technologies therefore the implementation was not able to complete on time

PM have to reschedule the sprint and every member have to work hard and completed all the uncompleted tasks by the end of sprint
Sprint 3 Delay in previous sprint

Due to the sprint delay in sprint 2, the team had a shorter period of time to finish match options.

After reviewing with the client, we decided to reschedule generate proposal, review and edit proposal to be implemented after acceptance. PM also have to review all the future sprint schedule for the team
Sprint 5 No domain knowledge for the product catalogue

When designing the ontologies, the team realized that there is no domain knowledge in the product catalogue for us to reference from. After a clarify requirements session with one of our end users, we realized that we took a wrong approach to design our ontologies.

We decided to consult prof Lim Ee Peng for better understanding on how ontologies can be created. The team put on more man hours to make sure that the uncompleted tasks can finished on time.



Technical Complexity

The technical complexities of our tools employed are in the following descending order:

COMPLEXITY DESCRIPTION
SAPUI5
  • About this complexity:
  • Why is it complex?:

Ontologies

Framework

  • About this complexity:
  • Why is it complex?:


Project Management

Project Status

Features Status Confidence Level (0-1) Member In-Charge
Login 100% developed and deployed 1 Justin
Take in Requirements from RFP 100% developed and deployed 1 Kenneth
Download PDF 100% developed and deployed 1 Si min
Design ontology 100% developed and deployed 1 Kenneth
Enhance take in RFQ inputs 100% developed and deployed 1 Yao zong
Generate Proposal 100% developed and deployed 1 Max
Review and Edit Proposal 100% developed and deployed 1 Max
Recommended Options 100% developed and deployed 1 Yao zong
Modify Recommended Options 100% developed and deployed 1 Max and Si min
Dashboard Not Started 0 Max and Si min
Adjust Pricing Not Started 0 Kenneth and Yao zong
Enhance Edit Proposal Not Started 0 Justin
State Save Not Started 0 Max
Furnish Proposal Not Started 0 Yao Zong
Delete Proposal Not Started 0 Si min


Project Scope (Planned Vs Mid Term)

PlannedVSactual3.jpg

Project Scope
Since inception, there are two changes in the priority circle:

  • Version 2
    • Approve Proposal, Preserve State and Save Current inputs are added
  • Version 3: Analytic Based Recommendations is removed
  • Altitude have to developed all the core features and secondary features by the end of IS480
  • Good-to-have features will only need to be developed if the core and secondary features are completed


Current Scope

Altitude project scope.png

Schedule (Planned vs Actual till Mid Term)

Features changes

PlannedVSActualDiagram1.jpg


Project Metrics

Schedule Metric

The diagram below shows the burn-down charts of the 7 sprints we have completed thus far:

Key Issues

1. Sprint 2

2. Sprint 3

3. Sprint 5


Links
1. Altitude Metrics|Schedule Metric Calculation
2. Schedule Metric Documentation for Sprint Number: 1, 2, 3, 4, 5,
Release Burn-down Chart





Burn-down Charts

Burndownchart1to4.jpg

Bug Metric




Risk Management

Prioritised Risks as at mid-term. Full entries as shown under the Project Management and Technological Implementation headings in the Risk Management Table.

S/N Risk Description Impact Impact Level
(High/Med/Low)
Likelihood
(High/Med/Low)
Mitigation Strategy Status

1

Project Management

1.1

  • The team required longer period of time to work on the required tasks.
  • Scope and schedule of the project affected

High

High

  • Frequent trips to consult domain experts from IMC is needed to ensure that all requirements are clarify

Mitigation strategy
in force

2

Client Management

2.1

  • Change requests expected from client as SIS is developed from scratch
  • Scope and schedule of the project affected

High

Medium

  • PM have to evaluate the change request and re-adjust the project schedule accordingly

Mitigation strategy
in force

3

Team Management

3.1

  • Conflict amongst team members due to different working styles,different commitment
  • Project progress will be affected

Medium

Medium

  • Project Manager to organize a “Trashing Out” session for the team. Members to come to an understanding for the team to progress forward.

Mitigation strategy
in force

4

Team Management

4.1

  • Members unfamiliar with technologies
  • Project iteration takes longer to completed which affects the project schedule to be delayed

High

High

  • Spend more time on the current sprint and consult external experts for help

Mitigation strategy
in force



Project Quality

Intermediate Deliverables

Stage Specification Modules
Project Management Minutes
Metrics
Requirements User Interface Mockups and Videos
Analysis Use case
Design Deployment Diagram
System Architecture Diagram


ER diagram
Testing User Test Plan


Deployment

Area Details
Development Environment
Database


Web Services
Web Links


User Testing 1

Area Details
Objectives
Details
Method
Data Collection
Scope of features tested



Reflections


IMG 1047.JPG


Team Reflection

1. Due to unfamiliar technologies, schedule is delay and team have to work hard to completed all tasks

2. There are many unexpected situations that the team have to handle in terms of client and project management


Reflection3.jpg