The Team keeps it up-to-date all the time. It is valid for one Sprint – it is created at the start of the Sprint, never earlier, and ceases to exist at the end of the Sprint. The Sprint Backlog is a plan from the Team on how they are going to attempt to achieve the goal of the Sprint. The Product Owner uses the Product Backlog for tracking product progress, deciding features to create next, and for making scope/time/cost trade-offs. The Product Backlog contains items that represent product features or improvement work. It leads to confusion about their purpose. This might seem like a good idea but in practice, it is not. Jira integrates the Product and Sprint backlog. Micro-management due to integration of Product and Sprint Backlog Scrum implies team-owned processes rather than tool-owned processes.
-1.png "setting up speedy for jira")
Team practices are not prescribed or fixed but are adopted and adapted as context changes. How? Scrum has a minimum of prescriptions as it implements empirical process control. Teams end up adopting ideas that they think, or were told, are included in Scrum. It is an issue tracking tool with many ideas integrated into it, such as Scrum and many… not-Scrum.
People learn Scrum through Jira, or so they think.
Many companies start “enterprise-wide” Scrum adoption with mandating Jira.
0 kommentar(er)
