Product Backlog Template: Deep dive on reasoning and regulations (5..11)

<< Previous section - Estimate/effort

THINGS TO KNOW

Testing notes:

See below.

Reasoning: This calls out any outliers or things that a potential developer or testing resource should remember that is not immediately evident from the rest of information in this effort. Rather than the information being siloed, it can be captured and discussed here, and a place to capture it. It also allows for potential risks in accounting for and being transparent through the risk assessments and testing evidence/considerations for requirements gathering and compliance. It helps with new team members to be able to contribute as well.

Regulatory guidance: TODO

Risks/dependencies:

To not address these issues as a set will result in limited effectuality and time wasted. To not address them at all will continue to incur the costs mentioned below, as well as further security risks, and our compliance efforts and thus contracts. There is a risk of potentially missing a detail in our implementation, but that risk is already present and ongoing due to the current state. The current ongoing implementations cannot be affected and must continue to function in whatever fashion they currently are.

Reasoning: Potential risks should be captured and documented, not only for full discussion and testing, but for requirements gathering and change management. External dependencies should be tracked in order to identify coordinating points for other teams in order to get work ready to be started. Being able to report on this information as captured in the backlog addresses the artifacts required as evidence of risk assessment.

Regulatory guidance: TODO

Next section - Other >>