Presentation (animated) on Agilve vs Iterative vs Waterfall models in SDLC.
Detailed comparison across Process, Planning, Execution and Completion.
#Cricket Analogy#
Waterfall (Test Match) vs Iterative (ODI) Format vs Agile (T20)
#Waterfall: Test Match Format - Strategic-Phase by Phase like Innings by Innings.
Game for Specialists, Slow and Steady.
#One Day (ODI) Format : Strategic approach – First10/Middle/Slog overs.
Mix of Specialists and
All-Rounders, Result oriented.
#T20 Format: Lively,Dynamic, Full of Action. Game for All-Rounders. Changes with every over.
Highly Result oriented
Agile management, or agile process management, or simply agile refers to an iterative, incremental method of managing the design and build activities of engineering, information technology and other business areas that aim to provide new product or service development in a highly flexible and interactive manner; an example is its application in Scrum, an original form of agile software development.
Agile management, or agile process management, or simply agile refers to an iterative, incremental method of managing the design and build activities of engineering, information technology and other business areas that aim to provide new product or service development in a highly flexible and interactive manner; an example is its application in Scrum, an original form of agile software development.
Ever wondered how Agile can be implemented in larger organisation/project. SAFe is the answer. In this session we will understand the core principles and values that is require to implement SAFe in larger organisation.
This is a short introduction to the practice of Sprint Planning in Scrum. It would be useful for people new to Scrum or Agile. For more, comment or write to read my blog : http://agilediary.wordpress.com/
Iterative model.
Spiral model
RAD(Rapid application development)
model.
Iterative model.
Spiral model
RAD(Rapid application development)
model.
A Water Fall Model is easy to flow.
It can be implemented for any size of project.
Every stage has to be done separately at the right time so you cannot jump stages.
Documentation is produced at every stage of a waterfall model allowing people to understand what has been done.
Testing is done at every stage.
This model was not the first model to discuss iterative development.
As originally envisioned, the iterations were typically 6 months to 2 years long.
Each phase starts with a design goal and ends with the client (who may be internal) reviewing the progress thus far.
Analysis and engineering efforts are applied at each phase of the project, with an eye toward the end goal of the project.
This model was not the first model to discuss iterative development.
As originally envisioned, the iterations were typically 6 months to 2 years long.
Each phase starts with a design goal and ends with the client (who may be internal) reviewing the progress thus far.
Analysis and engineering efforts are applied at each phase of the project, with an eye toward the end goal of the project.
This model was not the first model to discuss iterative development.
As originally envisioned, the iterations were typically 6 months to 2 years long.
Each phase starts with a design goal and ends with the client (who may be internal) reviewing the progress thus far.
Analysis and engineering efforts are applied at each phase of the project, with an eye toward the end goal of the project.
This approach carries less risk than a traditional Waterfall approach but is still far more risky and less efficient than a more Agile approaches.
In Iterative model, iterative process starts with a simple implementation of a small set of the software requirements and iteratively enhances the evolving versions until the complete system is implemented and ready to be deployed.
Iterative model.
Spiral model
RAD(Rapid application development)
model.
The first formal description of the waterfall model is often cited as a 1970 article by Winston W. Royce
Royce did not use the term "waterfall" in this article.
Royce presented this model as an example of a flawed, non-working model.
Modernize project controls to ensure project success aecomAconex
Kim McAvoy from AECOM and Garrett Fultz from FTI Consulting share how consistent results can be attained by implementing modern systems on projects, and throughout organizations. New tools provide visibility into potential cost and schedule impacts. Use data and insights to deliver successful projects from controls systems to help you make the right decisions at the right time.
Ever wondered how Agile can be implemented in larger organisation/project. SAFe is the answer. In this session we will understand the core principles and values that is require to implement SAFe in larger organisation.
This is a short introduction to the practice of Sprint Planning in Scrum. It would be useful for people new to Scrum or Agile. For more, comment or write to read my blog : http://agilediary.wordpress.com/
Iterative model.
Spiral model
RAD(Rapid application development)
model.
Iterative model.
Spiral model
RAD(Rapid application development)
model.
A Water Fall Model is easy to flow.
It can be implemented for any size of project.
Every stage has to be done separately at the right time so you cannot jump stages.
Documentation is produced at every stage of a waterfall model allowing people to understand what has been done.
Testing is done at every stage.
This model was not the first model to discuss iterative development.
As originally envisioned, the iterations were typically 6 months to 2 years long.
Each phase starts with a design goal and ends with the client (who may be internal) reviewing the progress thus far.
Analysis and engineering efforts are applied at each phase of the project, with an eye toward the end goal of the project.
This model was not the first model to discuss iterative development.
As originally envisioned, the iterations were typically 6 months to 2 years long.
Each phase starts with a design goal and ends with the client (who may be internal) reviewing the progress thus far.
Analysis and engineering efforts are applied at each phase of the project, with an eye toward the end goal of the project.
This model was not the first model to discuss iterative development.
As originally envisioned, the iterations were typically 6 months to 2 years long.
Each phase starts with a design goal and ends with the client (who may be internal) reviewing the progress thus far.
Analysis and engineering efforts are applied at each phase of the project, with an eye toward the end goal of the project.
This approach carries less risk than a traditional Waterfall approach but is still far more risky and less efficient than a more Agile approaches.
In Iterative model, iterative process starts with a simple implementation of a small set of the software requirements and iteratively enhances the evolving versions until the complete system is implemented and ready to be deployed.
Iterative model.
Spiral model
RAD(Rapid application development)
model.
The first formal description of the waterfall model is often cited as a 1970 article by Winston W. Royce
Royce did not use the term "waterfall" in this article.
Royce presented this model as an example of a flawed, non-working model.
Modernize project controls to ensure project success aecomAconex
Kim McAvoy from AECOM and Garrett Fultz from FTI Consulting share how consistent results can be attained by implementing modern systems on projects, and throughout organizations. New tools provide visibility into potential cost and schedule impacts. Use data and insights to deliver successful projects from controls systems to help you make the right decisions at the right time.
Agile and Waterfall are two distinct methods of project management.
The Waterfall model can essentially be described as a linear model of project development. Like its name suggests, waterfall employs a sequential process. Development flows sequentially from start point to end point, with several different stages: Conception, Initiation, Analysis, Design, Construction, Testing, Implementation, and Maintenance.
In contrast, the Agile method proposes an incremental and iterative approach to project development. It was essentially developed in response to the limitations of Waterfall, as a way to give more freedom. The process is broken into individual models that team work on. There is no pre-determined course of action or plan with the Agile method. Rather, team-mates are free to respond to changes in requirements as they arise and make changes as the project progresses. Agile is a pretty new player to the development management. However, it has made substantial gains in use and popularity in the last couple of years.
The basics of Agile and Waterfall Project management methodologies. Description when each approach can be applied.
Advices How to create a Product backlog and how to colect requirements. Sprint planning, Burndown chart, Demonstration, Retrospective, Tasks board examples.
Digital Transformation: What it is and how to get thereEconsultancy
Digital Transformation: What it is and how to get there.
Authored by Econsultancy CEO Ashley Friedlein, this presentation on the topic of 'Digital Transformation', is broken down into six sections covering:
1. Digital Transformation - what it is and recent data and research on the topic
2. Strategy - what a digital strategy should include
3. Technology - the challenges of technology and the skills gap
4. People - looking at organisational structure, culture, roles & responsibilities, environment recquired
5. Process - how to address the speed, innovation and agility required
6. Business Transformation - how digital transformation is actually business transformation
Building Quality In in SAFe – The Testing Organization’s Perspective Yuval Yeret
SAFe emphasizes Building Quality In. We will take a deep dive into how this looks from a testing organization’s perspective and what does a SAFe implementation mean for Testing/QA professionals. We will map SAFe’s approach to best practices in the “”Agile Testing”” world. We will look at examples from the real world of how traditional testing organizations shift left and evolve towards continuous testing.
Learning Objectives and Key Takeaways:
Understand how best practices from the “”Agile Testing”” world map to SAFe’s context
Learn ideas and patterns for evolving Testing/QA’s role during a SAFe implementation
Understand how Test-Driven looks like and how techniques like Acceptance-Test-Driven-Design/Behavior-Driven
Development can empower testers as well as improve the flow on SAFe agile teams.
See how SAFe’s principles can be used to guide the evolution towards a lean/agile testing organization
STX Next - Scrum Development Process OverviewSTX Next
An overview of Software Development Process at STX Next presenting basic SCRUM ceremonies and workflows. To learn more about STX Next visit https://stxnext.com
Agile Testing Leadership Lessons for the Test & QA Professionals
Silicon India Software Testing Conference - SOFTEC - 2 July 2011
Bangalore
Presentation from Speaker: Vaidyanathan Ramalingam,
Director Engineering (Test), Huawei Technologies R&D, Bangalore
Coverage:
1) Waterfall Testing Vs Agile Testing
2) Testing Checklist - 5W & 2H
3) Trade Off Economics in Testing
4) Software Testing Eco System
5) RCA (Root Cause Analysis)
Cotact: rvaidya67@hotmail.com
Linked-In: Vaidyanathan Ramalingam
Agile Testing Leadership Lessons for the Test & QA Professionals
Silicon India Software Testing Conference - SOFTEC - 2 July 2011
Bangalore
Presentation from Speaker: Vaidyanathan Ramalingam,
Director Engineering (Test), Huawei Technologies R&D, Bangalore
Coverage:
1) Waterfall Testing Vs Agile Testing
2) Testing Checklist - 5W & 2H
3) Trade Off Economics in Testing
4) Software Testing Eco System
5) RCA (Root Cause Analysis)
Agile Testing Leadership Lessons for the Test & QA Professionals
Silicon India Software Testing Conference - SOFTEC - 2 July 2011
Bangalore
Presentation from Speaker: Vaidyanathan Ramalingam,
Director Engineering (Test), Huawei Technologies R&D, Bangalore
Coverage:
1) Waterfall Testing Vs Agile Testing
2) Testing Checklist - 5W & 2H
3) Trade Off Economics in Testing
4) Software Testing Eco System
5) RCA (Root Cause Analysis)
Agile Testing Leadership Lessons for the Test & QA Professionals
Silicon India Software Testing Conference - SOFTEC - 2 July 2011
Bangalore
Presentation from Speaker: Vaidyanathan Ramalingam,
Director Engineering (Test), Huawei Technologies R&D, Bangalore
Coverage:
1) Waterfall Testing Vs Agile Testing
2) Testing Checklist - 5W & 2H
3) Trade Off Economics in Testing
4) Software Testing Eco System
5) RCA (Root Cause Analysis)
Cotact: rvaidya67@hotmail.com
Linked-In: Vaidyanathan Ramalingam
Agile Testing Leadership Lessons for the Test & QA Professionals
Silicon India Software Testing Conference - SOFTEC - 2 July 2011
Bangalore
Presentation from Speaker: Vaidyanathan Ramalingam,
Director Engineering (Test), Huawei Technologies R&D, Bangalore
Coverage:
1) Waterfall Testing Vs Agile Testing
2) Testing Checklist - 5W & 2H
3) Trade Off Economics in Testing
4) Software Testing Eco System
5) RCA (Root Cause Analysis)
Agile Testing Leadership Lessons for the Test & QA Professionals
Silicon India Software Testing Conference - SOFTEC - 2 July 2011
Bangalore
Presentation from Speaker: Vaidyanathan Ramalingam,
Director Engineering (Test), Huawei Technologies R&D, Bangalore
Coverage:
1) Waterfall Testing Vs Agile Testing
2) Testing Checklist - 5W & 2H
3) Trade Off Economics in Testing
4) Software Testing Eco System
5) RCA (Root Cause Analysis)
Agile Testing Leadership Lessons for the Test & QA Professionals
Silicon India Software Testing Conference - SOFTEC - 2 July 2011
Bangalore
Presentation from Speaker: Vaidyanathan Ramalingam,
Director Engineering (Test), Huawei Technologies R&D, Bangalore
Coverage:
1) Waterfall Testing Vs Agile Testing
2) Testing Checklist - 5W & 2H
3) Trade Off Economics in Testing
4) Software Testing Eco System
5) RCA (Root Cause Analysis)
Cotact: rvaidya67@hotmail.com
Linked-In: Vaidyanathan Ramalingam
Agile Testing Leadership Lessons for the Test & QA Professionals
Silicon India Software Testing Conference - SOFTEC - 2 July 2011
Bangalore
Presentation from Speaker: Vaidyanathan Ramalingam,
Director Engineering (Test), Huawei Technologies R&D, Bangalore
Coverage:
1) Waterfall Testing Vs Agile Testing
2) Testing Checklist - 5W & 2H
3) Trade Off Economics in Testing
4) Software Testing Eco System
5) RCA (Root Cause Analysis)
Agile Testing Leadership Lessons for the Test & QA Professionals
Silicon India Software Testing Conference - SOFTEC - 2 July 2011
Bangalore
Presentation from Speaker: Vaidyanathan Ramalingam,
Director Engineering (Test), Huawei Technologies R&D, Bangalore
Coverage:
1) Waterfall Testing Vs Agile Testing
2) Testing Checklist - 5W & 2H
3) Trade Off Economics in Testing
4) Software Testing Eco System
5) RCA (Root Cause Analysis)
Similar to Agile vs Iterative vs Waterfall models (20)
A Comprehensive Look at Generative AI in Retail App Testing.pdfkalichargn70th171
Traditional software testing methods are being challenged in retail, where customer expectations and technological advancements continually shape the landscape. Enter generative AI—a transformative subset of artificial intelligence technologies poised to revolutionize software testing.
Multiple Your Crypto Portfolio with the Innovative Features of Advanced Crypt...Hivelance Technology
Cryptocurrency trading bots are computer programs designed to automate buying, selling, and managing cryptocurrency transactions. These bots utilize advanced algorithms and machine learning techniques to analyze market data, identify trading opportunities, and execute trades on behalf of their users. By automating the decision-making process, crypto trading bots can react to market changes faster than human traders
Hivelance, a leading provider of cryptocurrency trading bot development services, stands out as the premier choice for crypto traders and developers. Hivelance boasts a team of seasoned cryptocurrency experts and software engineers who deeply understand the crypto market and the latest trends in automated trading, Hivelance leverages the latest technologies and tools in the industry, including advanced AI and machine learning algorithms, to create highly efficient and adaptable crypto trading bots
Globus Compute wth IRI Workflows - GlobusWorld 2024Globus
As part of the DOE Integrated Research Infrastructure (IRI) program, NERSC at Lawrence Berkeley National Lab and ALCF at Argonne National Lab are working closely with General Atomics on accelerating the computing requirements of the DIII-D experiment. As part of the work the team is investigating ways to speedup the time to solution for many different parts of the DIII-D workflow including how they run jobs on HPC systems. One of these routes is looking at Globus Compute as a way to replace the current method for managing tasks and we describe a brief proof of concept showing how Globus Compute could help to schedule jobs and be a tool to connect compute at different facilities.
Globus Connect Server Deep Dive - GlobusWorld 2024Globus
We explore the Globus Connect Server (GCS) architecture and experiment with advanced configuration options and use cases. This content is targeted at system administrators who are familiar with GCS and currently operate—or are planning to operate—broader deployments at their institution.
OpenFOAM solver for Helmholtz equation, helmholtzFoam / helmholtzBubbleFoamtakuyayamamoto1800
In this slide, we show the simulation example and the way to compile this solver.
In this solver, the Helmholtz equation can be solved by helmholtzFoam. Also, the Helmholtz equation with uniformly dispersed bubbles can be simulated by helmholtzBubbleFoam.
Providing Globus Services to Users of JASMIN for Environmental Data AnalysisGlobus
JASMIN is the UK’s high-performance data analysis platform for environmental science, operated by STFC on behalf of the UK Natural Environment Research Council (NERC). In addition to its role in hosting the CEDA Archive (NERC’s long-term repository for climate, atmospheric science & Earth observation data in the UK), JASMIN provides a collaborative platform to a community of around 2,000 scientists in the UK and beyond, providing nearly 400 environmental science projects with working space, compute resources and tools to facilitate their work. High-performance data transfer into and out of JASMIN has always been a key feature, with many scientists bringing model outputs from supercomputers elsewhere in the UK, to analyse against observational or other model data in the CEDA Archive. A growing number of JASMIN users are now realising the benefits of using the Globus service to provide reliable and efficient data movement and other tasks in this and other contexts. Further use cases involve long-distance (intercontinental) transfers to and from JASMIN, and collecting results from a mobile atmospheric radar system, pushing data to JASMIN via a lightweight Globus deployment. We provide details of how Globus fits into our current infrastructure, our experience of the recent migration to GCSv5.4, and of our interest in developing use of the wider ecosystem of Globus services for the benefit of our user community.
Modern design is crucial in today's digital environment, and this is especially true for SharePoint intranets. The design of these digital hubs is critical to user engagement and productivity enhancement. They are the cornerstone of internal collaboration and interaction within enterprises.
Code reviews are vital for ensuring good code quality. They serve as one of our last lines of defense against bugs and subpar code reaching production.
Yet, they often turn into annoying tasks riddled with frustration, hostility, unclear feedback and lack of standards. How can we improve this crucial process?
In this session we will cover:
- The Art of Effective Code Reviews
- Streamlining the Review Process
- Elevating Reviews with Automated Tools
By the end of this presentation, you'll have the knowledge on how to organize and improve your code review proces
We describe the deployment and use of Globus Compute for remote computation. This content is aimed at researchers who wish to compute on remote resources using a unified programming interface, as well as system administrators who will deploy and operate Globus Compute services on their research computing infrastructure.
Cyaniclab : Software Development Agency Portfolio.pdfCyanic lab
CyanicLab, an offshore custom software development company based in Sweden,India, Finland, is your go-to partner for startup development and innovative web design solutions. Our expert team specializes in crafting cutting-edge software tailored to meet the unique needs of startups and established enterprises alike. From conceptualization to execution, we offer comprehensive services including web and mobile app development, UI/UX design, and ongoing software maintenance. Ready to elevate your business? Contact CyanicLab today and let us propel your vision to success with our top-notch IT solutions.
Accelerate Enterprise Software Engineering with PlatformlessWSO2
Key takeaways:
Challenges of building platforms and the benefits of platformless.
Key principles of platformless, including API-first, cloud-native middleware, platform engineering, and developer experience.
How Choreo enables the platformless experience.
How key concepts like application architecture, domain-driven design, zero trust, and cell-based architecture are inherently a part of Choreo.
Demo of an end-to-end app built and deployed on Choreo.
Gamify Your Mind; The Secret Sauce to Delivering Success, Continuously Improv...Shahin Sheidaei
Games are powerful teaching tools, fostering hands-on engagement and fun. But they require careful consideration to succeed. Join me to explore factors in running and selecting games, ensuring they serve as effective teaching tools. Learn to maintain focus on learning objectives while playing, and how to measure the ROI of gaming in education. Discover strategies for pitching gaming to leadership. This session offers insights, tips, and examples for coaches, team leads, and enterprise leaders seeking to teach from simple to complex concepts.
How Recreation Management Software Can Streamline Your Operations.pptxwottaspaceseo
Recreation management software streamlines operations by automating key tasks such as scheduling, registration, and payment processing, reducing manual workload and errors. It provides centralized management of facilities, classes, and events, ensuring efficient resource allocation and facility usage. The software offers user-friendly online portals for easy access to bookings and program information, enhancing customer experience. Real-time reporting and data analytics deliver insights into attendance and preferences, aiding in strategic decision-making. Additionally, effective communication tools keep participants and staff informed with timely updates. Overall, recreation management software enhances efficiency, improves service delivery, and boosts customer satisfaction.
Developing Distributed High-performance Computing Capabilities of an Open Sci...Globus
COVID-19 had an unprecedented impact on scientific collaboration. The pandemic and its broad response from the scientific community has forged new relationships among public health practitioners, mathematical modelers, and scientific computing specialists, while revealing critical gaps in exploiting advanced computing systems to support urgent decision making. Informed by our team’s work in applying high-performance computing in support of public health decision makers during the COVID-19 pandemic, we present how Globus technologies are enabling the development of an open science platform for robust epidemic analysis, with the goal of collaborative, secure, distributed, on-demand, and fast time-to-solution analyses to support public health.
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I ...Juraj Vysvader
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I didn't get rich from it but it did have 63K downloads (powered possible tens of thousands of websites).
Why React Native as a Strategic Advantage for Startup Innovation.pdfayushiqss
Do you know that React Native is being increasingly adopted by startups as well as big companies in the mobile app development industry? Big names like Facebook, Instagram, and Pinterest have already integrated this robust open-source framework.
In fact, according to a report by Statista, the number of React Native developers has been steadily increasing over the years, reaching an estimated 1.9 million by the end of 2024. This means that the demand for this framework in the job market has been growing making it a valuable skill.
But what makes React Native so popular for mobile application development? It offers excellent cross-platform capabilities among other benefits. This way, with React Native, developers can write code once and run it on both iOS and Android devices thus saving time and resources leading to shorter development cycles hence faster time-to-market for your app.
Let’s take the example of a startup, which wanted to release their app on both iOS and Android at once. Through the use of React Native they managed to create an app and bring it into the market within a very short period. This helped them gain an advantage over their competitors because they had access to a large user base who were able to generate revenue quickly for them.
3. ITERATIVE Model
1Code
1 Test
2Code
2 Test
3Code
3 Test
1A 2A 3A 4A 5A
1D 2D 3D 4D 5D
4Code
4 Test
5Code
5 Test
ANALYSIS
DESIGN
C
O
N
S
T
R
U
C
T
I
O
N
A
D
c
T
Iterative Model
For a small set of functionality
Analysis & Design will be
completed first before
proceeding to Coding & Testing
within same iteration.
Project Time line
25% 50% 75% 100%
6. 6
Process vs Project Triangle
ADC
A
D
C
T
A
D
C
TT
Schedule Schedule Schedule
WATER FALL ITERATIVE AGILE - SCRUM
Waterfall Iterative Agile
Format Test Match: Strategic-
Phase by Phase like
Innings by Innings.
Game for Specialists.
Slow and Steady.
One Day: Strategic approach –
First10/Middle/Slog overs.
Mix of Specialists and
All-Rounders.
Result oriented.
T20: Lively , Dynamic, Full of
Action. Game for All-Rounders.
Changes with every over.
Highly Result oriented
7. Agile vs Iterative vs Waterfall
{Process}
{Planning}
{Execution}
{Completion}
8. 8
Agile vs Iterative vs Waterfall – {Process}
Waterfall Iterative (hybrid) Agile
Quality Quality focus changes
from Analysis > Design
> Code > Test
Quality focus shifts
between Analysis/Design
phase to Coding/Testing
phase
Quality focus on all aspects
of SDLC at any given time.
Quality Control Detection & fixing
during system and
regression testing at the
last phase of project.
Early detection & fixing in
each iteration for new
features. Followed by
regression testing.
Early detection & fixing in
each sprint followed by
stabilization.
Continual
Improvement
(CA & PA)
Lessons learned from
previous release
implemented in next
release
Lessons learned from
previous Iteration
implemented in next
Iteration.
Lessons learned from
previous sprint implemented
in next sprint
Risk No Risk Identification.
Firefighting during
testing phase.
Risk identification &
mitigation in dev & test
phase of each iteration.
Early identification &
mitigation in every sprint.
Postmortem/
Retrospection
After every release After every iteration/
milestone
After every sprint in
retrospection meeting
Customer
Feed back
At the end of the
project.
At the end of every
iteration
At the end of every sprint 4
Less Agile
More Agile
9. 9
Practice Waterfall Iterative (hybrid) Agile
Goals Goals are defined for
each phase by defining
entry and exit criteria.
Delivering artifacts by
phase wise.
Completion of analysis &
design for a set of features
by one team followed by
completion of code & test
by another team.
Completing the feature/story
in all aspects within a sprint.
Delivering the shippable
product.
Definition of
Ready
Analysis and design
should be completed for
all stories before
programming
Analysis and design should
be completed for a ‘set of
stories’ before
programming
Stories that are not subjected
to change, that can be
completed (analysis to demo)
within the sprint will be
considered for the sprint.
Scoping Product Owner (PO)
decides project scope
Project Manager (PM)
decides scope for iteration
in consultation with
Product Owner
Team decides the sprint
scope as per the capacity
availability & product backlog
prioritization
Agile vs Iterative vs Waterfall – {Planning}
Less Agile
More Agile
10. 10
Practice Waterfall Iterative (hybrid) Agile
Effort
Estimation
PM provides estimates
and get approval from
PO for entire project.
Project Manager (PM)
provides the estimation
for each iteration.
Scrum Master facilitates and
Team does the estimation.
Story points can be reviewed
and refined during sprint
planning meeting.
Scheduling Scheduled by phase wise
milestones – Analysis,
Design, Development
and Testing
Scheduled based on
Iteration wise delivery
commitments –
Iternation#1, #2, #3, #4,
etc.,
Scheduled based on velocity
and Release backlog.
Time boxed in short cycles of
duration say 1wk, 2wks, or
3wks – Sprint#1,#2,#3,#4, etc.,
Plan Review Team need to stick to
baseline project plan.
Team need to stick to
baseline iteration plan
Team can review during mid
sprint planning
Agile vs Iterative vs Waterfall – {Planning}
Less Agile
More Agile
11. 11
Practice Waterfall Iterative (hybrid) Agile
Phase silos or
Role silos or
Story silos
Analysis and design will
be completed for all
stories before
proceeding to coding and
testing. Lag by phase.
Within in the team, analysts &
architects work on analysis &
design of future stories and pass
it to the remaining team to work
on coding & testing of those
stories. Lag by phase with overlap
Team gets divided into mini
teams and each min team
focus on story completion in
all aspects – analysis, design,
development, test, doc,
delivery. There is no lag.
Resource
Utilization
Role specific. Resources
restricted to the tasks
that suits/matches their
role only.
Role switch over rarely seen.
Resources extend only on need
basis.
Role switchover common.
Everybody is ready to work on
any task
(analysis/design/dev/test) to
complete the story.
Ownership Ownership changes from
role to role by phase to
phase. Roles play key
role. PM responsible for
overall delivery.
PM is responsible for getting the
iteration completed.
Entire team is responsible for
story completion in all
aspects – analysis, design,
development, testing and
demo.
Task
Assignment
Project Manager do the
feature/task
assignment for entire
project.
PM influence the feature/task
assignment for entire iteration.
Team members are
empowered to own the
feature/tasks for every
sprint
Agile vs Iterative vs Waterfall – {Execution}
Less Agile
More Agile
12. 12
Practice Waterfall Iterative (hybrid) Agile
Daily Standup Daily/Weekly Status
reports. PM calls for
the status meeting at
scheduled intervals
Daily/Weekly Status
reports. PM calls for the
status meeting at
scheduled intervals.
Scrum Master facilitates the
daily standup meeting to
update:
• what we did?,
• what we are going to do?
• where we lag?
Status Report Status report in
prescribed template.
More focus on
Percentage done.
Status report in
prescribed template.
More focus on
Percentage done.
Update on daily basis by
logging hours spent & hours
required to complete.
Burndown/Burnup chart
reflects the remaining hours
required to complete
Planned vs
Actual
Stick to baseline
project plan
Stick to baseline iteration
plan
Actual hours burnt vs hours
required to complete
Agile vs Iterative vs Waterfall – {Execution}
Less Agile
More Agile
13. 13
Practice Waterfall Iterative (hybrid) Agile
Testing Resources Only Testers will
identify, prepare, and
execute the TCs.
Only Testers will identify,
prepare, and execute the
TCs.
Any one in the team
identify, prepare and
execute TCs.
New Feature Testing TC preparation and
execution starts after
analysis, design and
development phase.
TC preparation and
execution starts after
analysis and design phase.
TC preparation and
execution starts in parallel
with analysis and design
and completes within same
sprint.
Regression Testing After the completion
of first cycle system
testing.
Partial coverage within the
iteration and full coverage
in stabilization iteration.
Full coverage within the
sprint.
Stabilization Phase NA. Full scale regression testing
after the completion of
development iterations.
No feature development.
Only defect fix.
Performance, deployment,
migration testing after the
completion of development
sprints.
No feature development.
Only defect fix.
Agile vs Iterative vs Waterfall – {Execution}
Less Agile
More Agile
14. 14
Practice Waterfall Iterative (hybrid) Agile
Definition of
Done
DOD for a story will be
measured by phase wise
delivery of artifacts (req. doc,
design doc, test cases, code)
which are validated,
reviewed, approved, baseline
and delivered at the end of
respective phase.
DOD will be measured by
phase wise delivery of set
of features - analysis &
design in one phase and
development & testing in
followed phase with in
same iteration.
DOD for a story will be
measured by its capability
of demonstration and
delivery to the external
world.
Story Closing Delivering/Publishing artifacts
(DOD) phase by phase
Closing analysis & design
stories. Closing code & test
stories.
Closing the story based
on demo feedback, test
case results (90% pass)
and defect status (no
critical & high defects)
Delivery Delivering artifacts phase
wise and delivery of working
software at end of the
project.
Delivering working software
at the end of each Iteration.
Demonstration and
delivering working
software at the end of
every sprint.
Agile vs Iterative vs Waterfall – {Completion}
Less Agile
More Agile