Scribd
Upload
59 views

Agile

The document provides an overview of Agile methodology and Scrum framework. Some key points: - Agile is an iterative software development approach using short 1-4 week sprints to deliver working software frequently that is aligned with changing business needs. - The Scrum framework is a common Agile methodology that uses sprints, daily stand-ups, product backlogs and burn-down charts to manage projects. - User stories are written by product owners to define required functionality from the user's perspective in a "As a <user>, I want <feature> so that <benefit>" format. Acceptance criteria specify what makes a story complete.

Uploaded by

Mahenndhiran PD
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
59 views

Agile

The document provides an overview of Agile methodology and Scrum framework. Some key points: - Agile is an iterative software development approach using short 1-4 week sprints to deliver working software frequently that is aligned with changing business needs. - The Scrum framework is a common Agile methodology that uses sprints, daily stand-ups, product backlogs and burn-down charts to manage projects. - User stories are written by product owners to define required functionality from the user's perspective in a "As a <user>, I want <feature> so that <benefit>" format. Acceptance criteria specify what makes a story complete.

Uploaded by

Mahenndhiran PD
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 32

Agile Process

• Agile is a software development methodology


to build a software incrementally using short
iterations of 1 to 4 weeks so that the
development process is aligned with the
changing business needs.
Agile Manifesto and Principles
4 key values
12 Principles of Agile Manifesto
1. Customer Satisfaction - Highest priority is given to satisfy the
requirements of customers through early and continuous
delivery of valuable software.

2. Welcome Change - Changes are inevitable during software


development. Ever-changing requirements should be
welcome, even late in the development phase. Agile processes
should work to increase customers' competitive advantage.

3. Deliver a Working Software - Deliver a working software


frequently, ranging from a few weeks to a few months,
considering shorter time-scale.
12 Principles of Agile Manifesto(cont.)
4. Collaboration - Business people and developers must
work together during the entire life of a project.

5. Motivation - Projects should be built around motivated


individuals. Provide an environment to support
individual team members and trust them so as to make
them feel responsible to get the job done.

6. Face-to-face Conversation - Face-to-face conversation


is the most efficient and effective method of conveying
information to and within a development team.
12 Principles of Agile Manifesto(cont.)
7. Measure the Progress as per the Working
Software - Working software is the key and it
should be the primary measure of progress.

8. Maintain Constant Pace - Agile processes aim


towards sustainable development. The business,
the developers, and the users should be able to
maintain a constant pace with the project.

9. Monitoring - Pay regular attention to technical


excellence and good design to enhance agility.
12 Principles of Agile Manifesto(cont.)
10. Simplicity - Keep things simple and use simple
terms to measure the work that is not completed.

11. Self-organized Teams - An agile team should be


self-organized and should not depend heavily on
other teams because the best architectures,
requirements, and designs emerge from self-
organized teams.
12. Review the Work Regularly - Review the work
done at regular intervals so that the team can
reflect on how to become more effective and adjust
its behavior accordingly.
Why Agile Rocks?
• Speed to market
• Flexibility
• Risk Management
• Cost control
• Quality
• Right Product
• Transparency
Overview of Scrum
• Is an Agile, light weight process.

• Can manage and control software and product


development.

• Use iterative and incremental processes

• Has a simple implementation

• Increases productivity

• Reduce time to benefits.


Role of Scrum Master
Role of Product Owner
Role of Development Team
Cross Functional Team
How an Agile team plan 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. The team uses its
capacity − how many hours are available with team to work on
tasks − to decide how much scope they have to plan.
What is a User story?
• A user story is a requirement which defines what is required
by the user as functionality.

• A user story can be in two forms:


– As a <User Role> I want <Functionality> so that <Business Value>
– In order to <Business value> as a <User Role> I want
<Functionality>

• During release planning, a rough estimate is given to a user


story using relative scale as points.

• During iteration planning, the story is broken down into


tasks.
Acceptance criteria
• Acceptance Criteria are the conditions that a software
product must satisfy to be accepted by a user, customer, or in
the case of system level functionality, the consuming system.

• Every user story has Acceptance Criteria.


• Point
– A Point defines how much a team can commit to
implement the story. A point usually refers to 8
hours. Each story is estimated in points. Can also be
represented in sizes like – small, medium, large, XL.

• Capacity
– Capacity defines how much an individual can
commit. Capacity is estimated in hours.

• Product Backlog
– A product backlog is a list of items to be done.
Items are ranked with feature descriptions.
• Velocity
The total number of completed story points is the team’s
velocity or work output.

• The average velocity is the total number of story points


completed, divided by the total number of iterations
completed.

• Example:
– Iteration 1 = 15 points
– Iteration 2 = 19 points
– Iteration 3 = 21 points
– Iteration 4 = 25 points
– total number of story points completed is 80
-- average velocity is 20 to 80 story points divided by four iterations.
Overview of Scrum
Product Backlog
Sprint Planning Meeting
Sprint Backlog
• Sprint
– In product development, a sprint is a set period of
time during which specific work has to be
completed and made ready for review.(2 – 3
weeks)
– similar to iteration.
– Each sprint begins with the daily scrum meeting.
Daily Scrum Meeting
• Parameters
– Daily
– 15-minutes
– Stand-up
– Not for problem solving
• Three questions:
1. What did you do
yesterday?
2. What will you do today?
3. What obstacles are in your
way?
• Chickens and pigs are invited
– Help avoid other
unnecessary meetings
• Only pigs can talk
• Burn down Charts
• Visual representations of the progress within a sprint
and within the project as a whole.
• Burndown reports track the number of points
completed and are used for monitoring single
iterations, releases, and the entire project backlog.
Sprint Review Meeting

You might also like