Story Board Every location had its own story board which was maintained by the local team, these boards were always in sync with Story boards of other locations. A variety of boards were used in the project such as iteration story boards, planning board, iteration Retro board and Triage board. An Iteration Story Board is used to for each iteration/Sprint. It has all planned stories for particular iteration. Daily standup uses this story board. A Planning Board is basically to show high level planning of product backlog items. It shows what are stories planned in which iteration based on their priorities.
Triage Board is used as a store house of stories which are open for user’s discussion and not very critical for project. Post discussion with users, these can be either prioritized or discarded. Retro Board is for retrospection wherein team lists out as to what augured well, things which didn’t work as envisaged and was puzzling them. That is the area for Process improvement. Risk &Issue Board is used to manage and track Project Risks. Story boards acted as a main information radiator for project and anyone who was interested to know about project could walk to story wall which mundanely illustrated the progress of the project.
Product Backlog The product backlog is a prioritized, living master list of all the features and functionalities required to complete the project. Product backlogs commonly include requirements/ user stories e.g. requirements, bugs, research tasks (spikes) and engineering improvements. These items are estimated in abstract units that are often called story points. Product Backlog is maintained both on Jira Agile and physical Planning board. SCRUM board in Jira Agile views as to what is in store for the iteration (Product owner is responsible for Product Backlog management). Jira Agile is very useful tool to manage stories and its movement from one stage to other. It also offers dashboard to see project health. It can give project velocity, Burndown/up charts etc. In our project one product backlog was maintained for both the streams.
Product Backlog Grooming The team and stakeholders are involved in creating and managing the product backlog, but the product owner has ultimate responsibility for it. Product backlog grooming must happen regularly. Scrum team should spend 515% of its time in any iteration in grooming activities. This helps team to understand what’s coming up and what’s changing. Product backlog grooming exercise happened during iteration planning session. Feedback: pminicmag@pminorthindia.org
Synergy Dec 2014, Page 25