Unlocking true collaboration

Question 1

Question: What are the five values that Scrum teams should focus on?

Answer 1

Answer: The five values are Focus, Courage, Openness, Commitment, and Respect.

Question 2

Question: How does Scrum encourage teams to maintain Focus?

Answer 2

Answer: Scrum encourages teams to take on only a few tasks at a time, breaking the work into smaller Sprints to maintain focus on each item.

Question 3

Question: What is the significance of Courage in a Scrum team?

Answer 3

Answer: Courage in a Scrum team enables them to tackle greater challenges as a cohesive unit, thanks to close collaboration and pooled skills.

Question 4

Question: Why is Openness considered one of the most important values in Scrum?

Answer 4

Answer: Openness in Scrum is vital for regular reviews with stakeholders, planning, and communication among team members.

Question 5

Question: What does Commitment mean in the context of Scrum teams?

Answer 5

Answer: Scrum teams commit to delivering high-quality work, being transparent with stakeholders, and a specific amount of work in each Sprint, which builds trust.

Question 6

Question: Why is Respect important within a Scrum team?

Answer 6

Answer: Respect fosters open communication, enabling team members to share impediments and support each other effectively.

Question 7

Question: What is the ultimate goal of Scrum teams in a real project?

Answer 7

Answer: Scrum teams aim to build people knowledge, foster team spirit, deliver successful projects, and ensure customer success while enjoying their work.

Question 8

Question: What is the key difference between the Waterfall and Agile approaches regarding team size?

Answer 8

In Agile, small cross-functional teams are preferred, while Waterfall often involves large groups working on long-term projects.

Question 9

Question: How many people are typically in a small Agile team for developing a small app?

Answer 9

Answer: A typical small Agile team for a small app comprises three people.

Question 10

Question: Who is responsible for translating business needs into project backlog items and prioritizing them in an Agile team?

Answer 10

Answer: The Product Owner is responsible for translating business needs into project backlog items and prioritizing them.

Question 11

Question: What roles do the other two developers in a small Agile team take on?

Answer 11

Answer: The other two developers in a small Agile team are often referred to as Business Engineers and are responsible for development tasks.

Question 12

Question: In a small Agile team, who typically takes on the role of the Scrum Master?

Answer 12

Answer: In a small Agile team, the duties of the Scrum Master are often assigned to the lead developer.

Question 13

Question: How does a small team size benefit communication and collaboration in Agile?

Answer 13

Answer: A small team size in Agile keeps communication lines short and enhances collaboration effectiveness.

Question 14

Question: When might it be necessary to involve Subject Matter Experts (SMEs) in an Agile project?

Answer 14

Answer: SMEs may be needed in Agile projects depending on the technical challenges, but they are not accountable for product delivery.

Question 15

Question: What happens to the team size when a company aims to develop multiple apps in Agile?

Answer 15

Answer: When developing multiple apps, a company may expand the team size by adding more developers, but they may still run projects in smaller teams once they’ve gained experience.

Question 16

Question: What is the purpose of Sprint 0 in Scrum?

Answer 16

Answer: Sprint 0 in Scrum is a period preceding development where the team familiarizes itself with the project, organization, and people involved.

Question 17

Question: What key events should happen during Sprint 0?

Answer 17

Answer: During Sprint 0, important events include an official kick-off meeting and an initial Product Backlog Refinement meeting to ensure user stories are in a ‘ready’ state.

Question 18

Question: Is Sprint 0 an official Scrum event?

Answer 18

Answer: No, Sprint 0 is not an official Scrum event, but it’s necessary to prepare the team for upcoming development.

Question 19

uestion: What is the purpose of the official kick-off meeting during Sprint 0?

Answer 19

Answer: The official kick-off meeting formalizes agreements, defines responsibilities, discusses dependencies, and confirms the project’s setup, promoting transparency and clear collaboration.

Question 20

Question: What does the Scrum Master do during Sprint 0 regarding technical challenges?

Answer 20

Answer: The Scrum Master identifies technical challenges and books the availability of Subject Matter Experts (SMEs) with the required skills to address these challenges.

Question 21

Question: Why is it important to have an understanding of the overall project during Sprint 0?

Answer 21

Answer: Understanding the overall project provides context and clarity about what needs to be created, helping the team prepare for development.

Question 22

Question: What is the purpose of the initial Product Backlog Refinement meeting during Sprint 0?

Answer 22

Answer: The Product Backlog Refinement meeting in Sprint 0 clarifies which user stories will be picked up during the first sprint and ensures they are in a ‘ready’ state.

Question 23

Question: What are the four main events in Scrum?

Answer 23

Answer: The four main events in Scrum are Sprint Planning, Sprint Review, Sprint Retrospective, and Daily Stand-Up.

Question 24

Question: What is the purpose of Product Backlog Refinement?

Answer 24

Answer: Product Backlog Refinement is aimed at reaching a mutual understanding of user stories, aligning priorities, and ensuring that backlog items are in a ‘ready’ state.

Question 25

Question: Who participates in Sprint Planning in Scrum?

Answer 25

Answer: Sprint Planning involves the Scrum Master, Product Owner, and the entire Development Team.

Question 26

Question: What is the role of the Scrum Master in Sprint Planning?

Answer 26

Answer: The Scrum Master facilitates Sprint Planning and ensures that it runs smoothly. They also pay attention to engaging Subject Matter Experts (SMEs) if needed.

Question 27

Question: What is the responsibility of the Product Owner in Sprint Planning?

Answer 27

Answer: The Product Owner is responsible for clarifying Product Backlog items, their acceptance criteria, and resolving any unanswered questions from Product Backlog Refinement.

Question 28

Question: What is the purpose of defining the “Definition of Done” during Sprint Planning?

Answer 28

Answer: Defining the “Definition of Done” is to agree on what criteria must be met for a user story to be considered complete, which helps ensure a shared understanding of what “Done” means.

Question 29

Question: What is the role of the Development Team in Sprint Planning?

Answer 29

Answer: The Development Team defines the work, effort, and scope necessary to meet their Sprint commitment, and they select which user stories to work on during the Sprint.

Question 30

Question: What does team velocity determine in Sprint Planning?

Answer 30

Answer: Team velocity determines how much work the team can accomplish during one Sprint, helping them estimate the number of user stories they can commit to.

Question 31

Question: Why is it important to keep the team composition intact in Sprint Planning?

Answer 31

Answer: Keeping the team composition intact promotes aligned and effective collaboration and helps maintain or improve team velocity.

Question 32

Question: What is the purpose of the Sprint Review in Scrum?

Answer 32

Answer: The purpose of the Sprint Review is to demonstrate the results of the Sprint to the Product Owner, Management, and end-users.

Question 33

Question: What is the starting point for reviewing the product during the Sprint Review?

Answer 33

Answer: The starting point for reviewing the product is the Sprint goal, which defines the scope of user stories to be addressed.

Question 34

Question: How are acceptance criteria used during the Sprint Review?

Answer 34

Answer: Acceptance criteria are used to check whether the presented increment meets the Definition of Done during the demo.

Question 35

Question: What can result from feedback received during the Sprint Review?

Answer 35

Answer: Feedback from the Product Owner and stakeholders may lead to the addition of new user stories in the next Sprint or adjustments to the Product Backlog.

Question 36

Question: What is the outcome of the Sprint Review?

Answer 36

Answer: The outcome of the Sprint Review is a set of potential new backlog items that are approved by the Product Owner.

Question 37

Question: When is the Sprint Retrospective typically held in Scrum?

Answer 37

Answer: The Sprint Retrospective is typically held at the end of each Sprint or at the end of a major development cycle.

Question 38

Question: What is the purpose of the Sprint Retrospective?

Answer 38

Answer: The purpose of the Sprint Retrospective is to reflect on the completed Sprint, gather feedback, identify what went well, what needs improvement, and plan interventions for the next Sprint.

Question 39

Question: Who facilitates the Sprint Retrospective?

Answer 39

Answer: The Sprint Retrospective is facilitated by the Scrum Master.

Question 40

Question: What are the key aspects evaluated during the Sprint Retrospective?

Answer 40

Answer: During the Sprint Retrospective, the team evaluates what went well, what didn’t go well, and identifies new actions or improvements to be undertaken.

Question 41

Question: How is feedback collected during the Sprint Retrospective?

Answer 41

Answer: Team members typically list five items in each category (what went well, what didn’t, new actions). The team then votes to select three improvement points for the next Sprint.

Question 42

Question: What should be avoided during the Sprint Retrospective to ensure effective improvements?

Answer 42

Answer: Avoid trying to change too much at once, as it may not lead to the desired process improvement.

Question 43

Question: Who is responsible for implementing improvement points identified during the Sprint Retrospective?

Answer 43

Answer: Every improvement point is the responsibility of the whole team but should have a designated owner to oversee its implementation.

Question 44

Question: What is the purpose of the Daily Scrum in Scrum?

Answer 44

Answer: The purpose of the Daily Scrum is for Scrum team members to share daily progress updates, discuss tasks for the day, and identify any impediments.

Question 45

Question: Who typically attends the Daily Scrum?

Answer 45

Answer: The Daily Scrum is typically attended by developers, but the Product Owner (PO) is also welcome.

Question 46

Question: What are the three key things that each developer shares during the Daily Scrum?

Answer 46

Answer: Each developer shares what they have done since the last Daily Scrum, what they plan to do until the next one, and any impediments they are facing.

Question 47

Question: Why is it called a “stand-up” meeting in Scrum?

Answer 47

Answer: It’s called a “stand-up” meeting because participants are encouraged to stand to keep the meeting quick and focused.

Question 48

Question: What is the recommended duration for the Daily Scrum?

Answer 48

Answer: The Daily Scrum is typically limited to 15 minutes to ensure it stays concise and efficient.

Question 49

Question: What is the primary goal of the Daily Scrum?

Answer 49

Answer: The primary goal of the Daily Scrum is to inform team members about progress, not to update the Scrum Master, and to identify any impediments that require help or input from others.

Question 50

Question: What is a common tool or chart used during the Daily Scrum to track progress?

Answer 50

Answer: A common tool used during the Daily Scrum is a burndown chart, which measures work completed versus the total required by the end of the Sprint.

Question 51

Which of the events is performed in the beginning of the sprint?

Answer 51

Sprint planning

Question 52

What happens in the daily scrum?

Answer 52

Team members share their progress, plans, and issues.

Question 53

What do Story Points associated with a user story indicate?

Answer 53

Estimation of complexity of a user story.

Question 54

During which of the Sprint Events does the development team determine user stories that will be finished in the sprint?

Answer 54

Sprint Planning