Difference between revisions of "IS480 Team wiki: 2012T2 box.us Project Management"

From IS480
Jump to navigation Jump to search
Line 84: Line 84:
* Iteration 2 Schedule Ratio: [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdHo2ZmNTSUxWcjZQTm1hbzU3VkhYQlE#gid=31 Iteration Report]
* Iteration 2 Schedule Ratio: [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdHo2ZmNTSUxWcjZQTm1hbzU3VkhYQlE#gid=31 Iteration Report]
* Iteration 3 Schedule Ratio(Acceptance): [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdHo2ZmNTSUxWcjZQTm1hbzU3VkhYQlE#gid=32 Iteration Report @ Acceptance]
* Iteration 3 Schedule Ratio(Acceptance): [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdHo2ZmNTSUxWcjZQTm1hbzU3VkhYQlE#gid=32 Iteration Report @ Acceptance]

Revision as of 18:46, 15 January 2013


Home Stakeholders Project Overview Project Management Documentation Learning Outcomes Useful Links

Team Box.us is a project team that consists of 6 individuals with varying (and complementing skillsets). The team set out with the following beliefs to achieve at the end of the project:

  • Create value for organizations - Value could be business value and also social value to our sponsors.
  • Sustainable implementations - Our team believes in having projects that would be sustainable and be able to bring value to the organizations in a long run
  • Team Learning - Our team believes in learning during the entire development process so that the experience would be enriching for the organization, the team and the individuals invovled.

Our Project Milestone

Project Milestones - Project Milestones List

Project Schedule - Project Schedule on Google Docs


  • To ensure that all project tasks are completed on time and milestones are met.

Schedule Ratio = Actual Duration / Planned Duration

Schedule Ratio Description Response
< 0.8 Team is ahead of schedule Proceed to embark on the next task if possible
0.8 - 1.2 Within healthy schedule range No actions required for ratio below 1.
Keep close monitor on tasks that have a ratio of more than one.
Project Manager to review schedule to see which tasks have gone over time. If necessary, review time estimations for tasks in the next iteration.
> 1.2 Team is behind schedule Team is behind schedule. Project Manager identifies root cause of the delay. Project Manager would increase the velocity of the team in the upcoming iteration to complete the tasks on time.



  • To minimize the number of bugs that surface during the duration of a sprint and thus ensuring the quality of the application.
  • A bug is defined as errors in code that causes system to behave differently from expected.


Bug Score = (1 X Total No. of Low Severity) + (2 X Total No. of Medium Severity Bug) + (10 X Total No. of High Severity Bug)

Severity Score Severity Level Description
1 LOW System is able to function as per normal. Minor issues in expected output or user interface alignment
2 MEDIUM System is able to function but with runtime errors. Some non-critical functionalities may not work as expected
10 HIGH System has some compilation error and unable to run or unusable for a period of time. Core functionalities may be affected
Bug Score Action Plan
6 and below Developers resolve issues within the iteration
7 - 9 Schedule debugging in the buffer of the iteration.
10 and above Priority goes to resolving bug. Project Manager reallocates task for debugging team to focus on debugging.

There are few sources of change for the project itself. Depending on the initiator of the project change, change control processes would have to be taken into consideration.


Requirement Change

Requirement changes are modifications, additions, deletions of requirements stated in the latest version of requirements documentation. In this case, sponsor and supervisor would be noted. Response from supervisor and sponsor would be sought before decision is sealed.

System Design Change

System changes are modification, additions, deletions to the system architecture and detail system design as stated in the latest versions of system architectural documentations and technical infrastructure documentations. Depending on severity, response from supervisor might be sought before decision is sealed.

Business Process Change

Business Process changes are modifications, additions, deletions to the existing business processes as stated in the latest versions of process analysis documentation.


Following the feedback given by our supervisor, we have come up with the revised change process:

  1. Change initiated by external party
  2. Project Manager informed of change
  3. Project Manager makes decision of change and decides if team meeting is needed
  4. Project Manager informs team supervisor and sponsor(only if necessary)
  5. If team meeting is needed, meeting is scheduled, else team would be informed of change once decision made
  6. Change would be analyzed and decision reached by team to make it known.
  7. Change decision is being made known to supervisor
  8. Change implemented and decision is made known to team, supervisor and sponsor(if necessary)


Changes that are formalized and agreed upon by team, and stakeholders if necessary, would be recorded in the respective documentation by Project Manager/Deputy Project Manager. Followup actions of changes made to project and team would be tracked by the Deputy Project Manager.

Check out our Change Log:

Our team's risk management approach is in constant monitoring and reviewing risk at the start and end of each milestone. Check our our Risk Management Plans for more information:

Risk matrix.gif
Priority Type Risk Consequence Likelihood Impact Level Risk Assessment Level Mitigation Strategy


Unfamiliarity with mobile development frameworks required for the project

  • Inability to make decision about best framework to use
  • Slow project progress because of unfamiliarity




  • Conduct research on possible mobile development technologies and consult peers and supervisors for advice on which framework to use, in view of mobile app's scope
  • Development of mobile application in parallel with web application to highlight any possible loopholes and to buffer for any major changes needed early.


Group members making assumptions of technical scope required within the project

Inaccurate estimates of time required to complete tasks that leads to unreliable project deadlines and milestones




  • Review Project Scope at the start of every iteration by the team
  • Paper Prototype is being done to ensure common understanding
  • Encourage Members to Check their understanding of the scope.


Difference in understanding of terminologies and terms used in describing the business process (e.g. task, questions, assignments)

Confusion over terms that may lead to the wrong picture being conveyed between client and team




  • Implement a project dictionary where common terms of use are being recorded down
  • Proactive logging down of common terms of use in the project dictionary


Team Box.us would be responsible for the deployment of the system onto the client's servers and to ensure that the application is able to function smoothly and integrate into their current workflow processes.