10+ CaratLane - A Tata Product Scrum Master Interview Questions and Answers

A task is a unit of work that needs to be completed within a project. It can be categorized into different types based on its nature and complexity.

• A task is a specific piece of work that needs to be accomplished.

• Tasks can be categorized into different types such as development tasks, testing tasks, documentation tasks, etc.

• Tasks can vary in size, complexity, and duration.

• Tasks are usually represented on a task board or in a project management tool.

• Tasks should be well-define...read more

Velocity is calculated by summing up the story points completed in a sprint. Capacity is the amount of work a team can handle in a sprint.

• Velocity is calculated by summing up the story points completed in a sprint

• Capacity is the amount of work a team can handle in a sprint

• Velocity is used to forecast the amount of work a team can complete in future sprints

• Capacity is determined by considering factors like team size, availability, and individual skills

• Velocity and capacity are...read more

The recommended team size in Scrum is 5-9 members.

• The Scrum Guide recommends a team size of 5-9 members.

• Smaller teams may have difficulty completing all necessary work, while larger teams may face coordination challenges.

• A larger team may also lead to decreased individual accountability and increased complexity in communication.

• Having a cross-functional team with diverse skills and perspectives is important for successful collaboration.

• Examples: A team of 7 developers, a team...read more

There are two types of estimation in Agile: Relative and Absolute.

• Relative estimation involves comparing the size of one item to another, using techniques like Planning Poker or T-Shirt sizing.

• Absolute estimation involves assigning a numerical value to an item, using techniques like Wideband Delphi or Affinity Mapping.

• Relative estimation is more commonly used in Agile, as it is quicker and more collaborative.

• Absolute estimation is useful for more complex projects or when a mo...read more

All stakeholders including the development team, product owner, and customers can participate in Sprint Review.

• Development team presents the completed work to stakeholders

• Product owner reviews the progress and provides feedback

• Customers can provide feedback on the product

• All attendees collaborate to identify improvements for the next sprint

Agile values focus on individuals and interactions, working software, customer collaboration, and responding to change. The 12 principles guide the Agile approach.

• Agile values prioritize people and their interactions over processes and tools

• Working software is the primary measure of progress

• Customer collaboration is essential for success

• Responding to change is more important than following a plan

• The 12 principles include continuous delivery, self-organizing teams, and regular...read more

Prioritizing the Product Backlog is crucial for successful product development.

• Collaborate with stakeholders to understand their needs and priorities

• Use techniques like MoSCoW, Kano model, and Cost of Delay to prioritize

• Consider dependencies, risks, and technical feasibility

• Regularly review and adjust the prioritization based on feedback and changes in the market

Scrumban is a hybrid Agile methodology that combines Scrum and Kanban.

• Scrumban is used when a team wants to transition from Scrum to Kanban or vice versa.

• It allows for flexibility in the process and can be customized to fit the team's needs.

• Scrumban uses a Kanban board to visualize work and limit work in progress (WIP).

• It also includes Scrum ceremonies such as daily stand-ups and retrospectives.

• Scrumban is useful for teams that have a mix of predictable and unpredictable work...read more

User stories are short, simple descriptions of a feature told from the perspective of the end user. INVEST is a set of criteria to evaluate user stories.

• User stories describe what the user wants to achieve and why

• They are written in a simple, non-technical language

• INVEST stands for Independent, Negotiable, Valuable, Estimable, Small, and Testable

• User stories should be independent of each other

• They should be negotiable and subject to change

• They should provide value to the end ...read more