1. What is Agile?

Answer: Agile is a way of working where teams deliver work in iteration rather than all at once. It
focuses on flexibility, collaboration, and customer feedback. Agile teams work in iterations, called
sprints, and continuously improve their work based on feedback.

2. What is the difference between Agile and Waterfall?

Agile : Agile is a way of working where teams deliver work in iteration rather than all at once.

Waterfall : Waterfall is a rigid method where all planning is done upfront, and work follows a strict
sequence.

Agile : Changes are welcome can be made along the way.

Waterfall : In Waterfall, changes are difficult to accommodate once the project is underway.

3. What are Sprints?

Agile teams work in iterations in order to complete the work. These iterations are called sprints. The
sprint is the short or fixed time process usually 1-4 weeks. At the end of sprint team delivers working
piece of project like feature or update and gets feedback to improve in the next sprint.

4. What are some key roles in Agile?

Product Owner: Responsible for:

i. Decide the tasks to be completed by the team.

ii. Prioritizing tasks.

Scrum Master: Ensures the team follows

i. Agile practices

ii. removes any obstacles that slow down the team progress.

Development Team: The group that works on delivering the product or project.

5. What is a User Story?

Short description of the feature from end user prospective. It follows the format "As a [user], i want
[goal] so that [outcomes of the goal achieved]. This helps the team understand what the user needs
and why.

6. What is a Product Backlog?

Prioritized list of all the features, improvements, and tasks needed for the project.

The Product Owner manages this list

Product Owner add new items and re-prioritize based on customer need.

7. What is a Sprint Review?

Answer:
A Sprint Review is a meeting held at the end of a Sprint. The team demonstrates what they have
completed and gets feedback from stakeholders (like customers or management) to see if any
changes are needed.

8. What is the purpose of a Daily Stand-up?

Answer:
The Daily Stand-up is a short meeting (usually 15 minutes) where team members share what they
worked on yesterday, what they plan to do today, and if they have any challenges. It helps the team
stay on the same page and resolve issues quickly.

9. What is Velocity in Agile?

Answer:
Velocity is a way to measure how much work a team can complete in a Sprint. It helps in planning
future Sprints by estimating how much the team can accomplish based on their past performance.

10. What is the Definition of Done (DoD)?

Answer:
The Definition of Done is a checklist that ensures a piece of work is fully completed. It can include
criteria like testing, documentation, or code review. Work is only considered "done" when it meets all
the items on this checklist.

11. What is the difference between an Epic and a User Story?

Answer:
An Epic is a large chunk of work that can be broken down into smaller tasks or features, called User
Stories. User Stories are more detailed and describe specific functions or features needed by the
user.

12. How do you handle changing requirements in Agile?

Answer:
Agile embraces change! When requirements change, the team can adjust the work for future Sprints.
Instead of trying to stick to a rigid plan, Agile teams focus on delivering what's most important to the
customer at the time.

13. What are the benefits of using Agile?

Answer:

• Flexibility to adapt to changes.

• Faster delivery of work in small parts.

• Regular feedback ensures the project is moving in the right direction.

• Better collaboration within the team and with the customer.

• Continuous improvement of the product and process.

14. What is a Retrospective?

Answer:
A Retrospective is a meeting held at the end of each Sprint where the team reflects on what went well,
what didn’t, and how they can improve in the next Sprint. It helps the team continuously improve their
way of working.

1. What is Jira?

Answer:
Jira is a tool used by teams to track tasks, bugs, or any work that needs to be done. It's especially
popular for managing projects and issues in software development teams, but it can be used for any
kind of task management.

2. What is an issue in Jira?

Answer:
An issue in Jira is any task, bug, story, or work item that needs to be tracked. For example, if you need
to fix a bug in software, that would be an "issue."

3. What are the main features of Jira?

Answer:

• Issue Tracking: Keep track of tasks, bugs, and work items.

• Agile Boards: Organize work with boards like Scrum or Kanban.

• Reporting: Get detailed reports about your team's progress.

 • Custom Workflows: Set up how tasks move from start to finish (like To Do → In Progress →
Done).

4. What is a Jira workflow?

Answer:
A workflow is the series of steps an issue moves through, from the time it's created until it's
completed. For example, a simple workflow might be:

• To Do → In Progress → Done

5. What are the different issue types in Jira?

Answer:
Common issue types include:

• Bug: A problem in the software.

• Task: General work that needs to be done.

• Story: A feature or requirement from the user’s perspective.

• Epic: A large body of work that can be broken down into smaller stories.

6. What is a Jira Scrum board?

Answer:
A Scrum board is used by teams following the Scrum framework. It helps organize work into sprints
(short, fixed periods) and shows what tasks are To Do, In Progress, or Done.

7. What is a Kanban board in Jira?

Answer:
A Kanban board helps teams visualize their work in a continuous flow. It shows tasks moving from To
Do to In Progress to Done, but there are no fixed time frames like in Scrum.

8. What are Jira filters?

Answer:
A filter allows you to search and save specific issues based on criteria you choose, like all bugs
assigned to you or all tasks due this week.

9. How do you create an issue in Jira?

Answer:
 1. Click on the Create button in Jira.

2. Fill out details like the issue type (bug, task, etc.), summary, and description.

3. Assign it to someone and choose the priority.

4. Click Create to save it.

10. What is a Jira project?

Answer:
A project in Jira is a collection of issues that belong to a specific goal, like a software development
project or a marketing campaign. Each project can have its own settings, boards, and workflows.

11. What are Jira components?

Answer:
Components are sub-sections of a project that help organize issues. For example, if you have a
project for a website, components might be "Frontend," "Backend," and "Design."

12. What are Jira versions?

Answer:
A version in Jira represents a specific release of your product. You can group issues under a version to
track what’s being worked on for a particular release.

13. What is a sprint in Jira?

Answer:
A sprint is a time-boxed period (usually 1-4 weeks) where a Scrum team works to complete a set of
tasks. At the end of the sprint, the team reviews their progress and plans for the next sprint.

14. How do you close an issue in Jira?

Answer:

1. Open the issue you want to close.

2. Move it through the workflow stages (for example, from In Progress to Done).

3. Once it's marked as Done, the issue is considered closed.

15. What is the difference between Scrum and Kanban boards in Jira?

Answer:
 • Scrum Board: Focuses on sprints and completing a set of tasks in a time frame.

• Kanban Board: Continuous flow of work, no sprints, and tasks move at their own pace.

16. What are swimlanes in Jira?

Answer:
Swimlanes are horizontal rows in a board that help group issues. For example, you might have
swimlanes for each team member or each priority level.

17. What are permissions in Jira?

Answer:
Permissions control who can view, create, edit, or delete issues. They help ensure that only the right
people can change important things in the project.

18. What is an Epic in Jira?

Answer:
An Epic is a large piece of work that can be broken down into smaller tasks (stories). For example,
"Build a shopping cart feature" could be an Epic, with individual stories like "Create the add to cart
button."

19. How do you link issues in Jira?

Answer:
You can link issues to show their relationship. For example, one issue might "block" another from
being done. To link:

1. Open the issue.

2. Click on More and select Link.

3. Choose the type of link (like "blocks," "duplicates") and the related issue.

20. What is a backlog in Jira?

Answer:
The backlog is where all issues or tasks that are not yet started are listed. It’s a to-do list of work that
the team plans to tackle in future sprints.

These questions and answers should give you a solid foundation for understanding Jira in an interview
setting!
1. What is Scrum?

Scrum is a framework used to help teams work together to build products or solve problems. It’s
often used in software development, but it can be applied to other industries as well. Scrum
focuses on delivering small, usable parts of a product in short periods called Sprints, which
usually last 2-4 weeks.

Example answer:

"Scrum is a framework that helps teams work together to complete projects in small,
manageable steps. Teams work in short cycles called sprints, and at the end of each sprint, they
have something ready to show or use."

2. What are the roles in Scrum?

There are three key roles in Scrum:

Product Owner: Decides what needs to be built and prioritizes the work.

Scrum Master: Ensures the team follows Scrum rules and removes obstacles.

Development Team: The group of people who do the actual work, like coding, designing, or
testing.

Example answer:

"In Scrum, there are three roles. The Product Owner decides what the team should work on and
prioritizes tasks. The Scrum Master helps the team work smoothly and solves any problems. The
Development Team is the group that builds or works on the product."

3. What is a Sprint?

A Sprint is a short, fixed period (usually 2-4 weeks) during which the Scrum team works on a
specific set of tasks. At the end of the Sprint, the team should have a working part of the product
that can be reviewed.

Example answer:

"A Sprint is a short time frame, usually 2 to 4 weeks, where the team focuses on completing a set
of tasks. By the end of the sprint, the team should have a piece of the product ready to show or
use."

4. What is a Sprint Planning Meeting?

Sprint Planning is a meeting where the Scrum team decides what work will be done during the
upcoming Sprint. The team selects items from the Product Backlog (a list of everything that
needs to be done) and creates a plan to complete them.

Example answer:

"A Sprint Planning Meeting is when the team comes together at the beginning of the sprint to
decide which tasks they’ll complete in the next few weeks. They pick tasks from a list called the
Product Backlog and plan how they’ll get them done."

5. What is a Daily Scrum (Daily Standup)?

The Daily Scrum is a short, daily meeting where team members quickly share what they worked
on the previous day, what they plan to work on today, and if they have any challenges.

Example answer:

"A Daily Scrum is a quick meeting that happens every day where team members say what they
worked on yesterday, what they’ll work on today, and if they have any problems. It helps
everyone stay updated."

6. What is a Sprint Review?

A Sprint Review is a meeting at the end of the Sprint where the team shows the work they
completed to the Product Owner and stakeholders. The goal is to get feedback and discuss the
next steps.

Example answer:

"A Sprint Review happens at the end of the sprint. The team shows what they have built to the
Product Owner and other people interested in the product. The goal is to get feedback and see if
any changes are needed."

7. What is a Sprint Retrospective?

A Sprint Retrospective is a meeting where the Scrum team looks back on the last Sprint and
discusses what went well, what didn’t, and how they can improve in the next Sprint.

Example answer:

"A Sprint Retrospective is a meeting where the team talks about how the last sprint went. They
discuss what worked well and what didn’t, so they can improve in the next sprint."
8. What is the Product Backlog?

The Product Backlog is a prioritized list of everything that needs to be done to improve the
product. It’s managed by the Product Owner, who adds new items, reorders them, and removes
unnecessary ones.

Example answer:

"The Product Backlog is a list of tasks or features the team needs to work on to build the product.
The Product Owner decides what goes on the list and in what order, so the most important work
gets done first."

9. What is a Definition of Done (DoD)?

The Definition of Done is a shared understanding of what it means for a task or product to be
considered complete. It could include things like passing all tests, being reviewed, and being
approved by the Product Owner.

Example answer:

"The Definition of Done is what the team agrees on for when a task is finished. For example, it
might mean the code is tested, reviewed, and approved before it’s called done."

10. What are User Stories?

User Stories are simple descriptions of a feature or task from the perspective of the user. They
usually follow a format like: "As a [user], I want [action] so that [benefit]."

Example answer:

"User Stories are short descriptions of something a user wants from the product. They usually
say who the user is, what they want, and why it’s important. For example, 'As a customer, I want
to be able to reset my password so I can log in if I forget it.'"

1. What is Acceptance Criteria?

Acceptance criteria define specific conditions or requirements that a product or feature must meet to
be considered complete. These are set by the product owner or stakeholders and ensure the feature
works as intended.
Simple Example:
Imagine you’re building an online shopping cart. Some acceptance criteria could be:

• The cart should allow users to add/remove items.

• The cart should display the total price of items.

• Users should be able to proceed to checkout from the cart.

Why Important?:
They ensure everyone (developers, testers, product owners) has a clear understanding of what “done”
means for a feature.

2. Difference between Acceptance Criteria and Definition of Done?

• Acceptance Criteria: Specific conditions for a particular user story or feature.

• Definition of Done (DoD): General checklist applicable to all features (e.g., code reviewed,
tested, documented).

Simple Example:
For a shopping cart feature:

• Acceptance Criteria could be that items can be added to the cart.

• DoD might be that all code is reviewed, the feature is tested, and the documentation is
updated.

3. What are User Stories?

A user story is a short description of a feature from the perspective of the end-user. It helps in
understanding what users need without technical jargon.

Format:
"As a [user], I want [some feature] so that [benefit]."

Example:
"As a shopper, I want to view the total price of items in my cart so that I can decide what to buy."

4. What are the 3C’s in User Stories?

The 3C’s framework helps write and refine user stories.

1. Card: A short description of the user story, usually written on a card.

2. Conversation: Discuss the details with stakeholders or team members to clarify the
requirements.

3. Confirmation: Acceptance criteria confirm that the story is complete.

Example:
 • Card: "Allow adding items to the cart."

• Conversation: Discuss how the user will add items.

• Confirmation: Test it against acceptance criteria.

5. What is the INVEST Criteria?

The INVEST criteria ensure that user stories are well-defined:

• I: Independent (Can be developed separately)

• N: Negotiable (Can be changed based on feedback)

• V: Valuable (Delivers value to users)

• E: Estimable (Can estimate time/effort)

• S: Small (Small enough to complete in a sprint)

• T: Testable (Can be tested against acceptance criteria)

6. What is the difference between a User Story and a Use Case?

• User Story: High-level description of a feature.

• Use Case: Detailed step-by-step interaction between the user and the system.

Example:

• User Story: "As a user, I want to reset my password."

• Use Case: Describes each step the user and system take to complete the password reset (e.g.,
request link, send email, validate token).

7. What are EPICs and how do they relate to User Stories?

• EPIC: A large user story that is too big to complete in one sprint. It’s broken down into smaller
user stories.

• User Story: A smaller piece of work derived from an EPIC.

Example:

• EPIC: "Develop an online checkout system."

• User Stories under this EPIC could be:

o "Allow users to add a payment method."

o "Display the total price before confirming purchase."

8. Scrum Concepts in Simple Terms:

• Sprint: A time-boxed period (usually 2-4 weeks) to complete a set of tasks.

• Product Backlog: A list of all desired features or tasks.

• Sprint Backlog: The tasks to be completed during the current sprint.

• Daily Standup: A quick daily meeting to discuss progress.

• Sprint Review: A meeting to review what was completed in the sprint.

• Sprint Retrospective: A meeting to discuss what went well and what could improve for the
next sprint.

9. How do you prioritize features?

Use frameworks like MoSCoW:

• Must-have: Features that are critical.

• Should-have: Important but not critical.

• Could-have: Nice to have but not necessary.

• Won't-have: Not needed now, maybe in the future.

10. What is a Minimum Viable Product (MVP)?

An MVP is the simplest version of a product that can still function and provide value to users. It helps
in testing ideas with minimal resources before fully developing a product.

Example:
An MVP for a ride-sharing app could be a basic app where users request rides, and drivers get
notified—no extra features like tracking or payment.

1. What is a Burndown Chart?

A Burndown Chart shows how much work is left to do in a Sprint or project over time.

Example:

• You start with 100 tasks in a Sprint.

• Every day, you update the chart to show how many tasks are left.

• The goal is to have the line go down to zero by the end of the Sprint.

Why it’s important:

• It helps the team see if they are on track to finish the work in time.

2. What is a Burnup Chart?

A Burnup Chart shows how much work has been completed and how much is still left.

Example:

• At the start of the project, you have a total of 100 tasks.

• As you complete tasks, the line moves up, showing progress.

• Unlike Burndown, it focuses on what’s done, not just what’s left.

Why it’s important:

• It’s good for showing progress and if scope is changing (e.g., new tasks are added).

3. What’s the difference between a Burndown and Burnup Chart?

• Burndown Chart: Focuses on how much work is left.

• Burnup Chart: Focuses on how much work is done and if the total work is increasing or
decreasing.

Example:

• If you have a sprint of 100 tasks, and you complete 50 tasks, the Burndown will show 50 tasks
left, while the Burnup will show 50 tasks completed.

4. What is Velocity in Scrum?

Velocity is the amount of work a team can complete during a Sprint.

Example:

• If a team completes 30 story points in one Sprint, their velocity is 30.

• Velocity helps predict how much work the team can handle in future Sprints.

5. What is a Sprint Review?

A Sprint Review is a meeting at the end of the Sprint where the team shows what they’ve built (the
increment) to stakeholders.

Example:

• The team demonstrates the completed features to the product owner and gets feedback.

• It’s an opportunity to inspect the product and adapt the backlog if needed.

6. What is a Sprint Retrospective?

A Sprint Retrospective is a meeting where the Scrum team discusses what went well, what didn’t,
and how to improve in the next Sprint.
Example:

• If the team faced delays due to unclear requirements, they can discuss ways to get better
clarity in future Sprints.

7. What is an Epic in Scrum?

An Epic is a large user story that is too big to complete in a single Sprint.

Example:

• "Build an online shopping system" could be an Epic because it contains many small user
stories like "Create a shopping cart" or "Add payment gateway."

8. What is a User Story in Scrum?

A User Story is a short, simple description of a feature from the perspective of the user.

Example:

• "As a user, I want to be able to add items to my shopping cart so I can buy them later."

9. What is the INVEST criteria for a User Story?

A good user story follows the INVEST criteria:

• Independent: It can be developed separately from other stories.

• Negotiable: The details can be changed before or during the Sprint.

• Valuable: It provides value to the user or business.

• Estimable: The team can estimate how long it will take to complete.

• Small: It can be completed in a single Sprint.

• Testable: It has clear acceptance criteria to know if it’s done.

10. What is the Definition of Done?

The Definition of Done is a checklist the team uses to decide if a User Story is truly complete.

Example:

• For a software feature, it might include:

o Code is written.

o Tests are done.

o Documentation is updated.