They should be planned in parallel Sprints so not to disrupt the Development Team during feature development. After security concerns have been finalized, they will be applied to the work that is already completed before new feature development can continue.
They should be handled in a parallel Sprint by a separate security team so that security can be resolved through application enhancements without impacting the functional development.
A complete list of security-related Product Backlog items needs to be created before starting a new Sprint.
During the Sprint Retrospective, the Development Team assesses how to add these expectations to their Definition of Done so every future Increment will meet these security requirements. If needed they can work with external specialists to better understand the requirements.
They are added to the Product Backlog and addressed throughout the next Sprints, combined with creating the business functionality in those Sprints, no matter how small the business functionality.
© Copyrights DumpsEngine 2025. All Rights Reserved
We use cookies to ensure your best experience. So we hope you are happy to receive all cookies on the DumpsEngine. Accept