Skip to content

suggestion: chapter on good agile practices (e.g. example definition of done) #5

Open
@tobiasbueschel

Description

📚 Handbook

Example:

Product
- PO accepts user story
- Acceptance criteria met
- Non-functional requirements met (compliance, data, security, etc.)
- User story has been promoted to a higher environment (e.g. Non-PROD)
 
Testing
- Test coverage not dropped, appropriate tests were added (I think it’s better not to dictate a coverage as it’s not always a meaningful measure of robustness)
- Unit tests, integration and e2e tests (where applicable) have been added / done
- QAs have signed off
 
Code
- Code reviewed and approved by x people
- Well documented
- Code has been merged to develop branch (if using e.g. Git Flow)
- Code changes follow best practices as agreed by the team
- Other dependencies, e.g. database or infrastructure changes have been made in the respective environment

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions