Scrum Master Flashcards
(27 cards)
The Agile Manifesto infers people over processes. Isn’t a Scrum Master — whose role is meant to “enforce” the process — therefore a contradiction?
- The Scrum Master serves the team rather than enforcing rigid rules
- Helps the team adopt Agile principles in a way that suits them.
- Supports collaboration, removes impediments, and fosters continuous improvement.
What indicators might there be that demonstrate agile practices are working for your
organization, and which of these would demonstrate your efforts are succeeding
- Improved delivery speed
- Higher quality outputs
- Strong team morale and engagement
- Adaptability to change
- Customer satisfaction
Should a Scrum Master remove impediments on behalf of the Scrum Team?
- The Scrum Master assists in removing impediments but does not always handle them directly
- The focus is on enabling the team to resolve challenges themselves.
How should a Scrum Master communicate with a Product Owner?
- Frequent and Transparent Discussions
- Facilitating Backlog Refinement
- Bridging Business and Development
- Encouraging Agile Best Practices
- Resolving Conflicts & Stakeholder Alignment
Should the Scrum Team become involved in the product discovery process and, if so, ho
Yes, for two reasons
- Won’t pursue solutions that are technically not viable
- Develop a sense of ownership for a scrum team on what they need to build to create customer value
The role of the Product Owner is a bottleneck by design. How do you support the Product
Owner so that they can maximize the value of the work of the Scrum team?
- Facilitate effective backlog management
- Improve stakeholder communication
- Educate on Agile principles & value delivery
How can you ensure that a Scrum team has access to a product’s stakeholders?
- Define clear communication channels
- Involve stakeholders in sprint reviews
- Create a stakeholder engagement strategy
- Address stakeholder feedback transparently
How do you promote an agile mindset across departmental boundaries and throughout an
organization and, in pursuit of that, what is your strategy when coaching stakeholders not
familiar with agile product development?
- Educate Through Practical Examples
- Encourage Cross-Team Collaboration
- Make Agile Tangible
- Address Resistance with Data
- Foster an Agile Culture
Definition of done (DoD)
- Checklist of items that needs to be completed in order to declare a task as ‘Done’
- Eg. Written codes, unit testing, integration testing, design documents, release notes
MVP vs MMP
MVP (Minimum Viable Product)
- Product with minimal features released to market for customer to use and provide feedback
MMP (Minimum Marketable Product)
- Consists of all minimal features
- Functional software that is ready for monetization
Timebox
- Timeslot of an activity
- Eg 15 minutes for daily scrum
Drawback of estimating user story in hours or days
- Estimate varies between different team members
Tools used in Scrum projects
Jira, Confluence, Azure Devops, Trello, Asana
Is Scrum Master a management position?
- Yes, it a management position
- Manager of process and not people
What does the Scrum Master do to enhance the productivity of the development team?
- Eliminates the hurdles of the development team
- Shields the team from extrinsic troubles
How do you follow up on action items?
- Action items are one among the primary outcomes of the retrospectives-
- Open the list of action items and their owners
- Mark the progress of all items
- Include newly pinpointed items
Scrum artefacts
- Product backlog
- Sprint backlog
- Increment
- Burn-down chart
Product goal vs sprint goal
Product Vision:
- Long term strategic goal
- Eg. Be the leading online bakery in the UK
Product goal
- Intermediate goal that will advance us towards product vision
- Eg Launch a website
Sprint goal
- Intermediate tactical goals which moves us towards product goal
- Eg1. Create basic website structure
- Eg2. Build capability to purchase products using credit card
Scrum of Scrum
- Scaled agile technique
- Helps organizations to connect with multiple Scrum teams to develop and deliver complex solutions
What elements constitute a good user story?
- A description
- Pre-condition
- Performance criteria
- UI design links
- Dependencies
- Acceptance criteria
- Additional notes
Explain the distinction between epics, stories, and tasks?
Epics (Large-Scale Initiatives)
- An epic is a large body of work that can be broken down into smaller, manageable pieces.
- Epics contain multiple stories.
- Example: Display trips data
Stories (User-Centric Features)
- A story (or user story) is a specific functionality or requirement that contributes to an epic
- Stories are broken down into tasks.
- Example: As a scheduler, I should be able to view speed and distance so that I schedule a trip
Tasks (Actionable Work Items)
- A task is a granular unit of work required to complete a story.
- Tasks are executed by developers, designers, or other team members.
- Example: Implement the backlog logic for calculating the speed and distance
Differentiate between Agile and Scrum
Agile
- Agile is a development methodology that follows an incremental approach
Scrum
- Framework of Agile.
- Follows an iterative and incremental approach called sprints which lasts 2-3 weeks
What are the Scrum Methodology steps?
- Refining and building the Product Backlog
- Sprint planning and building the sprint backlog
- Sprint in progress
- Daily scrum
- Sprint Review
- Sprint Retrospective
SAFe (Scaled Agile Framwork)
https://www.tutorialspoint.com/what-is-scaled-agile-framework-safe-methodology-tutorial
- Open source knowledge base
- based on lean-agile principles
- divided into 3 streams - team, program and portfolio
