AGILE QUESTIONS

1. What is role of BA in SCRUM project? What are the deliveries are they expecting from BA in SCRUM projects?
Ans: In SCRUM project, BA role is as follow
 BA as Product Owner
 BA as Scrum Master
 Independent BA
The deliveries are they expecting from BA in SCRUM projects are:
 Gather requirements from Clients.
 Convert Requirements into User Stories and Create Product Backlog.
 Convey priority user stories to Scrum Master and Cross Functional Teams by Creating Sprint Backlog.

2. How documentation will be prepared in SCRUM projects?

Ans: In SCRUM projects, there is no specific documents will get created or prepared as like traditional documents (BRD/FRD etc.) as the key point in the
agile manifesto is “Working software is preferred over comprehensive documentation”. This does not mean that there is no documentation in Agile or Scrum
projects.
There are certain number of information radiators and artifacts defined in the Scrum framework which the Scrum teams can make use of them. Few of them
are:
a. Product Backlog:
A list of requirements from clients in form of User stories. It is owned by the Product Owner.
b. Sprint Backlog:
A prioritized list of items the Scrum Team needs to execute in the upcoming Sprint. Any risk mitigating activities are also included as tasks in
the Sprint Backlog.
c. Scrum Board:
It is tool used to track the work in a Sprint. It is also known as a task board or a progress chart. The most basic version of a Scrum board is
divided into three sections: To Do (sometimes referred to as Work Not Started), Work In Progress, and Completed Work.
d. Burndown chart:
A burndown chart shows the amount of work that has been completed in an epic or sprint, and the total work remaining.
e. Impediment Log:
Impediments or obstacles encountered by the team should be formally recorded by the Scrum Master in an Impediment Log.

3. How costing and timelines decided in SCRUM project?

Ans:
  The cost of an Agile project is simply the fixed cost per sprint multiplied by the number of sprints the project will take, and number of resources are
going to working with some buffers.
 Creating an Agile project timelines which starts with a pre-planning phase, where the product owner defines the project goals and prioritizes
requirements (the product backlog) which need to be delivered as a final product. The team formation, as well as a high-level time and cost estimation
are also documented during this first stage.
Next, the team will break the functionality from the product backlog into several sprints or iterations and determine the length of a sprint (Min 10
days or Max 30 days per sprint). The iterations are then assigned to releases, where each release should deliver one or more working product
increments. This initial documentation can act as an Agile release plan template (Gantt chart), based on which the team can plan the dates for the
release milestones, as well as for the final product delivery.

4. What is role of BA in SCRUM project? What are the deliveries are they expecting from BA in SCRUM projects?
Ans: Please refer the answer to question 1 as its repeating question.
5. Who will BA reporting too in SCRUM project?
Ans: Product Owner. Also, it is depending on Organization to Organization, so BA may report to Project Manager.

6. What is role of project team in SCRUM project?

Ans: In SCRUM project, project team is referred as Scrum team which involves Product Owner/Business Analyst, Scrum Master and Cross Functional team
(Developers, Testers, DBA, Support Analysts etc).

7. Is there development, testing, UAT and production server existing in SCRUM project?
Ans: Yes

8. What is the role of BA in deployment process in SCRUM project?

Ans: BA doesn’t play any role in internal deployments.
BA role in UAT and PROD deployment as follow.
 BA will take release document from development team and convey same document to client team.
 BA 2ill ask client users to follow release document steps on day of deployment.
 To make deployment process smooth, BA will take assistance from developer and tester.
 BA will monitor development process by taking RDP of client users.
 If something goes wrong in deployment process, then BA will fix it up with help of developers and testers.
 Post successful deployment, BA will do sanity testing just to make sure all high-level functionalities are working fine.
 BA will also ask client to test same and give sign off on that specific deployment.

9. Which tool they use to maintain product backlog and sprint backlog in AGILE SCRUM?
Ans: JIRA, Confluence, Vivify Scrum, Target Process, Clickup, Scrumwise

10. Is sprint timeline are pre-decided or decided on go?

Ans: Sprint timeline will be pre-decided during sprint planning.
In case any bug/defect/issues received then planning for next/current sprint will be decided on go.

11. Who is the decision maker to decide which user stories to be taken in specific Sprint?
Ans: Product Owner after having discussion with clients about priorities of user stories.

12. Do they have SCRUM team at client side? If YES explain the role of each team member?
Ans:
13. What is iterative approach and incremental delivery?
Ans:
 Iterative Approach: It means software development activities are systematically repeated in cycles known as iterations.
Each iteration will have phases such as Plan  DesignDevelopTestDeploy
 Incremental Delivery: It breaks the software development process down into small, manageable portions known as increments which add
on values in each iteration and at end final product value gets delivered with those increments.

14. Who has the right to stop specific sprint?

Ans: Only the Product Owner has the authority to cancel the Sprint when Sprint Goal becomes obsolete.

15. Will you find SCRUM team at one location or different location?
Ans: It depends on case to case, so team may be seating at same location or different locations.

16. Advantages and disadvantages of SCRUM?

Ans:
 Advantages:
 o It's adaptable and flexible.
o It encourages creative approaches.
o It involves low costs.
o It usually leads to better quality work.
o It improves customer satisfaction.
o It typically results in more satisfied employees.

 Disadvantages:
o It requires extensive training.
o It can be difficult to scale.
o It may require major transformations within the organization.
o It can be difficult to integrate with a classic project management approach.
o It is not related to the project's deadline.
o It requires the use of small teams.
o It requires experienced personnel.

17. What is the maximum size of SCRUM team?

Ans: The ideal size of SCRUM team is 7 to 9 with +/- 2

18. What is sprint task board?

Ans: In Scrum the task board is a visual display of the progress of the Scrum team during a sprint. It presents a snapshot of the current sprint
backlog allowing everyone to see which tasks remain to be started, which are in progress, and which are done.
PFB example which shows task board in JIRA tool.
19. Explain AGILE ceremonies in below format.
Ans:
Sr. No. Meeting Attendees Duration Points to Discuss When to
 Commence
1 Daily Required - Scrum Master & Ideally 15 1. The current progress of every Ideally it should be
Standup Cross Functional Team. minutes team member conducted in core
Meeting 2. Their short-term goals and tasks hours or in morning
Optional - Product for rest of day. or after start of new
Owner/Business Analyst 3. Any roadblocks that prevent them business day.
from doing their work.
2 Sprint Entire Scrum Team Two hours of 1. Come prepared with data Sprint planning
Planning - Product Owner/BA sprint planning and estimated story points occurs on the first
Meeting -Scrum Master for every one 2. Confirm estimated story points day of a new sprint.
-Cross Functional/Development week of sprint for all items on the backlog (or, at The event should
Team length minimum, in the next sprint) occur after the sprint
3. Agree on the items to move to the review and
new sprint retrospective from
4. Determine the team’s capacity for the previous sprint
the upcoming sprint and compare so that any output
it with the total story points from those
proposed  discussions can be
5. End the meeting with a Q&A to considered when
ensure all team members are on planning for the new
the same page  sprint.
3 Sprint Required - Entire Scrum Team One hour for Team features a product At the end of each
Review - Product Owner/BA sprint review demonstration where a working sprint
Meeting -Scrum Master every one version of the latest increment is
-Cross Functional/Development week of sprint presented and inspected.
Team length.

Optional
-Stakeholders/Client/Customer
(Depending on case to case)
4 Sprint Entire Scrum Team 45 minutes for Where the scrum teams along with Between sprints,
Retrospective - Product Owner/BA each week of the scrum master and product owner after the sprint
 Meeting -Scrum Master sprint length. meet and retrospect the last sprint review and before
-Cross Functional/Development they worked on. They majorly sprint planning for
Team discuss 3 things: the next sprint.
- What went well?
- What could be done better?
- Action Items

20.
&
21. What is Sprint burn down and burn up charts?
Ans: In SCRUM, a burn-down chart shows the amount of work remaining on a project (the remaining effort), whereas a burn-up chart shows
how much work has been completed and the total scope of the project. In a burn-down chart, the line goes from top to bottom as a team makes
progress, while in a burn-up chart the line climbs from the bottom upwards. Both charts use the same axies.

22. What are story points?

Ans: Story points are units of measure for expressing an estimate of the overall effort required to fully implement a product backlog item or any
other piece of work. Teams assign story points relative to work complexity, the amount of work, and risk or uncertainty.

23. What is Velocity?

Ans: Velocity is a measure of the amount of work a Team can tackle during a single Sprint and is the key metric in Scrum. Velocity is calculated
at the end of the Sprint by summing up the Points for all fully completed User Stories.

24. What is poker planning?

Ans:

25. What is DoD?

Ans: DoD stands for Definition of Done. It’s the checklist to ensure product quality of your deliverables.
It consists of quality checks/Criteria which are as follows.
 Code Review
 Test cases
 Test cases Review
 Unit test
 Zero P1 warnings
 Performance test
 Stress test