Summary:
[This is NOT the same thing as the Product Requirements.]
The completion of this story may (or should) include the following:
Documented inventory of the existing products "under the hood" with a plan for their ongoing maintenance and/or sunset.
Versioning implemented for each component resource and bespoke development, automated, and fully documented.
Automated testing where possible.
Up-to-date, evergreen documentation of resulting systems installed, i.e. network diagrams.
Up-to-date, evergreen documentation of the system and process followed for each in arriving to the final installation.
Data flow diagrams of the internal flows.
Evidence and diagrams of identified use cases/environments and their testing prior to completion.
Gated, compliant SDLC evidence and artifacts.
Fully self-documenting code where changes were made.
Benchmarks of installation times.
Identification and specification for pre-existing situations (i.e. service principal or role needed to begin installation).
Creation of stories/features for any opportunities taken in the process of completing this epic but not specifically tied to this effort.
Creation of stories/features to plan for addressing any technical debt in the process of exploration and implementation of scans and best practices.
Documented and published Azure Secure Score.
Plan for gathering client system architectures for additional use cases as allowed on an ongoing basis.
Sign-off and review by delivery team and product stakeholders.
Reasoning: This may be an item that is necessary but does not have a product aspect to it but is work that must be done. It would ultimately be tied to a larger feature or epic, but in the case where this backlog item is at the user story level, while it may or may not have Product Requirements, it MUST have Acceptance Criteria.
Regulatory guidance: TODO
留言