Picturative Modified Scrum Process

From IS480
Jump to navigation Jump to search

Back to Main: IS480_Team_wiki:_2010T1_Picturative

Due to the constantly changing requirements of our project, it is critical to provide adequate project progress visibility. Examining a few frameworks for project management, we came to the conclusion that SCRUM is most suitable for our needs. However, we needed to modify the process so as to suit our schedules (changing the scrum meeting structure to that of individual progress logs, and changing scrum times to 48 hour updates). This framework gives high visibility to our project's progress and allows us to easily track our schedule.

Our Scrum Process

The following details our Scrum Process. Bryan is in charge of monitoring this and allocating hours for each sprint. Currently, we are structuring each sprint as being a single iteration in the project. This is due to what we have for the HCI framework for user interface development.

Modifications Made to Original SCRUM

  • Modification was made in the form of putting our individual updates on dropbox and using Skype to have SCRUM meetings.
  • Hours were extended from 24 hour updates to 48 hours due to our workload outside of the project


Iteration Flow

The following is a breakdown of each iteration (Sprint) in our project development process. It involves extensive testing and aims to create a system where bugs are tracked and logged early, while providing very focused user interface and program development.



Review Proces

At the end of each Iteration (Sprint), a review is conducted by Bryan with the team in order to understand whehter future sprints require more or less time allocated. This provides involves reviewing the BurnChart and Individual Sprint files.
For example, if Skye has taken less time than anticipated in the area of modelling, future iterations could see a decrease in the work hours allocated for modelling. This applies to the converse situation as well.