Sl.No.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
Questions
What is meant by Agile mindset?
What are the limitations of Waterfall model?
What are the advantages of Agile?
How Iterative approach is different from Incremental approach?
What are the major roles in scrum? #38
What are the scrum ceremonies? #37
What is the difference between Product backlog and Spring backlog? #36
Explain the Scrum process flow. #36
Give an example to a User Story template/syntax. #39
What is the difference between Epic, User Story and Task? #40 & #41
Explain the sequence of activities involved in Sprint Planning. #42, #43 & #44
Name few Agile Frameworks and Practices.
What is daily scrum?
What happens in Sprint Planning?
What are the pre-requisites and outcomes of Sprint Planning?
What Is Inspect and Adapt?
Explain the process of Sprint Review & Sprint retrospective.
What is an impediments? How to handle that?
What is Capacity planning?
What are the triple constraints in project management? How they differe from Waterfall to Agile?
What is an estimate? Why do we estimate?
Explain Absolute Vs Relative Estimations.
What is the purpose of Base Story?
What are the factors in Relative Sizing?
What is meant by Agile Velocity? Explain Estimated Velocity Vs Actual Velocity Vs Average Velocity
What is meant by Definition of Ready? How do you define DoR with INVEST Model?
What is meant by Definition of Done?
What is meant by Acceptance Criteria?
Sl.No.
1

4
5
6
7

8
9
10
11

12
13

14
15

16
17
18

19
20
21
22

23

24

25

26

27

28

29

30
31

32

33

34

35

36

37

38

39
40

41

42

43

44

45

46

47
48

49

50

51

52

53

54
55

56

57
Definitions
Requirements analysis is a process used to determine the needs and expectations of a new product.
It involves frequent communication with the stakeholders and end-users of the product to define expectations, resolve conflic
document all the key requirements.

The design phase involves transforming the software requirements gathered during the Requirements Analysis phase into a st
design document.
Here we develop the conceptual blueprint of a software project.

The deployment phase is the final step in the SDLC that delivers the final product to the customer in a live production environ

The Maintenance Phase include software upgrades, repairs, and fixes of the software if it breaks.
Agile is a group of methodologies having an ability to create and respond to change.
Agile is a way of dealing with an uncertain and turbulent environment.
Agile means “incremental,” allowing teams to develop projects in small increments. It's known for breaking down projects into
chunks called “sprints.”
Agile helps to ensure that development teams complete projects on time and within budget
Scrum is one of the many frameworks of Agile methodology.
Scrum is a framework for getting work done within agile.
Scrum Vs Waterfall
Interative Development - Sequential Development
Delivery every 2 weeks - Delivery phase by phase
Regular feedback - Late learning at the end
Requirements can change - Requirements clearly defined
High Team collaboration - Low Team collaboration
High Client involvement - Low Client Involvement

Sprint is a short, time-boxed period when a scrum team works to complete set of PBIs (Tasks / User Stories)
What is the 3 5 3 rule in scrum?
A Scrum Team is built by 3 roles: the Product Owner, Scrum Master, and Developer. These roles work through 5 events: Sprin
Planning, Daily Scrum, Sprint Review, and Sprint Retrospective to build 3 artifacts: Product Backlog, Sprint Backlog, and Produ
Increment.

3 C's of Scrum: The 3 C's (Card, Conversation, Confirmation) of User Stories

A product backlog is a prioritized list of work for the development team that is derived from the product roadmap and its
requirements.
A sprint backlog is a subset of the product backlog and lists the work items to complete in one specific sprint.
Scrum has three roles: product owner, scrum master, and the development team members
Who can cancel a sprint?
Only the Product Owner has the authority to cancel the Sprint.
An EPIC is a large body of work that can be broken down into a number of smaller stories
A User Story is the smallest unit of work in an agile framework.
A daily Scrum meeting is a short, time-boxed meeting where the Scrum team gather to provide updates on
1. what they worked on the previous day,
2. what they plan to do today, and
3. what (if any) impediments or issues they encounter at the moment.
Impediments : It is anything that slows down or hinders the productivity of a team, hence affecting the successful delivery of
product.
Type of Impediments : Technical, People, Process, External, etc.
Skills needed to remove impediments : Facilitation, Communication, Coaching, Conflict resolution, Agile know-how, Empathy,

Capacity planning (Slide #45) in Agile is the process of determining a team's ability to take on and complete work within a sp
timeframe, considering factors like team member availability, skills, and historical data.
Inputs : Man days/hours available, Team's velocity, skillset
Output : Potential Capacity (for the upcoming sprint)

Sprint Planning
- It is the Process of Planning for the upcoming sprint
- The Scrum Team identifies set of User Stories (PBIs) to be completed in the next sprint.
Inputs : Product Backlog (Refined & ordered), Estimated PBIs (at the top) and Velocity of the team (Historic data.
Process:
1) The PO Presents the objective for the sprint
2) The Scrum team comes up with the Sprint Goal
3) The Scrum team Identifies PBIs from the Product Backlog as per the Sprint Goal and adds them into Sprint Backlog
Outputs : Sprint Goal, Sprint Backlog, PBI's with identified sub-tasks

Triple Constraints (Slide #12)

Waterfall model : Time (variable), Cost (variable), Features (Fixed) & Quality (average/poor)
Agile Model : Time (Fixed), Cost (Fixed), Features (Variable) & Quality (better)

Limitations of Waterfall model (Slide #14)

- Upfront requirements
- Each SDLC phase is frozen, hence cannot go back or change
- Only one big release/delivery at the end
- Less Customer Collaboration

Advantages of Agile model

- Short iterations/sprints
- frequent delivery of working features
- More customer collabaration
- better team effort and communication
- Flexible enough to accommodate new requirements
- Quick Customer feedback

Inspect and adapt is a fundamental scrum principle that informs the practice of continuous evaluation and adjustment based
given conditions.
Inspect: to look at something closely and view it critically
Adapt: to adjust, modify, or change something for a new purpose or conditions

Scrum includes FOUR formal events for inspection and adaptation named Sprint Planning, Daily Scrum, Sprint review & Sprint
Retrospective.

The purpose of a sprint review is to gather feedback on (inspect) newly added features.
Sprint review focuses on reviewing and demonstrating the work done during the sprint and discussing the future scope of wor
product.

Sprint retrospective focuses on the work process, focusing on how the team worked collaboratively during the sprint.
Objectives : What worked well, What didn't work well and What can be improved.
Product Backlog Refinement : It is an act of breaking down and further defining Product Backlog items into smaller, more prec
items. This is an ongoing activity and can be done offline with or without teams.
Potential Refinement Tasks : Breakdown large PBI's, Ordering of PBI's, Estimates, add/remove PBI's, etc.

Estimation (Slide #52) : It is the process of estimating the time, effort, and resources required to complete a given feature or
functionality.
Need for estimation :
- Helps team to establish realistic goals and commitments
- Cost and Schedule transparency
- Helps PO in prioritization

Absolute estimation assigns specific values, like hours or days, to each task. It uses Man days/hours (in Waterfall model)
Relative estimation in agile compares tasks to one another without assigning specific values, often using units like story points
shirt sizing / Story Points (Agile)

Base Story (Slide #61) is a Story that already has an Estimation so that it can be compared for the purpose of Relative Sizing.

Relative Sizing - Factors

1. Amount of Work
2. Complexity
3. Risk
4. Dependency
5. Business Value

Merits of Relative Estimation

- Typically faster and Easy to perform
- Commitment as a “Team” rather than “Individual”
- Considers factors like Complexity, Risk, Dependency, etc. while estimating Stories
- Less pressure on the team (there is no hourly estimates) that brings better productivity

Estimation at different level of PBI

- Epic - Story Points (Fibonacci series) OR T-shirt size (S, M, L, XL, XXL)
- User Story - Story Points (Fibonacci series)
- Tasks (subset of User Stories) - Hours

Velocity (Slide #69) is used to measure how much work can be completed in each iteration.
Velocity is the average amount of work a scrum team completes during a sprint, measured in story points.
It is an important metric that helps the team improve efficiency by determining how much it can achieve over time

Estimated Velocity is the total effort estimates associated with user stories during Sprint Planning.
Actual Velocity is the total effort (Story point) achieved with user stories during the completed Sprint
Average Velocity : Velocity achieved (average) in the last X number of Sprints by the Scrum Team

Sprint Burndown chart (Slide #70) is a graphic representation that shows the rate at which work is completed and how much
remains.
It shows the overall and day-to-day team's progress toward the goal in terms of Story Points.
It shows
- the amount of work your team has already completed in a given Sprint, and
- the amount of time that the team has left to complete that work.
Acceptance Criteria (Slide #72) refer to a set of predefined requirements/conditions that must be met to mark a user story co
These conditions required for the customer, product owner, or stakeholder(s) to accept the work you've done.
The product owner is responsible for writing acceptance criteria.
Syntax : User Story, Scenario, Given - When - Then...

Definition of ready (DoR) is used to determine whether work on a User Story is ready to be started.
It means that the PBI meets a set of team-established criteria as to whether the story is ready for implementation.
INVEST Model is used to define the DOR.

INVEST Model (Slide #74)

“I” ndependent (of all others)
“N” egotiable (not a specific contract for features)
“V” aluable
“E” stimable
“S” mall (so as to fit within an iteration)
“T” estable

DOR Checklist (Slide #75)

- INVEST Principle
- User Story - Summary
- User Story - Description
- Acceptance Criteria

Definition of Done (DoD) is a set of criteria that a product increment must meet so that it can be considered as "completed" a
for customers.
It is a shared understanding among the team members of when a product increment is ready for release.
Sample DoD Checklist :
- Code is complete,
- Code refactored,
- meet acceptance criteria,
- Testing done,
- Peer Review,
- Code merged,
- Deployed

Conflict Resolution is the informal or formal process that two or more parties use to find a peaceful solution to their dispute.
Steps : Listen, Empathize, acknowledge/apologize & Implement the Solution.

What are the Scrum Artifacts?

- Product Backlog
- Sprint Backlog
- Product Increment
- Burn-down charts
- Sprint Goal
- Definition of Done

Scrum Reports - Velocity Trend Chart, Sprint Burndown chart, Defect Report, Sprint Report, etc.
Risk - A possibility of suffering from loss in software development process is called a software risk

Risk Management - Steps

1. Risk Identification - identify thetype of the risk - operational, financial, resource, etc.
2. Risk Assessment - Severity (High, Medium or Critical)
3. Risk Response - Implementing a solution
4. Monitoring or Review
5. Closure

Planning Poker is a planning and estimation technique used by Agile teams. It helps software teams to estimate PBIs.

How do you Split User Stories (PBIs - Refinement Process)?

- Based on the conditions in the Acceptance Criteria
- Based on the business rules
- Based on the Test Cases

Explain the difference between the Burndown chart and Burnup chart?
- Burndown chart shows the remaining work
- Burnup chart tracks the work that has already completed

Responsibilities of a Scrum Master (frequently asked question in interviews)

- Guiding the Scrum team through executing the Scrum framework correctly
- Removes Impediments and help the team members
- Scheduling and Facilitating the Scrum Ceromonies
- Collaborate with product owner

Typical day of a Scrum Master (frequently asked question in interviews)

- Reading email reponses,
- Check for the day's scheduled meetings
- Facilitate the scheduled meetings
- Schedule new meetings, if requried
- Monitor the Sprint Progress
- Communicate with the PO and Scrum Team
- Removal of Impediments, if any.

Sprint 0 (Zero) - It is a practise/trial sprint happening before Sprint 1

What is ‘Scrum of Scrums’?
It is a technique used to connect multiple teams who need to work together to deliver complex solutions.

What is Empirical Process Control in Scrum?

Empiricism refers to work that’s based on facts, experiences, evidence, observations, and experimentation. It is established an
followed in Scrum.

What is a typical Sprint duration?

It can be 2 or 3 or 4 weeks, depends on the type of the project
2 Weeks sprint is a most widely used in the indestry.