AGILE

1. Agile framework provides flexibility to make changes in requirements, define new

requirements, and shuffle priorities even in the late stage of product development.
2. Agile methodologies adopt an iterative and incremental delivery of working software.
Scrum Methodology
The development of the project is achieved through iterative cycles known as Sprints.
In Agile methodology of software development, sprint is a set time period during which specific work has
to be completed and made ready for review.

Product owners are the champions for their product. They are focused on understanding business and
market requirements, they prioritize the work to be done by the engineering team accordingly.
1. Product Owners Build and manage the product backlog
2. They partner with the business and the various team to ensure that all the involved members
everyone understands the work items in the product backlog
3.Give the road map for the features to be delivered in the next sprint
4.Decides when the product to be delivered

Scrum masters are the champion for scrum within their team. They train the team, the product owner, and
the business on the scrum process and look for ways to fine-tune their practice of it.
1.Scrum master understands the work being done by the team and can help the team optimize their
delivery flow.
2.They schedule the needed resources (both human and logistical) for sprint planning, stand-up, sprint
review, and the sprint retrospective.

Scrum teams are the experts in their areas of work . The effective scrum teams are , co-located, and
usually contain a team of 5 to 7 members.
1. The Team members have differing skill sets, and cross-train each other so no one person becomes a
bottleneck in the delivery of work. S
2. Scrum teams approach where all the members of the team help one another to ensure a successful
sprint completion.
3. They forecast how much work can be complete over the iteration using past experience as a basis.

SCRUM Artifacts
Product Backlog is the artifact that holds entire set of requirements which is equivalent to
requirement specifications of the traditional model.
Product Backlog is groomed in a separate session or in a Sprint planning meeting. In the
grooming session, the stories are explained, defined in more detail along with acceptance tests.
Release Burndown The Release Burndown chart reflects the remaining Product Backlog items
across the releases.
Sprint Backlog real-time picture of the work that the Team plans to accomplish during the
Sprint. SB is a list of user stories and team is expected to complete them in the order they were
assigned.
Sprint Burndown displays remaining effort for all the tasks that were committed during the
Sprint.

SCRUM Events
Release Planning Meeting The purpose of release planning is to establish a plan and goals,
which the Scrum Team and the rest of the organization can understand and communicate.
Sprint Planning The work to be performed in a Sprint is planned in the Sprint Planning Meeting.
User stories are broken down to tasks, task level estimation is done and the team commits to
the Sprint goal. Product Owner, scrum master and the team participate in the Sprint planning.

The team gets clarity in a session of interactive conversation with Product Owner (PO) during
Release or Sprint level planning meetings.

Daily Scrum
The Daily Scrum meeting is a 15-minute time-boxed event for the Team to synchronize
activities. During the meeting, each Team member explains:
What he or she has accomplished since last meeting
What he or she is going to do before the next meeting
What issues/obstacles are in his or her way

Sprint Review
A Sprint Review Meeting is held at the end of the Sprint. During. The Sprint Review includes the
following:
Product Owner identifies what has been ‘Done’ and what has not been ‘Done’
Team demonstrates the work that has been ‘Done’ and answers questions about the
increment
Product Owner discusses the Product Backlog as it stands
The entire group discusses on what to do next

Sprint Retrospection Meeting

Retrospectives are planned at the end of each Sprint and each Release. It is a retrospection
meeting where the teams reflects on the happenings in the previous Sprint, both good and bad,
and take corrective actions which can be implemented in the subsequent Sprints.

Requirement Categorization
A Theme is very large requirement
‘Xyz Bank wants to allow customers transact online and be able to do fund transfer, open fixed
deposits, and request check book online.’

An Epic, is very large requirement that can’t be completed in a short iteration (Sprints), and
hence, needs to be broken down into User stories
Xyz Bank wants to allow funds transfer between own accounts in different branch, other
accounts in same bank, and preferably, accounts in other banks.

A User Story is written in perspective of user and how it would help business. It must always
capture AT (Acceptance Test) which should be testable and answer how team would be able to
claim the completion of the story.
Following is an example of a User Story:
‘As a fund transfer application, I want to register accounts for fund transfer for a customer.’
‘As a fund transfer application, I want to transfer amount between customer-owned accounts.’
‘As a customer, I would like to transfer funds and get an SMS on successful transfer.’