This document provides an overview of agile methodology and compares it to traditional waterfall development. It describes that agile focuses on iterative development with working software delivered frequently in short cycles. The key principles of the agile manifesto are also outlined. Specific agile frameworks like Scrum and Kanban are then explained in more detail. Scrum uses sprints, daily stand-ups, and artifacts like backlogs and burn-down charts. Kanban emphasizes visualizing and limiting work in progress to optimize flow. UX design is noted as an area that can benefit from adopting agile principles.
Agile methodology is a framework for modern software development.
What is the philosophy behind Agile?
How does it differ from traditional project management strategies like waterfall?
What are the stages, meetings, tools, and team roles?
What is Scrum?
A fair analysis of the Agile Methodology. A quick comparison of Agile and Waterfall to clear up misconceptions about the two. Scalability is a major issue with Agile and is worth considering if you're not a large software company.
This PPT throws light on some of the essential elements of the Agile methodology which has become crucial to ensure quality in this day and age. To know more on agile methodology, Scrum Model, Agile Principles and Scrum Board go through this presentation as well as the ones coming soon.
Agile methodology is a framework for modern software development.
What is the philosophy behind Agile?
How does it differ from traditional project management strategies like waterfall?
What are the stages, meetings, tools, and team roles?
What is Scrum?
A fair analysis of the Agile Methodology. A quick comparison of Agile and Waterfall to clear up misconceptions about the two. Scalability is a major issue with Agile and is worth considering if you're not a large software company.
This PPT throws light on some of the essential elements of the Agile methodology which has become crucial to ensure quality in this day and age. To know more on agile methodology, Scrum Model, Agile Principles and Scrum Board go through this presentation as well as the ones coming soon.
Introduction to the scrum framework: roles, activities and artifacts.
Scrum is an agile methodology for project management, to create a high quality product.
www.nieldeckx.be
This presentation describes the basics of Agile methodologies and how it is differed from Waterfall. Then continues with the most famous Agile approach: Scrum
Join BostonPHP and Michael Bourque as he presents the concept of Scrum and shows why so many people are now deploying scrum to their development projects. Michael will take us through the process and talk about how his company, Parametric Technology Inc. (PTC) , is successfully applying Scrum.
There you can find about definition of agile model.Working of agile model.You can also find where to use agile model.Examples of agile model is also given here.
Introduction to the scrum framework: roles, activities and artifacts.
Scrum is an agile methodology for project management, to create a high quality product.
www.nieldeckx.be
This presentation describes the basics of Agile methodologies and how it is differed from Waterfall. Then continues with the most famous Agile approach: Scrum
Join BostonPHP and Michael Bourque as he presents the concept of Scrum and shows why so many people are now deploying scrum to their development projects. Michael will take us through the process and talk about how his company, Parametric Technology Inc. (PTC) , is successfully applying Scrum.
There you can find about definition of agile model.Working of agile model.You can also find where to use agile model.Examples of agile model is also given here.
Overview of SCRUM development process. I put this together to present to my company/group.
Most slides are "borrowed" from Alan Shalloway's presentation.
What is Scrum? And Why? (For Stakeholders)Keisuke Daimon
This is to explain what scrum is and why we use it to stackholders (those who are not in Scrum team). Details about Scrum are not mentioned, but clarifying concepts is the main focus.
Ethnobotany and Ethnopharmacology:
Ethnobotany in herbal drug evaluation,
Impact of Ethnobotany in traditional medicine,
New development in herbals,
Bio-prospecting tools for drug discovery,
Role of Ethnopharmacology in drug evaluation,
Reverse Pharmacology.
Palestine last event orientationfvgnh .pptxRaedMohamed3
An EFL lesson about the current events in Palestine. It is intended to be for intermediate students who wish to increase their listening skills through a short lesson in power point.
The Indian economy is classified into different sectors to simplify the analysis and understanding of economic activities. For Class 10, it's essential to grasp the sectors of the Indian economy, understand their characteristics, and recognize their importance. This guide will provide detailed notes on the Sectors of the Indian Economy Class 10, using specific long-tail keywords to enhance comprehension.
For more information, visit-www.vavaclasses.com
Welcome to TechSoup New Member Orientation and Q&A (May 2024).pdfTechSoup
In this webinar you will learn how your organization can access TechSoup's wide variety of product discount and donation programs. From hardware to software, we'll give you a tour of the tools available to help your nonprofit with productivity, collaboration, financial management, donor tracking, security, and more.
How to Make a Field invisible in Odoo 17Celine George
It is possible to hide or invisible some fields in odoo. Commonly using “invisible” attribute in the field definition to invisible the fields. This slide will show how to make a field invisible in odoo 17.
This is a presentation by Dada Robert in a Your Skill Boost masterclass organised by the Excellence Foundation for South Sudan (EFSS) on Saturday, the 25th and Sunday, the 26th of May 2024.
He discussed the concept of quality improvement, emphasizing its applicability to various aspects of life, including personal, project, and program improvements. He defined quality as doing the right thing at the right time in the right way to achieve the best possible results and discussed the concept of the "gap" between what we know and what we do, and how this gap represents the areas we need to improve. He explained the scientific approach to quality improvement, which involves systematic performance analysis, testing and learning, and implementing change ideas. He also highlighted the importance of client focus and a team approach to quality improvement.
We all have good and bad thoughts from time to time and situation to situation. We are bombarded daily with spiraling thoughts(both negative and positive) creating all-consuming feel , making us difficult to manage with associated suffering. Good thoughts are like our Mob Signal (Positive thought) amidst noise(negative thought) in the atmosphere. Negative thoughts like noise outweigh positive thoughts. These thoughts often create unwanted confusion, trouble, stress and frustration in our mind as well as chaos in our physical world. Negative thoughts are also known as “distorted thinking”.
4. Waterfall Development
(contd..)
You complete one phase (e.g. design) before moving
on to the next phase (e.g.development)
You rarely aim to re-visit a ‘phase’ once it’s
completed. That means, you better get whatever
you’re doing right the first time!
5. This approach is highly risky, often more costly and
generally less efficient than Agileapproaches
DESIGN
DEVELOPMENT
TESTING
MAINTENANCE
Takes too long
Changes
REQUIREMENTS
Skipped
You don’t realize any value until
the end of the project
You leave the testing until the end
You don’t seek approval from the
stakeholders until late in the day
But…
7. Individuals and interactions over
processes and tools
Working software over comprehensive
documentation
Customer collaboration over
contract negotiation
Responding to change over
following a plan
Agile Manifesto
8. Agile Umbrella
Agile
XP
DSDM
FDD
Scrum
Crystal
Kanban
XP (13)
Scrum (9)
Kanban (3)
Do Whatever!! (0)RUP
and fewmore…
* Check wikipedia for list of all Agile methods
RUP has over 30 roles, over 20
activities, and over 70 artifacts
More Prescriptive
more rules to follow
RUP (120+)
More Adaptive
fewer rules to follow
9. ScrumA light-weight agile processtool
Split your organization
into small, cross-functional, self-
organizing teams. Scrum Team
Scrum Master
Split your work into a list of small, concrete deliverables.
Sort the list by priority and estimate the relative effort of each
item.
Product/ Project
Owner
10. Scrum
(contd..)
Split time into short fixed-length iterations/ sprints (usually 2 – 4
weeks), with potentially shippable code demonstrated after each
iteration.
January May
Optimize the release plan and update priorities in
collaboration with the customer, based on insights gained by
inspecting the release after each iteration.
Optimize the process by having a retrospective after each
iteration.
13. Things we do in Scrum
a.k.a Scrum terminologies
The project/ product is described as a list of features: the backlog.
The features are described in terms of user stories.
The scrum team estimates the work associated with eachstory.
Features in the backlog are ranked in order of importance.
Result: a ranked and weighted list of productfeatures, a
roadmap.
Daily scrum meeting to discuss What did you do y’day? What
will you do today? Any obstacles?
14. Iteration/ Sprint 1 Iteration/ Sprint 2
Scrum Artifacts
Sample Userstory
10h
Eff
r
or
s
ts
Efforts: 2hrs IA, 6hrs Development, 2hrs Testing
The total effort each iteration can
accommodate leads to number
of user story per iteration
One release may contains number of iterations
Release
15. Scrum planning example
Iteration cycle of 3 weeks
Working hours per day is 8
Total hours of work iteration can
accommodate
8hrs x 5days x 3weeks =120hrs
Product backlog of 20 stories
Each story effort is 10 hrs
Iteration backlog or number of stories per iteration
12 user story
16. Scrum in a nutshell
So instead of a large group spending a long time building a
big thing, we have a small team spending a short time
building a small thing.
But integrating regularly to see the whole.
18. KanbanLean approach to agiledevelopment
Similar to Scrum in the sense that you focus on features as
opposed to groups of features – however Lean takesthis
one step further again.
You select, plan, develop, test and deploy one
feature (in its simplest form) before you
select, plan, develop, test and deploy the next
feature.
Aim is to eliminate ‘waste’ whereverpossible…
19. Kanban (contd…)
Visualize the workflow
Split the work into
pieces, write each item on
a card and put on the wall
Use named columns to illustrate where
each item is in the workflow
Limit WIP (work in progress)
Assign explicit limits to how many items may be in progress
at each stage
Measure the lead time (average time to complete one
item, sometimes called “cycle time”)
Optimize the process to make lead time as small and predictable as possible
![Overview of
Agile Methodology
Dhruv Kumar [Mercer : Correspondence Team]](https://image.slidesharecdn.com/agilemethodology-200427064019/85/Agile-methodology-1-320.jpg)
![A [really] short history of
Software development processes](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)