Interview Questions and Answers

Scrum is an Agile framework that focuses on delivering a product incrementally through short, fixed-length iterations called sprints.

A Scrum Master is responsible for facilitating the Scrum process and ensuring the team follows Agile principles and practices.

Agile is iterative and flexible, while Waterfall is a sequential, linear approach to software development.

The Definition of Done is a checklist that defines the criteria a product increment must meet to be considered complete.

Velocity is a measure of the amount of work a development team can complete during a sprint, helping with future sprint planning.

Continuous Integration is the practice of regularly merging code changes from multiple contributors into a shared repository.

The Product Owner is responsible for defining and prioritizing the product backlog, ensuring the team delivers value to the customer.

QA is involved in the development process from the beginning, ensuring that quality is maintained throughout the lifecycle of the project.

A Release Manager coordinates the release planning and ensures that the product increment is ready for deployment.

The Agile testing pyramid is a concept that suggests a testing strategy with a higher focus on unit tests, followed by integration tests and a smaller number of end-to-end tests.

A business analyst in Agile helps define and prioritize user stories, ensuring that the product meets the needs of the business and customers.

WIP limits are constraints on the number of tasks or user stories that can be in progress at the same time, preventing overloading the team.

Technical Debt refers to the accumulated cost of postponing necessary work on a project, such as refactoring or addressing code issues.

A Scrum of Scrums is a meeting where representatives from different Scrum teams coordinate and discuss dependencies between their work.

Lean principles in Agile focus on delivering value to the customer by eliminating waste, improving efficiency, and optimizing the workflow.

A Release Burndown Chart tracks the progress of completing all the features planned for a release over time.

Pair programming involves two programmers working together at one workstation, with one typing and the other reviewing the code.