Skip to main content
Project Management

Return to Question

Tweeted twitter.com/StackProjects/status/1409980014884499462
Became Hot Network Question
added 4 characters in body
Source Link
Daniel
Daniel
  • 2.7k
  • 14
  • 36

If a requirement is discovered in the middle of a project or even later, then the cost of implementation of this requirement iscan be very high.

The Scrum suggets that we should only refine the top PBIs of the Product Backlog. The other PBIs are not refined, and thus the requirements related to these PBIs will be discovered lately in the project execution.

What is the Scrum's approach to this?

If a requirement is discovered in the middle of a project or even later, then the cost of implementation of this requirement is very high.

The Scrum suggets that we should only refine the top PBIs of the Product Backlog. The other PBIs are not refined, and thus the requirements related to these PBIs will be discovered lately in the project execution.

What is the Scrum's approach to this?

If a requirement is discovered in the middle of a project or even later, then the cost of implementation of this requirement can be very high.

The Scrum suggets that we should only refine the top PBIs of the Product Backlog. The other PBIs are not refined, and thus the requirements related to these PBIs will be discovered lately in the project execution.

What is the Scrum's approach to this?

Source Link
Daniel
Daniel
  • 2.7k
  • 14
  • 36

Lately discovered requirements in Scrum

If a requirement is discovered in the middle of a project or even later, then the cost of implementation of this requirement is very high.

The Scrum suggets that we should only refine the top PBIs of the Product Backlog. The other PBIs are not refined, and thus the requirements related to these PBIs will be discovered lately in the project execution.

What is the Scrum's approach to this?