Agile methodologies overview -Presentation by Sangram Behera Includes Basic knowledge how agile works

1. Agile Methodologies-Overview
Presentation by
Sangram Behera
Sangram.behera@capgemini.com
6/10/2016

2. Table of Contents
• What is Agile
• Agile Framework(Scrum)
• Role,Ceremonies,Artifacts
• Agile Manifesto
• Benefits of Agile
• Difference between Waterfall Vs Agile
6/10/2016

3. What is Agile
•Agile appears as a “solution” to the disadvantages of the waterfall methodology.
Instead of a sequential design process, the Agile methodology follows an incremental
approach.
•Developers start off with a simplistic project design, and then begin to work on small
modules. The work on these modules is done in weekly or monthly sprints, and at the
end of each sprint, project priorities are evaluated and tests are run.
The sprints allow for bugs to be discovered and fixed before next sprint.
•Demo at end of Each Sprint helps to collect customer feedback and incorporated into
the design before the next sprint is run.
•Agile development is a method of building software by empowering and trusting
people, acknowledging change as norm, and promoting constant feedback.
6/10/2016

4. Agile Framework-Scrum
Scrum is a simple inspect and adapt framework that has Three Roles, Four Ceremonies
and Three Artifacts to design to deliver in sprints usually 2-4 week iterations.
Role
– Product owner
– Scrum Master
– Team
Ceremonies
– Sprint Planning
– Daily Scrum Call
– Sprint Review
– Sprint Retrospective
Artifacts
– Product Backlog
– Sprint backlog
– Burn down charts
6/10/2016

5. Roles :What who does ?
Product owner
Define the features of the product
Decide on release date and content
Only Product Owner authorize to Cancel a Sprint
Prioritize features according to market value
Adjust features and priority every iteration, as needed
Accept or reject work results
Scrum Master
Serving the team
facilitate the team’s group interactions, to help the team achieve its full
potential
helps remove blocks that are surfaced by team members
Protecting the team
protects the team from outside interference or disruption
may need to raise uncomfortable issues within the team
Supporting the team’s use of Scrum
organizes and facilitates Scrum-related practices
serves as the Scrum “conscience” of the team, reminding the team of standard
Scrum practices
Team
Typically 5-9 people
Cross-functional:
Programmer, tester, user experience designers, etc.
6/10/2016

6. Ceremonies
Sprint Planning
Commit to certain functionality & estimate
Produces Sprint Backlog
Time-boxed to a maximum of eight hours
for a one-month Sprint
Daily Scrum (15 minutes daily)
What have you done since last Scrum?
What will do before next Scrum?
What obstacles?
Analysis,Design,Bulid,Test
2-4 weeks of iterations
(Not more than 1 month)
Sprint Review (2- 4 hrs)
Demo to Product owner and stake holders ,
Business users
Accept changes
Sprint Retrospective(1- 3 hrs)
What went well during the Sprint?
What could be improved for the
next(Start/Stop/Continue)
6/10/2016

7. Artifacts-JIRA
•Product Backlog
•Sprint Backlog
•Burn down Chart
6/10/2016

8. Agile Manifesto
6/10/2016

9. Benefits of Agile
•Quicker ROI
•Lower Total Cost
•Respond to Change
•Reduce Risk
•Faster time to Market
•Stakeholder Relation
6/10/2016

10. Waterfall Vs Agile
•Phased
•Working Software in Final stage
•Different people involved in different phases
Communication over head and uses low
Quality communication channels
•Verification done at Final stage
•Predictive Planning
•Less Visibility, artifacts, Prototypes
•Changes accepts at certain stage only
Waterfall
•Iterative and Incremental
•Working software every build
•Same set of people-less overhead and uses
high quality communication channels
•Verifiability Driven
•Adaptive Planning
•More visibility –Working software
•Changes embraced
Agile
6/10/2016

11. Thank you
None of us is as smart as all of us -
Agile Development ultimately a whole Team effort
6/10/2016 Prepared by Sangram Behera