HeaderSIS.jpg

IS480 Team wiki: 2012T1 Timber Werkz ProjectFramework

From IS480
Jump to navigation Jump to search
HOME   PROJECT OVERVIEW     PROJECT MANAGEMENT   DOCUMENTATION  
         


<< MID-TERM WIKI          << FINAL WIKI

Project Framework



Agile SCRUM1 is used as a project management framework to deliver the application for the client.
The process is explained by the following flow chart and SCRUM terminology list.


The SCRUM process and jargons explained:

SCRUM process flow of events


1. Roles in the process: Of Product Owner, Scrum Master and Team
The Product Owner (Oak3 Films) is responsible for the business interest and value of the project.
The Scrum Master (the Project Manager of the team) takes charge of managing the product backlog and the team’s productivity.
The team (TimberWerkz) is a self-managed entity that ensures that the work gets completed.


2. Product Backlog
The process is first triggered with a wish list of prioritised requirements drawn up by the product owner. In the case of our project,Timberwerkz aids the product owner in creating this list, regularly discussing with them on whether it is aligned with their needs or business objectives.


3. Sprint Backlog
Next, Timberwerkz pulls out a list of to-do items from the product backlog and places it in the sprint backlog. Each story of a sprint has an in charge, and he shall see through the development and testing of the story. He needs to update the status of the story in the product backlog.


4. Sprint
A sprint is a duration that the team takes to complete the tasks selected in the sprint backlog. TimberWerkz sprint duration is 3 weeks. Once the Sprint Backlog is up, the team scrambles to work on the sprint.
At the end of each sprint, the team meets to discuss their availability for the next sprint, the stories to be included in the next sprint (with reference from the priorities, estimated man-days required from the product backlog, and milestones list), and review the sprint that has just ended. Impediments of the sprint are identified and the members will aim to rid them from the next sprint. The review meeting also consist of some sharing from team members, be it stories that they have completed or new technologies/extensions/plugins that they have implemented. This ensures that all team members are on the same page and understand what each other have been working on.


5. Weekly meetings
Instead of having daily meetings as depicted in the original SCRUM process, TimberWerkz has a weekly SCRUM meeting instead to customise to its needs.


6. Potentially Shippable Product
After a sprint is complete, a workable function or deliverable can be released or demonstrated to the product owner. At the end of each sprint, Timberwerkz will approach her client and seek for approval for the stories that have been completed in that sprint. Upon approval, the workable story or deliverable can be released on the production environment and will be pending for usability test.

The SCRUM process then repeats itself until the product backlog is cleared.

Further your knowledge of SCRUM via Scrum Alliance, where TimberWerkz has referenced the contents of this section from, including the flow chart image used.