SCRUM Overview Flashcards
What are the SCRUM principles ?
- Empirical process control: observation and experimentation rather than detailed up-front planing
- Self-organization: workers will deliver greater value when self-organized, resulting in better team buy-in and shared ownership
- Collaboration: project management as a shared value-creation process
- TIme-boxing: time is a limit constraint and must be used to manage project planning and execution
- Iterative development: iteration will deliver products that better satisfy customer needs.
Define the SCRUM core roles
- Product owner: adds business value for the project and articulate customer requirements.
- Scrum master: Ensures the teams is provided with an conductive enviroment. Guides, facilitates and teaches scrum practices.
- Development team: understanding the requirement set by the the product owner. Also work on the user stories in the sprint backlog to create deliverables.
Define the SCRUM stakeholders
- Customer: individual or organization that acquires the project’s product
- Users: individuals or organizations that directly uses the project’s product or service
- Sponsor: individual or organization that provides resources and support for the project, and the stakeholder to whom everyone is accountable in the end.
Describe what DevOps is.
Traditional development involved development teams who made the systems and operations teams who operated and maintained the systems.
The role arose to address the need for consistent application of agile processes at all stages of the SDLC
Emphasis is on continuous delivery
Scrum processes
- Initiate
- Plan and estimate
- Implement
- Review and retrospect
- release
Describe the characteristics of Sprints
Work is performed in iterations called sprints.
- Sprints are timeboxed (time specific)
- No changes of scope
- Work completed in a sprint should create something of value to user
- typically multiple consecutive sprints in a project
Describe what Sprint Planning is.
input: product backlog
Output: sprint backlog
- The team decides what to work on next and how they will do it
- Agree sprint goal
- Identify most important task in the product backlog to create a sprint backlog
- fill timeboxed sprint to capacity with the right number of sized tasks
Describe what sprint review is (show and tell)
Input: sprint goal
Output: groomed product backlog
- regular meetings where the team demonstrates their work
- All stake holders can be invited
- Involves live demonstrations of potentially shippable product
- open and transparent for comments
Describe what sprint retrospective is.
Input: POV
Output: Process improvements
- Regular meetings with the whole scrum team
- held at the end of the iteraion
- 60 to 90 minutes, and talk about bad/good
- hosted by scrum master
- gives opportunities to inspect and adapt the process
Describe what backlog grooming is.
Input: POV
Output: groomed backlog
- occurs at the start of the release planning during the sprint
- proactively managing, organizing the product backlog
- collaborative effort led by the product owner
How are gathered the user requirements?
They are gathered through conversation with users, which happen continuously through development: ‘just in time’
What are product backlog items?
They are placeholders for vague or unknown requirements. Those are redefined into smaller and more detailed items that can be included in a sprint.
What is a sprint backlog?
It’s a list of task identified by the scrum team to be completed during the scrum sprint
What are user stories?
User stories are short, simple descriptions of a business need told from the perspective of the user.
As a < type of user >, I want < some goal > so that < some reason >
Describe characteristics of the product backlog
- Prioritized list of desired product functionality
- Centralized and shared understanding of what is to be built, and in what order
- Central artefact at the hard of scrum framework
- Comprises PBI of different sizes
