HeaderSIS.jpg

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

From IS480
Jump to navigation Jump to search
Line 41: Line 41:
 
|- style= "background: #00275E; color: #FFFFFF; text-align: center; font-weight: bold; font-size:13px;"
 
|- style= "background: #00275E; color: #FFFFFF; text-align: center; font-weight: bold; font-size:13px;"
 
| No.
 
| No.
| Type of Risk
+
| Description
| Risk Statement
+
| Expected Learning Outcome
| Likelihood (H/M/L)
+
 
| Impact
 
| Mitigation Strategy / Contingency Plan
 
 
|-
 
|-
| colspan=6 style= "background: #6D98AB; color: #000000; font-weight: bold; padding: 5px; font-size: 14px; text-align: center" valign="top" | Schedule Risk
+
| colspan=6 style= "background: #6D98AB; color: #000000; font-weight: bold; padding: 5px; font-size: 14px; text-align: center" valign="top" | Technological application skills
 
|-
 
|-
 
|- style= "background: #FFFFFF; "
 
|- style= "background: #FFFFFF; "
 
| 1
 
| 1
| Technical
+
| Improved coding efficiency level
| Schedule. Team members are busy with school work
+
| 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.  
| <font color="#FF0000">High</font><br> <s>Low</s>
 
| <font color="#FF0000">High</font><br> <s>Medium</s>
 
| Plan ahead and make sure that all team members are comfortable with the work load and free to meet on the dates scheduled. Team members to encourage each other and make extra effort to accommodate to each other and keep in pace with the schedule. Set weekly compulsory meeting dates.
 
 
|-  
 
|-  
| colspan=6 style= "background: #6D98AB; color: #000000; font-weight: bold; padding: 5px; font-size: 14px; text-align: center" valign="top" | Scope Risk
+
| colspan=6 style= "background: #6D98AB; color: #000000; font-weight: bold; padding: 5px; font-size: 14px; text-align: center" valign="top" | Project Management
 
|-
 
|-
 
|- style= "background: #FFFFFF; "
 
|- style= "background: #FFFFFF; "
| 2
+
| 2.1
| Internal
+
| Prioritizing of deliverables
| Project scope is too big
+
| 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.
| Medium
 
| High
 
| <ul>
 
<li>Discuss with clients and supervisor on our scope
 
<li>Priortise the more important functions that can value-add our application
 
</ul>
 
 
|-  
 
|-  
 +
|- 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=6 style= "background: #6D98AB; color: #000000; font-weight: bold; padding: 5px; font-size: 14px; text-align: center" valign="top" | Technical Risk
 
| colspan=6 style= "background: #6D98AB; color: #000000; font-weight: bold; padding: 5px; font-size: 14px; text-align: center" valign="top" | Technical Risk
 
|-
 
|-

Revision as of 11:56, 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.
Technical Risk
3 Technical Search function. Team is unfamiliar with the implementation techniques. Medium High
  • Set aside time for exploration of techniques
  • Insert buffer for this implementation
4 Technical Instant resume template. Difficult and time-consuming to implement because need to create CSS from scratch. Medium Medium
  • Scheduled for early implementation to prevent delay
  • Include buffer time for this implementation
5 Technical Deployment. Deploying to client server may affect the functioning of certain parts of the application. Medium High Always deploy in advance (1 week before) & test run the application.
Individual Reflection
Team Reflection OHW.png