Roles and Organization in Scrum Flashcards
1
Q
What are the aspects to consider when it comes to Scrum
A
- Roles & organization
- Business justification
- Quality
- Change
- Risk
2
Q
What are the Scrum Roles
A
- Core team: Product owner/ Scrum Master / Development Team
- Non-core Team: (Not mandatory)
Stakeholders / Vendors / Scrum Guidence Body (SGB)
3
Q
What is Scrum Master Identity
A
- Scrum master is servant leader of the scrum team.
- Plays role of motivator, facilitator and coach.
- Scrum Master is not a Project Manager.
- Well versed with scrum fundamentals and have more than basic training.
- Notices non-verbal clues, acts as mediator in conflicts.
- Good communicator and builds trust with both team and customer.
- Need to work with product owner.
- Help the team to develop to complete scrum task by removing impediment, monitoring team health.
4
Q
What are Scrum Master Responsibilities
A
- SM is not responsible for project performance, that role goes to Scrum team.
- SM will work with PO to identify stakholder(s) and select Scrum Team.
- SM enables team to use scrum practices effectively and coach the team on practices while providing guidance.
- Challange the team to improve performance and deliver more results effectively.
- SM protects team from distraction and seel resolution to impediments that may impact team’s performance.
- SM works with all core tram members and SM may be asked to explain scrum to stakeholder(s).
- SM may be called to assist the PO with maintenance of Prioritized product backlog, development of epic and defining done criteria.
- SM coordinates release planning and length of sprint.
- SM are agents of change improvement within project and also organization with respect to flexibility and adaptability.
5
Q
What are the Scrum Master Authority
A
- SN do not have direct authority over the project.
- SM is a “ motivator”, “facilitator”, “scrum solicitor”, “coach”.
- No authority to make decision on behalf of the team.
- Ensures that scrum practices are followed.
- How SM influence:
- With deep knowledge of scrum principles and practices.
- Advocate on behalf of all project stakeholders.
- Approachable and perception.
6
Q
What is Product Owner Identity
A
- Responsible for achievement of business value.
- Defines Project Vision
- Identifies Stakeholders.
- Help finalize selection of Scrum Master and with the Scrum master the Scrum Team.
- Representative of Business and the Voice of Customer (VoC).
- Product Owner maintains dual view of project:
- Understand, support and identify stakholder requirement that can be expressed as stories.
- Understand needs and working of scrum team.
7
Q
What are Product Owner Responsibilities
A
- PO should understand what customer needs and combine with business benefits.
- PO works with customer stakholders and project sponsor to establish a brief project vision.
- PO is responsible to define aceptance criteria for every user story.
- PO creates and maintains prioritized product backlog.
- PO works with scrum teram during sprint planning meeting to include user story in sprint backlog.
- PO participlate in sprint review meeting to approve done user stories.
- Collaboration between PO and SM is essential for getting feedback and ensure solution meets customer needs and expections.
8
Q
What are the Product Owner Authority
A
- PO respobsble product backlog, which is the main planning tool.
- PO is focus on business aspect.
- PO needs not be developer themselves, they just need to know about development, but lot about development business.
- Communication with customer and use the information to keep product backlog updated with all changes.
- PO measures performance of project, forecast the completion date, and make this information available to all stakeholders.
- PO understand the business, so they rank each product backlog item based on ROI.
- The product backlog items should be sorted based on their value, so higher they are on list the sooner will developed by scrum team
- PO decisions might be influenced by others, but he/she must have the final say.
9
Q
What is a Scrum Development Team
A
- Responsible for delivering backlog items and manageing thrie own efforts.
- Cross-functional and capable of doing all task involved in each product backlog.
- They should find their way rather than taking orders.
- A task might be assinged to single member throughtout sprint, but whole scrum team will be responsible and accountable for task.
- If change in team member, then it should not happen during sprint and since there will be short term decrease in productivity when team changes.
- Scrum effectiv when there are 3-9 member in scrum team.
- Deliver final product in step by step increaments.
10
Q
How to determin product quality
A
- Quality Definition
- Achieve business values expected by customer.
- Integrate activities in sprint to optimize quality.
- Functional vs Non-functional requirement.
- Acceptance Criteria
- PO responsible to write user stories in product backlog.
-Met when user story considered done.
-SM to help PO to define measureable acceptance criteria.
- PO responsible to write user stories in product backlog.
- Definition of Done (DoD)
- Broader than acceptance criteria.
- Not changed during sprint.
- Quality Management in Scrum
- Quality planning is part of customer satisfaction.
- PDCA cycle (plan-do-check-act).
11
Q
What are the aspects of Change in Scrum
A
- Supporting Change
- Change is normal
- Responding to change over following a plan.
- Unapproved and Approved Change Request.
- Small changes approved by PO.
- Process needs to be followed.
- Felxibility vs. Stability
- Maintain stability through change.
- Change can be requested and approved anytime.
- Change should not be introduced during sprint.
- Integrate Change
- PO responsible for ensuring that product is properly prioritized.
- Change can be reason for termination of sprint.
- SM to protect Scrum team with outside influence during sprint.
12
Q
What are the aspects of Risk in Scrum
A
- About Risk
- Uncertain event that can be impact project objectives.
- Risk Attitudes
-Risk averse, Risk neutral, Risk seeking. - Risk Identification
- Lesson Learned.
- Checklist.
- Risk breakdown structure.
- Risk Assement
- Probability, proximity, impact.
- Expected monetray value = probability x impact.
- Risk Prioritization
- Create list of prioritized risks.
- Risk Mitigation
- PO owned business aspect of risks.
- SM maintains visibility, awareness and communications.