Capgemini Agile Project Manager and Scrum Master Interview Questions, Process, and Tips

Team success in Scrum can be measured through various metrics such as velocity, sprint burndown charts, and team satisfaction.

• Velocity: Measure the amount of work completed in each sprint. A consistent increase in velocity indicates team success.

• Sprint burndown charts: Monitor how well the team is progressing towards completing the sprint goal. A steady burndown chart shows success.

• Team satisfaction: Conduct regular re...read more

EPIC is a large body of work that can be broken down into smaller, more manageable pieces called stories.

• EPIC is a high-level requirement that is too large to be completed in a single iteration.

• Stories are smaller, more detailed requirements that can be completed within a single iteration.

• EPICs are typically broken down into stories during the backlog grooming process.

• Stories are usually written from the perspective of...read more

Story points are arrived at through collaborative effort of the team based on complexity, effort, and risk involved in a user story.

• Discuss the user story with the team to understand the requirements and potential challenges

• Break down the user story into tasks and estimate the effort required for each task

• Consider factors like complexity, uncertainty, dependencies, and risks involved in completing the user story

• Use a s...read more

Team velocity is a measure of the amount of work a team can complete in a sprint.

• Team velocity is calculated by summing up the story points completed in a sprint.

• It helps the team understand how much work they can realistically accomplish in future sprints.

• Velocity is used for sprint planning and forecasting project timelines.

• It is not a measure of individual productivity but rather the team's overall capacity.

• For exam...read more

Major challenges faced include communication issues, changing requirements, team dynamics, and stakeholder management.

• Communication issues between team members and stakeholders can lead to misunderstandings and delays.

• Changing requirements can disrupt project timelines and require frequent adjustments.

• Team dynamics such as conflicts or lack of collaboration can impact productivity and morale.

• Stakeholder management invo...read more

Agile ceremonies are regular meetings that help teams collaborate, plan, and review progress in Agile projects.

• Examples include Daily Standup, Sprint Planning, Sprint Review, and Retrospective

• These ceremonies help teams stay aligned, communicate effectively, and continuously improve

• Each ceremony has a specific purpose and timebox to ensure efficiency and productivity

The Agile Manifesto talks about the anti-pattern of excessive documentation.

• The Agile Manifesto values 'Working software over comprehensive documentation'.

• This principle emphasizes the importance of focusing on delivering working software rather than spending excessive time on documentation.

• Excessive documentation can lead to delays, miscommunication, and reduced flexibility in responding to change.

• Teams should aim to ...read more

Planning Poker is a consensus-based technique used in Agile project management to estimate the effort or relative size of user stories.

• Team members use a deck of cards with values representing the complexity of a task.

• Each team member selects a card without revealing it, then reveals simultaneously.

• Discussion follows until a consensus is reached on the estimate.

• Common values on the cards include 0, 1, 2, 3, 5, 8, 13, 2