-
-
Notifications
You must be signed in to change notification settings - Fork 1
Definition of Ready
Tobias edited this page Jan 9, 2023
·
2 revisions
- The user story contains technically realizable tasks (checkboxes)
- The user story can be implemented independently of other user stories
- The user story is comprehensible and fully described for all participants
- The effort for the user story was estimated by the team
- The user story can be implemented within one iteration.
- At least 1 acceptance criterion is formulated
- Acceptance criteria are formulated in a way that is understandable and sufficient for all stakeholders and are testable (
SMART
) - Any non-functional requirements are linked to the user story
If an issue meets the Definition of Ready, it must be assigned the appropriate Status: Accepted
label.
README | Contributing | Code of Conduct | Support | Funding | Security | License |
- Home of the Wiki
- Roadmap
- API Reference
- Glossary
- Contributor Guide
- Code of Conduct
- Support
- Funding
- Security
- License
- Description of Core Essence
- Cost Estimates
- Staffing Estimates
- Predicted Benefits
- Risks
- Scheduled Milestones
- Definition of Ready
- Definition of Done
- Project Decisions
- Technological Decisions
- Sprint Reviews
- Sprint Retrospectives
- Continuous Integration
- Continuous Deployment
- Operations Troubleshooting
- External Systems
- Style Guide
- Specific Views
- View 1
- ...
- About
- Introduction and Goals
- Constraints
- Context
- Solution Strategy
- Building Block View
- Runtime View
- Deployment View
- Cross Cutting Concepts
- Design Decisions
- ADRXX Template
- ...
- Quality Requirements
- Risks and Technical Debt
- Glossary
- Reference Manuals
- Support Guides
- Release Notes