HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2012T1 One-hit Wonder MT Team Reflection"

From IS480
Jump to navigation Jump to search
 
(20 intermediate revisions by 2 users not shown)
Line 2: Line 2:
 
{| style="background-color:none; color:#ffffff; border-bottom:3px dotted #000000; border-top:3px dotted #000000; border-left:3px dotted #000000; border-right:3px dotted #000000;" width="100%" cellspacing="0" cellpadding="0" valign="top" |
 
{| style="background-color:none; color:#ffffff; border-bottom:3px dotted #000000; border-top:3px dotted #000000; border-left:3px dotted #000000; border-right:3px dotted #000000;" width="100%" cellspacing="0" cellpadding="0" valign="top" |
 
| style="padding:0.3em; font-size:100%; background-color:#ffffff; text-align:center; " width="6%" |
 
| style="padding:0.3em; font-size:100%; background-color:#ffffff; text-align:center; " width="6%" |
[[Image:HomeOHW.png]][[IS480_Team_wiki:_2012T1_One-hit_Wonder | <font color="#000000">Main Wiki</font>]]
+
[[Image:Undo-icon.png|22px]][[IS480_Team_wiki:_2012T1_One-hit_Wonder | <font color="#000000">Main Wiki</font>]]
 +
 
 +
| style="padding:0.3em; font-size:100%; background-color:#ffffff; text-align:center; color:#ffffff" width="6%" |
 +
[[Image:HomeOHW.png]][[IS480_Team_wiki:_2012T1_One-hit_Wonder_Mid_Term | <font color="#000000">Home</font>]]
  
 
| style="background:none;" width="1%" |
 
| style="background:none;" width="1%" |
Line 10: Line 13:
 
| style="background:none;" width="1%" |
 
| style="background:none;" width="1%" |
 
| style="padding:0.3em; font-size:100%; background-color:#ffffff; text-align:center; color:#ffffff" width="10%" |  
 
| style="padding:0.3em; font-size:100%; background-color:#ffffff; text-align:center; color:#ffffff" width="10%" |  
[[Image:Chart_line_icon&24.png|20px]][[IS480_Team_wiki:_2012T1_One-hit_Wonder_MT_Project Metrics | <font color="#000000">Project Metrics</font>]]
+
[[Image:Chart_line_icon&24.png|21px]][[IS480_Team_wiki:_2012T1_One-hit_Wonder_MT_Project Metrics | <font color="#000000">Project Metrics</font>]]
  
 
| style="background:none;" width="1%" |
 
| style="background:none;" width="1%" |
Line 18: Line 21:
 
| style="background:none;" width="1%" |
 
| style="background:none;" width="1%" |
 
| style="padding:0.3em; font-size:100%; background-color:#ffffff; text-align:center; color:#ffffff" width="10%" |
 
| style="padding:0.3em; font-size:100%; background-color:#ffffff; text-align:center; color:#ffffff" width="10%" |
[[Image:Users24.png|22px]][[IS480_Team_wiki:_2012T1_One-hit_Wonder_MT_UT1 | <font color="#000000">User Testing 1</font>]]
+
[[Image:Users24.png|22px]][[IS480_Team_wiki:_2012T1_One-hit_Wonder_MT_Usability_Studies | <font color="#000000">Usability Studies</font>]]
  
 
| style="background:none;" width="1%" |
 
| style="background:none;" width="1%" |
| style="padding:0.3em; font-size:100%; background-color:#000000; text-align:center; color:#ffffff" width="10%" |  
+
| style="padding:0.3em; font-size:100%; background-color:#000000; -webkit-box-shadow: 0px 0px 6px #000000; text-align:center; color:#ffffff" width="10%" |  
[[Image:TeamRef_White.png|22px]][[IS480_Team_wiki:_2012T1_One-hit_Wonder_MT_Team_Reflection | <font color="#ffffff">Team Reflection</font>]]
+
[[Image:TeamRef_White.png|20px]][[IS480_Team_wiki:_2012T1_One-hit_Wonder_MT_Team_Reflection | <font color="#ffffff">Team Reflection</font>]]
 +
 
 +
|}
 +
 
 +
{| class="wikitable" cellpadding="15"
 +
|-
 +
| style="background: #ffffff; color: #000000; font-weight: bold; text-indent: 2px; width: 10%; font-size:22px; border: 1px solid #ffffff" valign="top" | <b>Learning Outcome</b>
 +
|-
 +
 
 +
| style="background: #000000; border:1px solid #ffffff; color: #FFFFFF; font-weight: bold; padding: 10px 10px 0 15px; font-size: 14px;" valign="top"  |
 +
|-
 +
|}
 +
 
 +
{| class="wikitable" cellpadding="15"
 +
|- style= "background: #00275E; color: #FFFFFF; text-align: center; font-weight: bold; font-size:13px;"
 +
| No.
 +
| Description
 +
| Expected Learning Outcome
 +
 
 +
|-
 +
| colspan=3 style= "background: #6D98AB; color: #000000; font-weight: bold; padding: 5px; font-size: 14px; text-align: center" valign="top" | Technological application skills
 +
|-
 +
|- style= "background: #FFFFFF; "
 +
| 1
 +
| Improved coding efficiency level
 +
| As we commence on the second half of our project, we are more familiar with Play framework and other technologies.  Thus, we are now more confident in completing this project on time and the technical risk for our project has become relatively low.
 +
|-
 +
| colspan=3 style= "background: #6D98AB; color: #000000; font-weight: bold; padding: 5px; font-size: 14px; text-align: center" valign="top" | Project Management
 +
|-
 +
|- style= "background: #FFFFFF; "
 +
| 2.1
 +
| Prioritizing of deliverables
 +
| We prioritized our deliverables according to its risk level in order for us to allocate enough time for other more complex features. This has helped to reduce the unnecessary stress and prevent us from spending excessive time on non-crucial tasks.
 +
|-
 +
|- style= "background: #FFFFFF; "
 +
| 2.2
 +
| Strategic resource allocation
 +
| Our group aim is to build a robust and stable application within the allocated time frame. We thus have to allocate tasks based on each individual’s strength and schedule in order for us to produce optimal work within the limited time period.
 +
|-
 +
 
 +
| colspan=3 style= "background: #6D98AB; color: #000000; font-weight: bold; padding: 5px; font-size: 14px; text-align: center" valign="top" | Stakeholder Management
 +
|-
 +
|- style= "background: #FFFFFF; "
 +
| 3.1
 +
| Essentiality of communication and cooperation
 +
| Throughout the entire project, we make it a point to meet up with the supervisor and clients as frequently as possible to update them on the progress of our project so as to keep them in the loop. This also ensured that all parties are up to date with the current status of the project and allowed us to conduct discussion should there be any change in the requirement of the project. On top of that, we engage in open discussion. Every individual is encouraged to voice out his/her opinions so as to minimize conflicts and misunderstandings among the group and also between shareholders.
 +
|-
 +
|- style= "background: #FFFFFF; "
 +
| 3.2
 +
| Managing client expectations
 +
| We conduct regular meetings with the clients to understand their expectations as we progress into the different stages of our project.  This helped to ensure that our final product would meet the clients’ business value. In addition, from time to time, we would provide creative ideas for our clients so as to constantly improve our current features.
 +
|}
 +
<br>
  
 +
{| class="wikitable" cellpadding="15"
 +
|-
 +
| style="background: #ffffff; color: #000000; font-weight: bold; text-indent: 2px; width: 10%; font-size:22px; border: 1px solid #ffffff" valign="top" | <b>Individual Reflection</b>
 +
|-
 +
 +
| style="background: #000000; border:1px solid #ffffff; color: #FFFFFF; font-weight: bold; padding: 10px 10px 0 15px; font-size: 14px;" valign="top"  |
 +
|-
 
|}
 
|}
 +
 +
[[Image:Team_Reflection_OHW.png|center ]]

Latest revision as of 12:00, 8 October 2012

Undo-icon.png Main Wiki

HomeOHW.png Home

Calendar 2 icon&48.png Project Management

Chart line icon&24.png Project Metrics

20px‎ Technical Complexity

Users24.png Usability Studies

TeamRef White.png Team Reflection

Learning Outcome
No. Description Expected Learning Outcome
Technological application skills
1 Improved coding efficiency level As we commence on the second half of our project, we are more familiar with Play framework and other technologies. Thus, we are now more confident in completing this project on time and the technical risk for our project has become relatively low.
Project Management
2.1 Prioritizing of deliverables We prioritized our deliverables according to its risk level in order for us to allocate enough time for other more complex features. This has helped to reduce the unnecessary stress and prevent us from spending excessive time on non-crucial tasks.
2.2 Strategic resource allocation Our group aim is to build a robust and stable application within the allocated time frame. We thus have to allocate tasks based on each individual’s strength and schedule in order for us to produce optimal work within the limited time period.
Stakeholder Management
3.1 Essentiality of communication and cooperation Throughout the entire project, we make it a point to meet up with the supervisor and clients as frequently as possible to update them on the progress of our project so as to keep them in the loop. This also ensured that all parties are up to date with the current status of the project and allowed us to conduct discussion should there be any change in the requirement of the project. On top of that, we engage in open discussion. Every individual is encouraged to voice out his/her opinions so as to minimize conflicts and misunderstandings among the group and also between shareholders.
3.2 Managing client expectations We conduct regular meetings with the clients to understand their expectations as we progress into the different stages of our project. This helped to ensure that our final product would meet the clients’ business value. In addition, from time to time, we would provide creative ideas for our clients so as to constantly improve our current features.


Individual Reflection
Team Reflection OHW.png