
Key Artifacts: Team Level
Managing team-level work and deliverables
User Stories
- Smaller functional requirements implementable within 1-2 weeks
- Describes functionality from user perspective
- Follows the format: "As a [role], I want [feature] so that [benefit]"
- In hospitals: "As a nurse, I want to scan medication barcodes so that I can verify correct medication administration"
Team Backlog
- Prioritized list of all User Stories for the team
- Maintained by the Product Owner
- Contains both business and enabler stories
- Represents all work the team might do
Iteration Backlog
- Subset of Team Backlog selected for current sprint
- Stories are sized and committed to by the team
- Created during Iteration Planning
- Visible to all stakeholders
Iteration Goals
- Summarizes the business objectives for the current iteration
- Provides focus and alignment for the team
- Used to communicate intent to stakeholders
- In hospitals: "Complete patient scheduling interface integration with 3 main systems"
Definition of Done (DoD)
- Clear criteria for when a story is complete
- Includes quality, testing, and compliance requirements
- In healthcare: Often includes regulatory compliance elements
- Example healthcare DoD items:
- Code reviewed by at least one peer
- Unit and integration tests passed
- Documentation updated
- Patient data privacy requirements met
- Required regulatory documentation complete