HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2016T2 ProgneSIS MidTermWiki"

From IS480
Jump to navigation Jump to search
Line 48: Line 48:
 
<h3>Project Highlights</h3>
 
<h3>Project Highlights</h3>
 
Our project schedule is divided into 13 iterations.  
 
Our project schedule is divided into 13 iterations.  
*As of 14 February 2016, we have completed 80% of our <b>development</b>.
+
*As of 29 January 2016, we have completed 65% of our <b>development</b>.
 
* Two user testing with actual users (before midterms)  
 
* Two user testing with actual users (before midterms)  
* <b>Beta release</b> on XX February 2016, with our VersaFleet Analytics potential users using our application to track their Delivery Fulfilment Rate (before midterms). <h3>[[IS480 Team wiki:Check out our beta release here!|Check out our beta release here!]]</h3>
 
 
* Current iteration: 6
 
* Current iteration: 6
 
* Iteration 6: 10 January 2016 - 23 January 2016
 
* Iteration 6: 10 January 2016 - 23 January 2016
Line 63: Line 62:
  
 
<h3>Development Progress</h3>
 
<h3>Development Progress</h3>
Status: XX%
+
Status: 80%
 
[[IS480 Team wiki:1000px|1000px]]
 
[[IS480 Team wiki:1000px|1000px]]
  

Revision as of 21:24, 14 February 2016

Progensis.png
Team Prognesis Icon Home.png

HOME

  Team Prognesis Icon AboutUs.png

ABOUT US

  Team Prognesis Icon Overview.png

PROJECT OVERVIEW

  Team Prognesis Icon ProjectManagement.png

PROJECT MANAGEMENT

  Team Prognesis Icon Documentation.png

DOCUMENTATION

 
Main Wiki Mid Term Wiki Final Wiki


Project Progress Summary

Midterm slides

Deployed Link:

Project Highlights

Our project schedule is divided into 13 iterations.

  • As of 29 January 2016, we have completed 65% of our development.
  • Two user testing with actual users (before midterms)
  • Current iteration: 6
  • Iteration 6: 10 January 2016 - 23 January 2016
  • Major changes in requirements resulted in re-scoping in iteration 3-4 and hence major changes in schedule.
  • User Testing 1 was delayed by a month as a result of re-scoping.
  • Instead of different metrics for logistics SMEs, we focused on different dimensions for Delivery Fulfilment Rate.
  • Parts of our development had to follow the schedule of our client (when they could provide us certain information/data).



Development Progress

Status: 80% 1000px

  • The team is confident of completing the project and delivering the application on time.

Project Management

Project Status


Project Schedule (Planned vs Actual)


Project Metrics


Project Risks


Technical Complexity


Quality of Product

Intermediate Deliverables


Deployment


Testing


Reflection

Team Reflection


Individual Reflection