One of the biggest risks in Agile projects is the expectation of finishing too many user stories by the product owners by ignoring the quality of the software delivery. Product owner if not enough technical can sign off a story by just looking at the scenario Some one in the team can take up a volunteer job to identify the risks coming up due to technical debt.
Following are a few possible risks
1. Lack of Unit tests due to high expectations from the devs for developing too many user stories. This scenario makes devs to focus only on the development instead of writing Unit tests. 2. Lack of Automated tests. This also happens when teams pull in too many user stories in a sprint. It sometimes becomes impossible for the testers to automate cases related to all user stories in a sprint. 3. Availability of Business users / Subject Matter Experts / Product owners to do User Acceptance Testing
In one of the projects I worked we had a dedicated product owner in each team. It was quite easy to get the user stories closed.
However in the another project we had only 1 product owner assigned to 3 different teams. It was so hard to get even a few minutes to find her time to show user stories. Each team would take up 8-10 stories and imagine giving demo of 30 user stories to one person and then fixing stuff based on the feedback can cause a lot of damage. It can end being a very risky sign off process
Like always resourcing is always the one of the biggest risks of any project.
Other risks could be unknown integration points associated with a user story. At enterprise a simple feature can have really complex integration points. E.g In an insurance product implementation we had to just search an insurance policy from the system. Feature wise it looks easy, however in this implementation we had to pull the policy data from the legacy system. So the team had to implement a complex Integration with the legacy system and it also highlighted a lot of risks associated with the whole delivery.