LO8 – Backlog and Sprints

This is a new blog post explaining the new reasoning and methods behind backlog and sprints. We are using the Scrum methodology, but apparently it wasn’t correct, so we had to update the schedule and the backlog to the correct methods of using the agile method.

This was acceptable, and we tweaked our methods to the correct form of agile method ever since our lecturer talked to us in class.

Scrum was the most acceptable method for this project, as it was quite a big one. Our lecturer told us that scrum is quite an effective method that a lot of graphic designers use to do certain jobs.

We use our product backlog to keep track of what we have completed (job list) and what we have not completed. ‘WEF 01,04,06’ etc. are ordered from WEF keycodes and are colour coded to the priority of the task allocated Red=High priority. WEF keycodes are found within the Job List in order.

All our backlog is, is it is a list of things that need to be done inside the project. It is an extreme ToDo list that specifies each by the priority. Our most important objectives will be put up the top of the list. All other artefacts made are used to complement the sprint backlog itself, and are used to help understanding of it for other students. Using this and the sprint backlog and its prioritized content will help our group members get on workflow and complete projects on sprints and on time for the client.

The allocation or priority can be found in the product backlog document along with the burndown chart. The tasks are then separated into seperate sprints in the sprint backlog, a separate document.

The scrum co-ordinator students like to keep the  backlog and all  documents healthy and updated.

aaaaaa

 

sprint baCKLOG.jpg

The sprint backlog tracks who was behind the task from the product backlog. it shows how long the person worked behind that project, and if there are notes attached to display how the project went. It is a great tracking sheet for our members, who can look and find certain sprints and tasks for themselves.

During our weekly and daily stand up meetings we would discuss what we have done, and what we haven’t done, so that we can update and adjust the backlog and sprint backlog to keep it clean and prioritize other tasks to other members.

 

Sprints S1 S2 S3 S4 S5 S6
Jobs Left 30 27 15 10 5

The burndown chart is located next to the ‘job list – Product backlog’ where everything was completed each sprint. As you can see from the example, it can be made into an excel chart document file and placed automatically.

Our burndown chart measures the completion and time of how things were completed. From the image below, you can see we did a good job and were on time a lot of the time. We got to even do our desirables!

 

 

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s