The document provides an introduction to Agile methodologies, focusing on the principles of incremental and iterative software development as highlighted in the Agile Manifesto. It outlines various Agile methods, particularly Scrum, detailing its lifecycle, ceremonies, and team roles. Key Agile principles emphasize collaboration, customer interaction, and flexibility over rigid processes.

1. Introduction to Agile

2. Page 2Classification: Restricted
Agenda
• Agile Approach
• What is Agile?
• What does the Agile Manifesto Mean?
• Principles of Agile
• Central: Incremental and Iterative Development
• Agile Methods
• Scrum Lifecycle
• SCRUM team
• Agile Methods – Scrum

3. Page 3Classification: Restricted
Agile Approach

4. Page 4Classification: Restricted
XP
Concept :
Coding
Testing
Listening
Designing
• Light-weight: discipline without bureaucracy
• Under stress, people do what is easiest
• All XP practices have short-term benefits as well as long-term benefits
• Development as a Conversation
• The code is the documentation

5. Page 5Classification: Restricted
What is Agile
 Processes and techniques for incremental and iterative software
development
 Agile Manifesto
 – “We are uncovering better ways of developing software by doing it
and helping others do it. Through this work we have come to value”:
 Individuals and interactions over processes and tools
 Working software over comprehensive documentation
 Customer collaboration over contract negotiation
 Responding to change over following a plan

6. Page 6Classification: Restricted
What does the Agile Manifesto Mean?

7. Page 7Classification: Restricted
Principles of Agile

8. Page 8Classification: Restricted
Principles of Agile (2)

9. Page 9Classification: Restricted
Central: Incremental and Iterative
Development

10. Page 10Classification: Restricted
Agile Methods

11. Page 11Classification: Restricted
Scrum Lifecycle
 Planning
–Vision, expectations, funding
 Staging
– Identify requirements, prioritize iteration
 Development
– Implement system ready for release in each sprint
 Release
–Operational deployment

12. Page 12Classification: Restricted
Development team
product owner
scrum master
SCRUM team

13. Page 13Classification: Restricted
Agile Methods – Scrum (1)

14. Page 14Classification: Restricted
Scrum Ceremonies
1.SPRINT PLANNING
(Discuss top PBI scope>estimate)
2. Daily stand up meeting
(<15 minutes, what I did till this meeting, what ill do till next meeting ,
what's blocking me)
3. Sprint review (last day)
(To demonstrate what is ready to ship to po, no ppt, demo on prodn
env
4. Sprint retrospective –
what went right, what went wrong

15. Page 15Classification: Restricted
Agile Methods – Scrum (2)

16. Page 16Classification: Restricted
Product Backlog
PBIs are Uniquely ranked items, progressive
user stories are short plain language of description of functionality in
terms of customer benefit/need
Stories (=requirement) priority estima
te
As a user I want to be able to easily install
the application so that I can access my
bank account on my mobile
1 5
As a user I want to be able to view my bank
transaction history so that I can track my
transactions
2 3

17. Page 17Classification: Restricted
Agile Methods – Scrum (3)

18. Page 18Classification: Restricted
Agile Methods – Scrum (3)
Commitment
– Team takes responsibility to complete the Sprint. To avoid things that
will stand in its way
Focus
– Team’s focus is maintained. Distractions, interruptions are fielded
Openness
– Overall and individual status and commitments kept open.
Respect
– Team responsibility rather than scapegoat.
Courage
– Management and team have the courage to take responsibility to do
what is necessary

19. Page 19Classification: Restricted
Thank you