agile methodology
TRANSCRIPT
![Page 1: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/1.jpg)
Agile Methodology ISE Seminar
![Page 2: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/2.jpg)
• A Short history of Software development processes
• Defining and Analyzing the Problem ...
• Agile Manifesto
• The Agile Values
• The Agile Principles
• Scrum
Agenda
![Page 3: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/3.jpg)
Software Project Development
Software development processesA [really] short history of
![Page 4: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/4.jpg)
Software Project Development
traditional approach to software development
REQUIREMENTS
DESIGN
DEVELOPMENT
TESTING
MAINTENANCE
Waterfall Development is another name for the more
Waterfall Development
![Page 5: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/5.jpg)
Waterfall Development
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!
![Page 6: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/6.jpg)
• Is there any problem ?
Software Project Development
![Page 7: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/7.jpg)
Waterfall Development
This approach is highly risky, costly and
generally less efficient
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…REQUIREMENTS
DESIGN
DEVELOPMENT
TESTING
MAINTENANCE
Takes too long
Changes
Skipped
![Page 8: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/8.jpg)
Software Project Development
![Page 9: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/9.jpg)
Software Project Development
![Page 10: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/10.jpg)
Software Project Development
![Page 11: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/11.jpg)
Software Project Development
![Page 12: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/12.jpg)
Software Project Development
![Page 13: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/13.jpg)
Software Project Development
AGILERapid
Cooperative
Quality-driven
Not a process, it's a philosophy or set of values
Iterative
Adaptable
![Page 14: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/14.jpg)
XP
Scrum
Lean
Crystal
Adaptive
FDD
DSDM
Pragmatic
RUP (120+)
XP (13)
Scrum (9)
Kanban (3)
Do Whatever!! (0)
More Prescriptive
More Adaptive
RUP has over 30 roles, over 20 activities, and over 70 artifacts
AGILE
Software Project Development
![Page 15: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/15.jpg)
Software Project Development
![Page 16: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/16.jpg)
Software Project Development
![Page 17: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/17.jpg)
Software Project Development
![Page 18: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/18.jpg)
Software Project Development
the most important factors that you need to consider are the people and how they work together
A fool with a tool is still a fool.
![Page 19: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/19.jpg)
Software Project Development
![Page 20: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/20.jpg)
Software Project Development
Never forget that the primary goal of software development is to create software, not documents !
Otherwise it would be called documentation development wouldn’t it?
When you ask a user whether they would want ??
A fifty page document describing what you intend to build ?
orThe actual software itself, what do you think
they’ll pick?
![Page 21: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/21.jpg)
Software Project Development
![Page 22: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/22.jpg)
Software Project Development
Remember!!Only your customer can tell you what they want
![Page 23: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/23.jpg)
Software Project Development
![Page 24: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/24.jpg)
Software Project Development
Remember!!
Nothing ever goes entirely on plan
but instead of sticking with something that isn't working
It's much more effective to make adjustments as your situation changes
![Page 25: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/25.jpg)
Software Project Development
Following the values isn't always easy
But when you build them is your team's processes
You will definitely get a better software project
![Page 26: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/26.jpg)
Software Project Development
Hmm..
So , Is that It ?
![Page 27: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/27.jpg)
Software Project Development
Sure No !!
![Page 28: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/28.jpg)
Software Project Development
The four core values are illuminated by
12 principles of Agile software development.
![Page 29: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/29.jpg)
Software Project Development
“ Our highest priority is tosatisfy the customer through early and continuous delivery of valuable software. ”
Principle
#1
![Page 30: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/30.jpg)
Software Project Development
“ Welcome changing requirements, even late in development.Agile processes harness changefor the customer's competitive advantage.”
Principle
#2
![Page 31: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/31.jpg)
Software Project Development
“ Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter time scale. ”
Principle
#3
![Page 32: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/32.jpg)
Software Project Development
“ Business people and developers must work together daily throughout the project. “
Principle
#4
![Page 33: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/33.jpg)
Software Project Development
“ Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. “
Principle
#5
![Page 34: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/34.jpg)
Software Project Development
“ The most efficient and effectivemethod of conveying information toand within a development team is face-to-face conversation.“
Principle
#6
![Page 35: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/35.jpg)
Software Project Development
“Working software is the primary measure of progress. “
Principle
#7
![Page 36: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/36.jpg)
Software Project Development
“ Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. “
Principle
#8
![Page 37: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/37.jpg)
Software Project Development
“ Continuous attention to technical excellence and good design enhances agility. “
Principle
#9
![Page 38: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/38.jpg)
Software Project Development
“ Simplicity – the art of maximizing the amount of work not done ,is essential. “
Principle
#10
![Page 39: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/39.jpg)
Software Project Development
“ The best architectures, requirements, and designs emerge from self-organizing teams. “
Principle
#11
![Page 40: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/40.jpg)
Software Project Development
“At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.“
Principle
#12
![Page 41: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/41.jpg)
Scrum
![Page 42: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/42.jpg)
Scrum
• Scrum is an agile process that allows us to focus on delivering the highest business value in the shortest time.
• It allows us to rapidly and repeatedly check actual working software (2 – 4 weeks).
• The business sets the priorities.
![Page 43: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/43.jpg)
Scrum characteristics
• Self organizing team to determine the best way to deliver the highest priorities features
• Product progresses in a series of month-long “sprints”
• Requirements are captured as items in a list “product backlog”
• Uses general rules to create an agile environment for delivering projects
![Page 44: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/44.jpg)
Scrum sprint
![Page 45: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/45.jpg)
Scrum sprint
• Scrum projects make progress in a series of “sprints”
• Typical duration is 2–4 weeks
• Product is designed, coded, and tested during the sprint
NO Changes During Sprint !
![Page 46: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/46.jpg)
Scrum breaking down
![Page 47: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/47.jpg)
Scrum artifacts
The scrum team uses artifacts to run scrum successfully
• Impediment backlog
• Product backlog
• Sprint backlog
• Burn down charts
![Page 48: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/48.jpg)
Scrum ceremonies
• Sprint planning
• Sprint review
• Sprint retrospective
• Daily scrum
![Page 49: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/49.jpg)
Scrum ceremonies
Sprint planning :
• Sprint planning meeting #1
• Sprint planning meeting #2
![Page 50: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/50.jpg)
Scrum ceremonies
Sprint planning meeting #1:
• Purpose
• Basics
• Ingredients
• Output
![Page 51: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/51.jpg)
Scrum ceremonies
Sprint planning meeting #2:
• Purpose
• Basics
• Ingredients
• Output
![Page 52: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/52.jpg)
Scrum ceremonies
Sprint review:
• Purpose
• Basics
• Ingredients
• Output
![Page 53: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/53.jpg)
Scrum ceremonies
Sprint retrospective:
• Purpose
• Basics
• Ingredients
• Output
![Page 54: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/54.jpg)
Scrum ceremonies
Daily scrum
• Purpose
• Basics
• Ingredients
• Output
![Page 55: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/55.jpg)
Scrum roles
• Scrum master
• Team
• Product owner
• Customer
• User
![Page 56: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/56.jpg)
Scrum roles
Scrum Master:
• Represents management to the project
• Responsible for enacting Scrum values and practices
• Removes impediments (obstacles)
• Ensure that the team is fully functional and productive
• Enable close cooperation across all roles and functions
• Shield the team from external interferences
![Page 57: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/57.jpg)
Scrum roles
Team:
• (5 - 9) people
• Cross functional (programmers – designers….)
• Full time
• Self organizing
![Page 58: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/58.jpg)
Scrum roles
Team tasks:
• Delivers the product and is responsible for its quality
• Creating product backlog
• Analyses the backlog for information
• Works with product owner for strategic alignment
![Page 59: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/59.jpg)
Scrum roles
Product owner:
• Define the features of the product
• Decide on release date and content
• Be responsible for the profitability of the product
• Prioritize features according to market value
• Adjust features and priority every iteration, as needed
• Accept or reject work results
![Page 60: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/60.jpg)
Scrum roles
Customer:
• Executive managers
• Requests the product from Scrum team
• Budget
![Page 61: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/61.jpg)
Scrum roles
User:
• Defines the product with his business knowledge
• Domain expert , end user , marketing department
![Page 62: Agile Methodology](https://reader038.vdocuments.mx/reader038/viewer/2022100504/586ff9151a28ab92198b7885/html5/thumbnails/62.jpg)
Thanks For Listening