Agile is an iterative approach to project management and software development that helps teams deliver value to their customers faster and with fewer headaches. ... Requirements, plans, and results are evaluated continuously so teams have a natural mechanism for responding to change quickly.
3. Agile Methodology
Agile is a software development methodology to
build a software incrementally using short
iterations of 1 to 4 weeks so that the development
is aligned with the changing business needs. This
simple tutorial uses appropriate examples to help
you understand agile development in a general
and quick way.
3
6. Roles in AGile
1. Team Lead, Scrum Master (Scrum), Team Coach, or Project Lead
2. Team Member
3. Product Owner
6
7. 1. Scrum Master
A Scrum Master is a team leader and facilitator who helps the
team members to follow agile practices so that they can meet
their commitments.
1. To enable close co-operation between
all roles and functions.
2. To remove any blocks.
3. To shield the team from any
disturbances.
4. To work with the organization to track
the progress and processes of the
company.
7
1. Daily stand-ups,
2. Planned meetings,
3. Demo,
4. Review,
5. Retrospective Meetings, and
6. To facilitate team meetings and
decision-making process.
8. 2. Product Owner
A Product Owner is the one who drives the product from business
perspective.
1. To define the requirements and
prioritize their values.
2. To determine the release date and
contents.
3. To take an active role in iteration
planning and release planning meetings.
8
1. To ensure that team is working on the
most valued requirement.
2. To represent the voice of the customer.
3. To accept the user stories that meet the
definition of done and defined
acceptance criteria.
9. Cross-functional Team
Every agile team should be a self-
sufficient team with 5 to 9 team
members and an average
experience ranging from of 6 to
10 years. Typically, an agile team
comprises of 3 to 4 developers, 1
tester, 1 technical lead, 1 product
owner and 1 scrum master.
9
10. How an Agile Team Plans its Work?
An Agile team works in iterations to deliver user stories where each iteration is of 10
to 15 days. Each user story is planned based on its backlog prioritization and size.
10
11. What is a User Story?
1. A user story is a requirement which defines what is required by
the user as functionality. A user story can be in two forms −
1. As a <User Role> I want <Functionality> so that <Business
Value>
2. In order to <Business value> as a <User Role> I want
<Functionality>
11
12. Importance of User Story
1. User story talks about what is to
be done. It defines what a user
needs.
2. Task talks about how it is to be
done. It defines how a
functionality is to be
implemented.
3. Stories are implemented by tasks.
Each story is a collection of tasks.
1. User story is divided into tasks
when it is planned in current
iteration.
2. Tasks are estimated in hours,
typically from 2 to 12 hours.
3. Stories are validated using
acceptance tests.
12
13. 12 Principles of Agile
1. Customer
Satisfaction
2. Welcome Change
3. Deliver a
Working
Software
4. Collaboration
1. Motivation
2. Face-to-face
Conversation
3. Measure the
Progress as per
the Working
Software
4. Maintain
Constant Pace
1. Monitoring
2. Simplicity
3. Self-organized
Teams
4. Review the Work
Regularly
13
14. What is Daily Stand-up?
1. A daily stand-up is a daily status meeting among all
team members and it is held roughly for 15 minutes.
2. Every member has to answer three important
questions −
1. What I did yesterday?
2. What I'll do today?
3. Any impediment I am facing.../ I am blocked due
to...
14
15. Iteration & Release
1. An Iteration is a time boxed
collection of user stories /
defects to be worked upon
and accepted within the
release of a product.An
iteration is also termed as
a sprint.
1. A Release is a major
milestone that represents
an internal or external
delivery of working, tested
version of the
product/system.
15