Roles and Organization in Scrum

Question 1

What are the aspects to consider when it comes to Scrum

Answer 1

1. Roles & organization
2. Business justification
3. Quality
4. Change
5. Risk

Question 2

What are the Scrum Roles

Answer 2

1. Core team: Product owner/ Scrum Master / Development Team
2. Non-core Team: (Not mandatory)
   Stakeholders / Vendors / Scrum Guidence Body (SGB)

Question 3

What is Scrum Master Identity

Answer 3

1. Scrum master is servant leader of the scrum team.
2. Plays role of motivator, facilitator and coach.
3. Scrum Master is not a Project Manager.
4. Well versed with scrum fundamentals and have more than basic training.
5. Notices non-verbal clues, acts as mediator in conflicts.
6. Good communicator and builds trust with both team and customer.
7. Need to work with product owner.
8. Help the team to develop to complete scrum task by removing impediment, monitoring team health.

Question 4

What are Scrum Master Responsibilities

Answer 4

1. SM is not responsible for project performance, that role goes to Scrum team.
2. SM will work with PO to identify stakholder(s) and select Scrum Team.
3. SM enables team to use scrum practices effectively and coach the team on practices while providing guidance.
4. Challange the team to improve performance and deliver more results effectively.
5. SM protects team from distraction and seel resolution to impediments that may impact team’s performance.
6. SM works with all core tram members and SM may be asked to explain scrum to stakeholder(s).
7. SM may be called to assist the PO with maintenance of Prioritized product backlog, development of epic and defining done criteria.
8. SM coordinates release planning and length of sprint.
9. SM are agents of change improvement within project and also organization with respect to flexibility and adaptability.

Question 5

What are the Scrum Master Authority

Answer 5

1. SN do not have direct authority over the project.
2. SM is a “ motivator”, “facilitator”, “scrum solicitor”, “coach”.
3. No authority to make decision on behalf of the team.
4. Ensures that scrum practices are followed.
5. How SM influence:
   
   • With deep knowledge of scrum principles and practices.
   • Advocate on behalf of all project stakeholders.
   • Approachable and perception.

Question 6

What is Product Owner Identity

Answer 6

1. Responsible for achievement of business value.
2. Defines Project Vision
   
   • Identifies Stakeholders.
3. Help finalize selection of Scrum Master and with the Scrum master the Scrum Team.
4. Representative of Business and the Voice of Customer (VoC).
5. 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.

Question 7

What are Product Owner Responsibilities

Answer 7

1. PO should understand what customer needs and combine with business benefits.
2. PO works with customer stakholders and project sponsor to establish a brief project vision.
3. PO is responsible to define aceptance criteria for every user story.
4. PO creates and maintains prioritized product backlog.
5. PO works with scrum teram during sprint planning meeting to include user story in sprint backlog.
6. PO participlate in sprint review meeting to approve done user stories.
7. Collaboration between PO and SM is essential for getting feedback and ensure solution meets customer needs and expections.

Question 8

What are the Product Owner Authority

Answer 8

1. PO respobsble product backlog, which is the main planning tool.
2. PO is focus on business aspect.
3. PO needs not be developer themselves, they just need to know about development, but lot about development business.
4. Communication with customer and use the information to keep product backlog updated with all changes.
5. PO measures performance of project, forecast the completion date, and make this information available to all stakeholders.
6. PO understand the business, so they rank each product backlog item based on ROI.
7. The product backlog items should be sorted based on their value, so higher they are on list the sooner will developed by scrum team
8. PO decisions might be influenced by others, but he/she must have the final say.

Question 9

What is a Scrum Development Team

Answer 9

1. Responsible for delivering backlog items and manageing thrie own efforts.
2. Cross-functional and capable of doing all task involved in each product backlog.
3. They should find their way rather than taking orders.
4. A task might be assinged to single member throughtout sprint, but whole scrum team will be responsible and accountable for task.
5. 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.
6. Scrum effectiv when there are 3-9 member in scrum team.
7. Deliver final product in step by step increaments.

Question 10

How to determin product quality

Answer 10

1. Quality Definition
   
   • Achieve business values expected by customer.
   • Integrate activities in sprint to optimize quality.
   • Functional vs Non-functional requirement.
2. 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.
3. Definition of Done (DoD)
   
   • Broader than acceptance criteria.
   • Not changed during sprint.
4. Quality Management in Scrum
   
   • Quality planning is part of customer satisfaction.
   • PDCA cycle (plan-do-check-act).

Question 11

What are the aspects of Change in Scrum

Answer 11

1. Supporting Change
   
   • Change is normal
   • Responding to change over following a plan.
2. Unapproved and Approved Change Request.
   
   • Small changes approved by PO.
   • Process needs to be followed.
3. Felxibility vs. Stability
   
   • Maintain stability through change.
   • Change can be requested and approved anytime.
   • Change should not be introduced during sprint.
4. 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.

Question 12

What are the aspects of Risk in Scrum

Answer 12

1. About Risk
   
   • Uncertain event that can be impact project objectives.
2. Risk Attitudes
   -Risk averse, Risk neutral, Risk seeking.
3. Risk Identification
   
   • Lesson Learned.
   • Checklist.
   • Risk breakdown structure.
4. Risk Assement
   
   • Probability, proximity, impact.
   • Expected monetray value = probability x impact.
5. Risk Prioritization
   
   • Create list of prioritized risks.
6. Risk Mitigation
   
   • PO owned business aspect of risks.
   • SM maintains visibility, awareness and communications.