RE: Discuss the "to be checked" requirements with PO

Problem

There are some requirements that are not clear if they need to be included in our scope. To solve this we need to discuss and check these marked requirements with PO

Goal

Have a decision on all "to be checked" requirements

ACs

• PO goes through all the "to be checked requirements" of OZG, Zapuk, UR, DSGVO if they are relevant for us (and mark them)
• team::requirements defines the reason of "to be checked" of LB in the comments
• PO and team::requirements meet to discuss open "to be checked" in OZG, Zapuk and UR and all the "to be checked" requirements in LB

Notes/ resources

https://nextcloud.fitko.de/apps/files/files/2180937?dir=/Messenger-Kommunikation/Requirements%20Engineering

Who needs to be involved / informed

• reviewers:
• involved:
• informed: