Product Backlog Management and Training New Employees
Today’s post continues on with additional findings from the most recent Global Study of Product Team Performance. Consider how you would answer these two important questions. Are your answers similar to those given by other teams represented in the survey?
Question: My team’s product backlog … (Check all that apply.)
|Is a jumble||37.9%|
|Is effectively prioritized||43.5%|
|Is well thought out||34.7%|
|Has the right level of detail||33.9%|
Understanding Product Backlog Responses
More than 40% (43.5%)of respondents indicated that their team’s product backlog is effectively prioritized. Yet, nearly another 40% (37.9%) consider their product backlog to be in disarray. Product backlog in disarray can certainly cause a team to be less productive than it could be. More than a third of respondents characterized the handling of product backlog as well thought out (34.7%). Nearly as many, 33.9% indicated that the product backlog has the right level of detail.
Question: Which product development requirement format makes it easier to on-board new product team members?) (Check one.)
|Traditional requirements (Product requirements document or market requirements document)||19.4%|
|An ordered backlog of epics and user stories||31.6%|
|A hybrid model blending both||35.2%|
|None of the above||13.8%|
A Closer Look
One-third (35.2%) of respondents hold the same view: A hybrid approach blending user stories and a market requirements or product document is most useful in on-boarding new team members. Considered nearly as effective is the ordered backlog of epics and user stories alone. This answer garnered 31.6% of responses. Most respondents consider traditional requirements used alone are less effective. Only 19.4% favored this answer. A much smaller contingent, just 13,8% considers none of the options as a way to streamline the on boarding of new team members.
We’re drawing near the end of our review of findings in the most recent Global Study of Product Team Performance. Next week we’ll look at time-frames for sharing product roadmaps with customers. We’ll also consider how different organizations handle reporting of the user experience group.