Though the basics of "What is Agile/Why Agile" to introduce the concepts to those Who are new to Agile, the Traditional SDLC Scenarios and How Agile address them through the 4 values convince the need for Agile.

1. Agile, A Different Way To Build Software Products
Webinar on 25-May-2020,
Presented By
Ramadevi Lakshmanan, Senior Agile Coach

2. SDLC & Models
Requirement
Analysis
Build
Test
Deployment
High Level
Design
Low Level
Design
Water Falls
“Software Development Life Cycle (SDLC) is a process used by Information Technology
industry to design, develop and deliver software products”
“The SDLC aims to produce a high-quality software meeting customer expectations but
within the budget / cost estimates and complete on time. So, it is CTQ which matters”

3. The State of Software Products

4. Can we look into some “Live” scenarios
from these traditional SDLC approaches?
https://wallpaper-house.com/data/out/12/wallpaper2you_495940.jpg

5. Traditional SDLC Scenario 1
No..No.
We are supposed to be complaint
to the process and we are
expected to design first and then
write the program.
I have prepared the technical design only
after the coding. Do we really need to
keep documenting it? I find no use of it.
Agile gives importance to “Individuals and Interactions” than “Processes
and Tools”. It follows Empirical Process approach.
https://www.uihere.com/free-cliparts/silhouette-cartoon-download-flat-design-vector-business-people-talking-991839

6. Our project is halted. Customer
wanted us to deliver whatever
developed so far.
Ahh! Are we going to
deliver only HLD?
Agile gives importance to “Working Software” than “Comprehensive
Documentation”. It delivers business value at the end of each iteration.
Oh No.
Customer is
not going to
be happy
Traditional SDLC Scenario 2
https://www.uihere.com/free-cliparts/silhouette-cartoon-download-flat-design-vector-business-people-talking-991839

7. Agile gives importance to “Customer Collaboration” than “Contract
Negotiation”. Customer is part of Agile team and available throughout.
As per the contract, we deliver
by February 2021 which is 8
months away from now.
Hmmm.
I think I have
chosen the wrong
vendor…
Traditional SDLC Scenario 3
https://www.uihere.com/free-cliparts/silhouette-cartoon-download-flat-design-vector-business-people-talking-991839

8. Oh my God. It is not advisable to make
changes now. We are in coding phase
already. Starting from analysis all over
again ends up with lot of rework.
Customer has come up with so
many changes and new features.
How are we going to incorporate
them into our plan and execution?
Agile gives importance to “Responding to Change” than “Following a
Plan”. In Agile, the software is delivered as small product increments.
SDLC Scenario 1Traditional SDLC Scenario 4
https://www.uihere.com/free-cliparts/silhouette-cartoon-download-flat-design-vector-business-people-talking-991839

9. Quiz Time
• What are the two traditional models we discussed so far?
• How much of the software features were never used?
• Can we match the following?
than
• A Comprehensive documentation
• B Processes and tools
• C Contract negotiation
• D Following a plan
• 1 Individuals and interactions
• 2 Responding to change
• 3 Working software
• 4 Customer collaboration

10. Quiz Answers Time
• What are the two traditional models we discussed so far?
• Water Falls, V-Model
• How much of the software features were never used?
• 45%
• Can we match the following?
than
• A Processes and tools
• B Following a plan
• C Comprehensive documentation
• D Contract negotiation
• 1 Individuals and interactions
• 2 Responding to change
• 3 Working software
• 4 Customer collaboration

11. Iterative
Incremental
Feedback
Collaboration
What is Agile?
@
https://www.youtube.com/watch?v=AsFMHnSfI2I

12. Design Build Test
Design
Build
Test
Water
Falls
Design
Build
Test
Design
Build
Test
Agile
https://wallpapersafari.com/waterfall-desktop-wallpaper-free-download/
Parallel
Sequential

13. S.No. Agile Framework Scaling Agile Framework
1 Scrum SAFe (Scaled Agile Framework)
2 Agile Modeling LeSS (Large Scale Scrum)
3 AUP (Agile Unified Process) DaD (Distributed Agile Delivery)
4 Kanban Spotify
5 DSDM (Dynamic Systems Development Method) Nexus
6 XP (Extreme Programming)
7 FDD (Feature Driven Development)
8 Lean Software Development
9 ASD (Adaptive Software Development)
10 Scrumban
11 RAD (Rapid Application Development)
“Agile Software Development is culturally different way of building product increments in short iterations
with frequent inspection and adaptation”
“The cross functional team collaborates in a co-located environment to develop and deliver together by
becoming self-organized”
“Any S/W development approach which embeds Agile Manifesto in it, is called Agile Framework”
Agile & Frameworks

14. Scrum

15. kisspng-kanban-board-scaled-agile-framework-agile-software-process-flow-diagram-kanban-choice-image-how-to-5b673e66361a48.9194600915334928382216.png
Kanban

16. http://www.programmersought.com/article/7160380372/
Spotify

17. SAFe

18. https://stateofagile.com/#ufh-c-473508-state-of-agile-report

19. If no questions, Thank you all for your Time!
Continuous Learning & Sharing Knowledge is
my passion. And, The message for today is
“Let us be socially responsible”