HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki 2017T2 Oops Task Metric"

From IS480
Jump to navigation Jump to search
Line 56: Line 56:
 
|style= "padding-left:10px" |1) Important to get a server up and running to test the REST web service.
 
|style= "padding-left:10px" |1) Important to get a server up and running to test the REST web service.
 
2) Important to get the coordinates of the user to accurately get user coordinates.  
 
2) Important to get the coordinates of the user to accurately get user coordinates.  
 +
|-
 +
| style="text-align:center" | 3
 +
| style= "padding-left:10px" | Sandeep has left the group due to personal issues.
 +
 +
|style= "padding-left:10px" | Need to reschedule future iterations
 +
|-
  
 
|}
 
|}

Revision as of 22:23, 6 November 2016

Oopslogo.png
HomeButton.png Home ShakeHands.png About Us Glyphicons 042 pie chart.png Project Overview Calendaricon.png Project Management Tableicon.png Project Documentation


Schedule Change Management Risk Managment Task Metric Bug Metric



Summary of Task Metrics (by iteration)


Iteration Progress Action
1 We have finished doing the UI prototyping and how the overall app architecture and finished out market research.

We still need to read up more about android, UI prototyping to be able to perform the critical functions.

No action needed.
2 Sandeep has done the back-end coding of the PHP files that link together with the android front end through a REST system.

Zhi Hui is dealing with the GPS coordinates and ensuring that the GPS comes out fine on the screen.

Ke Ting is still refining the market value proposition to better understand the product and create value for the sponsor.

Ruixue is doing the user interface and overall user experience to better gauge the output.

Yifei is doing the quality assurance of the app through testing and debugging.

1) Important to get a server up and running to test the REST web service.

2) Important to get the coordinates of the user to accurately get user coordinates.

3 Sandeep has left the group due to personal issues. Need to reschedule future iterations
Score Action
TM < 0.9 Team is ahead of the schedule.
  • Re-schedule for next iteration is needed.
  • Re-evaluate team's availability and complexity of the tasks.
  • Move tasks from the following iteration to the next iteration.
TM >= 0.9 and TM <= 1.1 Team is on track. Yay! :D
TM > 1.1 Team is behind the schedule.
  • Re-schedule for next iteration is needed.
  • Re-evaluate team's availability and complexity of the tasks.
  • Move less important tasks to next iteration.

Task Metric Score = Tasks to complete / Tasks completed