Scrum
Practices Employed
- Approvals: Scrum requires approval during sprint reviews and at the end of each sprint. See:
- Sprint Review
- Automated Testing: Unit testing is part of the Definition of Done in Scrum. See:
- Unit Testing
- Automation: Automation of tests and integration (CI/CD) is common in Scrum practices.
- Change Management: Changes are managed through the product backlog and sprint planning.
- Code Reviews: Code reviews can be part of the development practices within Scrum.
- Coding: Coding is a core activity in Scrum as it is in any software development framework.
- Configuration Management: Configuration management helps maintain the consistency of the product's performance.
- Debugging: Debugging is an essential part of the development process in Scrum.
- Demo: Scrum includes sprint reviews which act as demos for stakeholders.
- Documentation: Documentation is produced, but Scrum values working software over comprehensive documentation.
- Estimating: Estimation is performed during sprint planning using techniques like story points. See:
- Planning Poker
- Sprint Planning
- Integration Testing: Integration testing is part of the Definition of Done in Scrum.
- Issue Management: Issues are logged and tracked through tools like JIRA to ensure they are resolved promptly. See:
- Sprint Backlog
- Measurement: Scrum uses various metrics like burndown charts to measure progress. See:
- Burndown Chart
- Definition of Done
- Meeting: Scrum uses various face-to-face meetings. See:
- Daily Stand-ups
- Retrospectives
- Monitoring: Monitoring progress through daily stand-ups and sprint reviews is integral to Scrum. See:
- Daily Stand-ups
- Prioritising: Scrum prioritizes work during sprint planning and focuses on delivering a potentially shippable product increment. See:
- Sprint Planning
- Sprint Goal
- Product Backlog Refinement
- Refactoring: Refactoring is encouraged to maintain code quality within Scrum.
- Regression Testing: Regression testing is part of the Definition of Done to ensure changes don't break existing functionality.
- Release Delivery: Scrum focuses on frequent releases, with potentially shippable increments delivered at the end of each sprint.
- Requirements Capture: Capturing requirements is done through user stories and the product backlog in Scrum. See:
- User Stories
- Retrospectives: Retrospectives are a key part of Scrum for continuous improvement. See:
- Sprint Retrospective
- Review: Scrum includes regular reviews in the form of sprint reviews and retrospectives.
- Stakeholder Management: Stakeholder engagement is critical in Scrum, especially through the role of the Product Owner.
- Version Control: Version control is a best practice in software development, including in Scrum.
Description
"Scrum prescribes for teams to break work into goals to be completed within time-boxed iterations, called sprints. Each sprint is no longer than one month and commonly lasts two weeks. The scrum team assesses progress in time-boxed, stand-up meetings of up to 15 minutes, called daily scrums. At the end of the sprint, the team holds two further meetings: one sprint review to demonstrate the work for stakeholders and solicit feedback, and one internal sprint retrospective. A person in charge of a scrum team is typically called a scrum master." - Scrum (software development), Wikipedia
Scrum is an Agile framework that focuses on iterative progress through small, cross-functional teams. Key practices in Scrum include sprint planning, daily stand-ups, sprint reviews, and retrospectives. Scrum emphasizes collaboration, flexibility, and continuous improvement, making it a popular choice for managing complex projects.
See Also
Fixing Scrum
Part of the 'Estimating' Risk-First Track, looking at the essential flaws in Scrums' time-boxing of work.
On Story Points
Part of the 'Estimating' Risk-First Track, about improving estimates using risk checklists.