HeaderSIS.jpg

Team Galaxy's Project Management

From IS480
Jump to navigation Jump to search


Project Management



What is Pivotal Tracker?


Tracker is a simple, story-based project planning tool that allows teams to collaborate and react instantly to real-world changes. It's based on agile software development methods, but it can be used on a variety of types of projects. Tracker frees you up to focus on getting things done, without getting bogged down keeping your plans in sync with reality.


How does it work?


Instead of managing hours spent on development, Pivotal Tracker allows you to easily track the progression of your project through the amount of features that you delivered to your end user. The Project Management concept behind Pivotal Tracker is that it view function as discrete and not continuous, a functions is either complete or not complete at all.


Thus, Pivotal Tracker allows one to create stories, for example, Features Osmosis star.png (functions of your application) and assigning points on a scale of 1 (Easiest), 2, 3, 5 & 8 (Toughest) to them. Osmosis bar.png Users will then be able to assign the stories to any of the team members or choose to take up so that they can work straight on the development.


Whenever a Feature Osmosis star.png story is completed, its points will be added cumulatively at the end of iterations to show progress of the project. Velocity which is a simple average of points completed over total iterations can then be derived to show the average progression of a team and then allow one to predict the progress of subsequent iterations.


You will also be able to schedule ‘Release’ Osmosis flag.png (milestone markers) and allow your team to track progress towards concrete goals, for example stakeholder or investor demos, software launches, etc. It's possible to specify target dates for releases. Thus with Pivotal Tracker, project management is made easier and more agile.

To learn more about how Pivotal Tracker works Visit https://www.pivotaltracker.com/help/gettingstarted



Schedule Metrics


Story Index= Actual Complete Story Points / Planned Story Points

Status Story Index Action
Ahead of Schedule >1.1 Bring forward tasks
On Schedule 0.8-1.1 Proceed as planned
Behind Schedule <0.8 Allocate more time resources

Reschedule or break up tasks

Velocity = Total Story Points / Iterations (n)


Where n = no. of iterations


The velocity points helps estimate the performance of the Team and thus the Project Manager is able to used the velocity points to plan for the next iterations

Osmosis graph.png


Metrics


Iterations Planned Story Points Complete Story Points Incompleted Story Points Index Cumulative Story Points Velocity
1 14 14 0 1 14 14
2 27 8 19 0.30 22 11
3 36 26 9 0.72 48 16
4 29 20 10 0.68 68 17
5 30 30 0 1 98 20
6 20 20 0 1 118 18


Schedule


Burnt Down Chart

Burntdown.png

Pre-Term Plan
Period Schedule Task

19 Dec - 6 Jan

1. Acceptance review with supervisor
2. Refine of Project scope with supervisor
3. Paper Prototype for application interface design
4. Paper Prototype for application form design
5. Exploring on Technology
  • AngularJS
  • Python (Django)
  • Tweeter Bootstrap
  • Pivotal Tracker
  • GitHub
  • Appfog
6. Setup GitHub environment
7. Transferring of schedule to pivotal tracker
8. Creating of database



Actual Term Plan
Osmosis ActualSchedule1.png
Osmosis ActualSchedule2.png
Osmosis ActualSchedule3.png
Osmosis ActualSchedule4.png
Osmosis ActualSchedule5.png
Osmosis ActualSchedule6.png
Osmosis ActualSchedule7.png




Risk Mitigation


Osmosis Risk Metrics.png

Project Risks

Osmosis Project Risks.png


Technical Risks

Osmosis Technical Risks.png


External Risks

Osmosis External Risks.png




Bug Metrics

Goal: To ensure all funtions are workable

Use:

  • To understand how well the functions of the application works so as to ensure continuity of the application.
  • Keep track on the severity of the bug(s) on the application.

Calculation: Classification of each bugs into severity * level of severity


Severity of bug Bugs Type
Severity Priority
Low (1 point) Low Impact – System can still run. Probably some UI issues.
Medium (10 points) Middle Impact – System can still run with some functionalities not working
High (50 points) Critical Impact – Entire system is affected by bugs or security issue arises. We have to fix the bugs to continue testing or further coding.
Iteration Function
Functionality A function should work 'properly' as intended. Example: Mousing over carousel should stop it from moving as intended
Design UI issues. Unable to display properly - text , table , pictures all over the place, some things are not shown on the page.
Linkage Unable to link from one place to another, keep linking to the wrong page.
Access Control User should not be able to modify data without permission. Example: Only team leader can edit Team members but not the team leader.
Runtime Error Nullpointer Exception or any runtime error that arises when the application is being used


Action Plan
Points in Iteration Action
<20 Fix during buffer time only.
Between 20 and 69 Use the planned debugging time.
70 and above Stop development and resolve the bug immediately. Project Management reschedules the project.




Minutes

Link to Pre-Acceptance minutes - Team Galaxy's Minutes


Date Meeting with Minutes Document
20 Dec 2012 Supervisor 20121220-Supervisor Meeting Minutes
11 Jan 2013 Sponsor 20130111-Sponsor Meeting Minutes
18 Jan 2013 Supervisor 20130118-Supervisor Meeting Minutes
18 Jan 2013 Sponsor 20130118-Sponsor Meeting Minutes
23 Jan 2013 FYP Client 20130123-FYP Client Meeting Minutes
20 Feb 2013 Supervisor 20130220-Supervisor Meeting Minutes
04 Mar 2013 Instructor 20130304-Instructor Meeting Minutes
06 Mar 2013 Supervisor 20130306-Supervisor Meeting Minutes