In Scrum, should you split up the backlog in a functional backlog and a technical backlog or not?
In our Scrum teams we use a backlog, which mostly contains functional topics, but also sometimes contains technical topics. The advantage of having 1 backlog is that it becomes easy to choose the topics for the next sprint, but I have some questions:
A backlog of “bite-size” tasks in parallel to the “main” feature backlog?
After over two years of working in a highly siloed, “lone-wolf” development department structure, we’re adopting Agile SCRUM. Great. I like Agile; as a dev it keeps you focused, busy, and productive without having myriad stakeholders shoving project after project down your throat with the expectation they all be done yesterday.
Can Scrum use technical specifications in the Product Backlog rather than user stories?
At the company I am currently working for we started to do Scrum projects. It was not so hard to convince the managers to move from waterfall to Scrum. We’re doing a project where we rebuild our platform from scratch. So (most) functionality is known and most improvements are rather technical.
In scrum, how do you give an estimate for a backlog item that is primarily research?
A few sprints ago I was assigned a task that was primarily research. I had to figure out how to get our product to interoperate with a very complex black box that we did not develop.
In scrum, how do you give an estimate for a backlog item that is primarily research?
A few sprints ago I was assigned a task that was primarily research. I had to figure out how to get our product to interoperate with a very complex black box that we did not develop.
In scrum, how do you give an estimate for a backlog item that is primarily research?
A few sprints ago I was assigned a task that was primarily research. I had to figure out how to get our product to interoperate with a very complex black box that we did not develop.
In scrum, how do you give an estimate for a backlog item that is primarily research?
A few sprints ago I was assigned a task that was primarily research. I had to figure out how to get our product to interoperate with a very complex black box that we did not develop.
In scrum, how do you give an estimate for a backlog item that is primarily research?
A few sprints ago I was assigned a task that was primarily research. I had to figure out how to get our product to interoperate with a very complex black box that we did not develop.
In scrum, how do you give an estimate for a backlog item that is primarily research?
A few sprints ago I was assigned a task that was primarily research. I had to figure out how to get our product to interoperate with a very complex black box that we did not develop.
Who should be allowed to add stories to the product backlog?
What is the best practice for that prevents the backlog from becoming a mess, but also maintaining developer productivity