1. Scrum Ceremonies 2. Do we include V&V during Sprint planning 3. Scrum and Kanban differentiate 4. Scrum Planning Estimation Techniques or types 5. Product backlog vs sprint backlog 6. sprint review what happens 7. sprint retrospective what happens 8. Traditional Vs agile what is the general preference 9. Sprint Capacity, Capacity Planning, Velocity planning and what do those terms mean 10. Sprint burndown, burnup, release chart 11. backlog refinement and user story 12. Duration/Timebox of a sprint 13. what is an increment 14. Spike 15. Scrum of Scrums 16. Planning Poker Technique 17. Definition of Ready 18. Definition of Done

Question

Accepted Answer

Questions related to Scrum methodology and agile practices.

Scrum ceremonies include daily stand-up, sprint planning, sprint review, and sprint retrospective.
Verification and validation (V&V) should be included in sprint planning.
Scrum and Kanban differ in terms of roles, ceremonies, and visualization techniques.
Scrum planning estimation techniques include planning poker, t-shirt sizing, and affinity mapping.
Product backlog contains all the user stories while sprint backlog contains the selected user stories for the current sprint.
Sprint review is a demo of the completed work while sprint retrospective is a reflection on the process.
Agile is generally preferred over traditional project management.
Sprint capacity is the amount of work a team can complete in a sprint while velocity is the amount of work completed in a previous sprint.
Sprint burndown, burnup, and release charts are used to track progress.
Backlog refinement involves adding details to user stories while a spike is a time-boxed investigation.
A sprint typically lasts 2-4 weeks.
An increment is a sum of all the completed user stories in a sprint.
Scrum of Scrums is a meeting of multiple Scrum teams to coordinate work.
Planning poker is a technique for estimating user stories.
Definition of Ready and Definition of Done are criteria for user stories to be considered ready for development and done respectively.

Accepted Answer

1. Daily StandUp, Sprint Planning, Sprint Refinement, Sprint Review, Sprint Retrospective
2. Yes
3. Agile Methodology Uses Scrum as a framework and Kanban as a framework based on project we generally choose 1 or both combined called Scrumban
4. Scrum Planning does not exist but sprint planning exist, and no. of sprints determine the likely hood of the entire project delivery. Sprint planning happens at the beginning of the sprint and there are different techiniques like T-Shirt Size, Fibonacci, bucket categorization.
5. Product Backlog will have the entire series of Epics, User Stories, Support tasks, Sprint tasks, but whereas sprint backlog will have segregated user story tasks for a particular sprint.
6. Sprint review Demo takes place and feedback from PO and key stakeholders, if its a product increment being delivered to the customer he would also be involved.
7.  Rose, Bud, Thorns, What went will, What did not go well, What needs to be improved.
8. It depends on the project/organization and customer changes taking place., if the scope/requirements is frozen by the customer then it is preferred traditional, if there are continuous changes at a very high rate in requirement/scope then agile is preferred. 
9.  Capicity is no. of working days in a sprint, capicatincy planning is no, of people and there availablity, the no. of tasks/story points completed in previous sprints, the average of the 3 sprints is the velocity planning average points.
10. no. of items/story points remaining in the sprint is burndown, the inverse is burn up, no. of sprints planned and the no. of sprints completed and relevant story points completed vs remaining is release plan.
11. Backlog refinement is done by the PO and some times combined with Scrum Master to brake epics into user story tasks using INVEST method.
12. no. of weeks in a sprint is timebox, generally 1-4 weeks
13. Agile every sprint is iterative and incremental.
14. A spike is similar to support task, where it would not contribute to the directly but indirectly to support a Epic/User story
15. Each team has a Scrum frame work, when 2 or more teams needs to collaborate to deliver a project then Scrum of Scrums is required.
16. Planning poker is a way of avoiding bias while estimating individualy on the user story/task the amount of points required for completion of that user story/task
17. Before taking a task into the sprint DOR
18. To move the task to complete in the sprint is DOD

TCS Associate Consultant interview questions & answers

Popular interview questions of Associate Consultant