Risks and uncertainties
It could be more strategic for Agile teams to get the riskiest items out of the way, first. If it turns out to fail earlier on in the project, they can still maneuver within the project timeline to assess and improve. Conducting risk analysis would be largely beneficial for the project. Testers can help the Product Owner by determining what the product risks are for a certain feature, if it does not meet the expected quality.
Dependencies
There will always be dependencies within any project. And when it comes to Product Backlog management, it restricts the prioritisation of PBIs, since it will be matter precedence. For example, development of Feature B could not push through until Feature A is completed, while Feature C is dependent on making a certain tool work.
Dependencies could delay the development of features, even those deemed to be highly valuable. This can be mitigated partly by breaking down features and user stories into more manageable work items. Going back to an earlier example, breaking down Feature C into smaller user stories that will tackle parts of the new tool is more manageable than attacking Feature C altogether.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: