Deloitte Senior Scrum Master Interview Questions and Answers

Sprint velocity is the amount of work completed in a sprint, while sprint capacity is the total amount of work a team can handle in a sprint.

• Sprint velocity is a measure of how much work a team can complete in a sprint based on past performance.

• Sprint capacity is the total amount of work a team is capable of completing in a sprint, taking into account team size, availability, and skills.

• Velocity helps in predicting how...read more

Sprint velocity is calculated by summing up the story points completed in a sprint. Sprint capacity is the total story points a team can commit to in a sprint.

• Sprint velocity is calculated by adding up the story points completed in the previous sprints and dividing by the number of sprints.

• Sprint capacity is determined by the team's historical velocity and their availability for the upcoming sprint.

• For example, if a te...read more

Common engineering practices include Agile methodologies, continuous integration, test-driven development, and pair programming.

• Agile methodologies such as Scrum and Kanban for project management

• Continuous integration to regularly merge code changes into a shared repository

• Test-driven development to write tests before writing code

• Pair programming for collaborative coding and knowledge sharing

The hierarchy structure of backlog in Agile is based on prioritization and refinement of user stories.

• Backlog items are prioritized based on value to the customer

• User stories are broken down into smaller tasks for implementation

• Backlog is constantly refined and updated based on feedback and changing requirements

Product increment is a potentially shippable version of the product at the end of the sprint.

• Product increment is the sum of all the completed and done user stories in a sprint.

• It should be in a usable condition and meet the team's definition of done.

• Sprint velocity for a team size of 5 can be calculated by summing up the story points completed in the last few sprints and dividing by the number of sprints.

Story estimation is the process of assigning relative sizes to user stories based on complexity and effort required.

• Story estimation is typically done using story points, which are a unit of measure representing the overall effort required to implement a user story.

• Team members collectively discuss and analyze the user story to determine its complexity and effort, then assign story points based on their consensus.

• Commo...read more