Skip to main content
Project Management

Return to Answer

added 19 characters in body
Source Link
Sarov
Sarov
  • 14.8k
  • 5
  • 34
  • 64

A POC can notProof of Concept (POC) cannot be estimated in terms of story points, hours, ornor any sizing you use, since it is all about trying to prove if a suggested model works or not. That's why, it can notcannot be included in a sprintSprint.

As far as I understand, the need to include it in the sprintsSprints arises since;due to:

  1. some of the resourcesDevelopers in the scrum teamScrum Team will be working on that POC
  2. the output of the POC will be epics, stories, and/or tasks for the scrum teamScrum Team

You should approach this POC just like how you approach to a bug from the production environment; have a kanbanKanban board for these kind of activities and add the POC there. In terms of the workload of the scrum teamScrum Team members, you can use the same model you use when a member uses a paid time off ( vacation vacation).

I would recommend the PO to do the communication between the external and internal teams because the POC is mainly done for the PO; the outputs of it will define what needs to be done. While the POs doPO does the communication, they can do the planning to act faster.

A POC can not be estimated in terms of story points, hours, or any sizing you use, since it is all about trying to prove if a suggested model works or not. That's why, it can not be included in a sprint.

As far as I understand, the need to include it in the sprints arises since;

  1. some of the resources in the scrum team will be working on that POC
  2. the output of the POC will be epics, stories, tasks for the scrum team

You should approach this POC just like how you approach to a bug from the production environment; have a kanban board for these kind of activities and add the POC there. In terms of the workload of the scrum team members, you can use the same model you use when a member uses a paid time off ( vacation ).

I would recommend the PO to do the communication between the external and internal teams because the POC is mainly done for the PO; the outputs of it will define what needs to be done. While the POs do the communication, they can do the planning to act faster.

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:

  1. some of the Developers in the Scrum Team will be working on that POC
  2. the output of the POC will be epics, stories, and/or tasks for the Scrum Team

You should approach this POC just like how you approach a bug from the production environment; have a Kanban board for these kind of activities and add the POC there. In terms of the workload of the Scrum Team members, you can use the same model you use when a member uses paid time off (vacation).

I would recommend the PO do the communication between the external and internal teams because the POC is mainly done for the PO; the outputs of it will define what needs to be done. While the PO does the communication, they can do the planning to act faster.

Source Link
Nezih TINAS
Nezih TINAS
  • 580
  • 3
  • 10

A POC can not be estimated in terms of story points, hours, or any sizing you use, since it is all about trying to prove if a suggested model works or not. That's why, it can not be included in a sprint.

As far as I understand, the need to include it in the sprints arises since;

  1. some of the resources in the scrum team will be working on that POC
  2. the output of the POC will be epics, stories, tasks for the scrum team

You should approach this POC just like how you approach to a bug from the production environment; have a kanban board for these kind of activities and add the POC there. In terms of the workload of the scrum team members, you can use the same model you use when a member uses a paid time off ( vacation ).

I would recommend the PO to do the communication between the external and internal teams because the POC is mainly done for the PO; the outputs of it will define what needs to be done. While the POs do the communication, they can do the planning to act faster.