New answers tagged

0

First, I would argue there is no such thing as a POC in an agile organization. You merely create an iteration of the product with the vendor's solution. Then if you don't like the results, the next iteration pulls that solution out. Liaising is easy. The PO and team together only create the user stories for their part of the process--creating specs to give ...


1

The team as a whole is responsible for requirements and specifications. Backlog Refinement - preparing backlog items so that they are ready to take into future sprints - is a continuous process. Some teams formally allocate a certain amount of time each sprint to backlog refinement or alternatively just do it as a background task. The point of backlog ...


4

There's a lot of grey area, but the direct answer to you question according to the Scrum Guide is no - it is not the Product Owner's responsibility to provide data mappings. https://scrumguides.org/scrum-guide.html#product-owner So... in your situation, the PO has a backlog item that says something like "As a sales exec, I want to see a graph of sales ...


1

If a company needs to deal with these kinds of technical stories a lot, they hire/have technical product owners. If such stories come up from time to time, then the product owners groom the stories with the support of the software developers in the team. So, my answer is; this is entirely in the scope of the product owner role.


2

Trust is agility's foundation. Lack of trust is painted all over the way the question is framed. The Product Owner is indeed responsible for driving the creation of the user stories. The PO, however, is not the sole responsible for that. Specially on Stories that have a considerable amount of technical background, development team should play a critical, ...


0

A Proof of Concept (POC) cannot be estimated in terms of story points, hours, nor any sizing you use, since it is all about trying to prove if a suggested model works or not. That's why, it cannot be included in a Sprint. As far as I understand, the need to include it in the Sprints arises due to: some of the Developers in the Scrum Team will be working on ...


0

In a POC the Product Owner ought to be the decision maker, the person who will assess the suitability of the product being evaluated and make or recommend the purchase - or someone nominated by the decision maker(s). It's most important that they keep the team's focus on demonstrating the required evidence or learning the lessons that the POC is intended for....


0

The Product Owner role as defined by the Scrum Guide says nothing about working with a vendor. are there any other responsibilities that that PO should own in this situation? That depends on a number of factors, including: The skill set of the Product Owner How much time they have available Whether they are interested and want to get involved in non-...


Top 50 recent answers are included