Waterfall model

The first known presentation describing use of such phases in software

engineering was held by Herbert D. Benington at the Symposium on Advanced
Programming Methods for Digital Computers on 29 June 1956
Spiral model

This model was first described by Barry Boehm in his 1986 paper, "A Spiral
Model of Software Development and Enhancement.
What is the Agile Manifesto?
 The Agile Manifesto is a document that focuses on four
values and 12 principles for Agile software
development. It was published in February 2001 by 17
software developers who needed an alternative to the
more linear product development process.
 The Agile Manifesto for Software Development was a
declaration of a unifying philosophy for frameworks
like Scrum, Extreme Programming, and Feature-
Driven Development (FDD). The Agile Manifesto
greatly departed from the waterfall-style project
management approaches that were widely in use prior
to that time.
Agile methodology
 Agile methodology is a project management
framework that breaks projects down into several
dynamic phases, commonly known as sprints.
 The Agile framework is an iterative methodology. After
every sprint, teams reflect and look back to see if there
was anything that could be improved so they can
adjust their strategy for the next sprint.
Agile methodology
4 pillars of Agile
 Individuals over processes and tools: Agile teams value team
collaboration and teamwork over working independently and doing
things "by the book.”
 Working software over comprehensive documentation: The
software that Agile teams develop should work. Additional work, like
documentation, is not as important as developing good software.
 Customer collaboration over contract negotiation: Customers are
extremely important within the Agile methodology. Agile teams allow
customers to guide where the software should go. Therefore, customer
collaboration is more important than the finer details of contract
negotiation.
 Responding to change over following a plan: One of the major
benefits of Agile project management is that it allows teams to be
flexible. This framework allows for teams to quickly shift strategies and
workflows without derailing an entire project. Agile embraces change,
focusing on releasing a minimum viable product that can be evaluated
and adjusted from iteration to iteration.
12 principles of agile
 Customer satisfaction
 Early and continuous delivery
 Embrace change
 Frequent delivery
 Collaboration of businesses and developers
 Motivated individuals
 Face-to-face conversation
 Functional products
 Technical excellence
 Simplicity
 Self-organized teams
 Regulation, reflection and adjustment
Agile methodologies
 Kanban
 Scrum
 Extreme Programming (XP)
 Adaptive Project Framework (APF)
 Extreme Project Management (XPM)
 Adaptive Software Development (ASD)
 Dynamic Systems Development Method (DSDM)
 Feature Driven Development (FDD)
 Lean Software Development

Scrum
 Scrum is a subset of Agile. It is a lightweight process
framework for agile development, and the most
widely-used one.
 Scrum is an agile project management methodology
or framework used primarily for software
development projects with the goal of delivering
new software capability every 2-4 weeks.
 Scrum is a common Agile methodology for small
teams and also involves sprints. The team is led by a
Scrum master.
 Sprint planning: This event kicks off the sprint. Sprint
planning outlines what can be delivered in a sprint
(and how).
Scrum
 Sprint retrospective: This recurring meeting acts as a
sprint review—to iterate on learnings from a previous
sprint that will improve and streamline the next one.
Lifecycle of Scrum
Scrum working
Scrum working
 In a rugby scrum, all the players literally put their heads together. When it comes to
software development, a scrum can be characterized by developers putting their heads
together to address complex problems.
 Scrum software development starts with a wish list of features — a.k.a. a product
backlog. The team meets to discuss:
 The backlog.
 What still needs to be completed.
 How long it will take.
 Scrum relies on an agile software development concept called sprints:
 Sprints are periods of time when software development is actually done.
 A sprint usually lasts from one week to one month to complete an item from the backlog.
 The goal of each sprint is to create a saleable product.
 Each sprint ends with a sprint review.
 Then the team chooses another piece of backlog to develop — which starts a new sprint.
 Sprints continue until the project deadline or the project budget is spent.
 In daily scrums, teams meet to discuss their progress since the previous meeting and
make plans for that day.
 The meetings should be brief — no longer than 15 minutes.
 Each team member needs to be present and prepared.
 The ScrumMaster keeps the team focused on the goal.
Scrum Visual Introduction
Key Features of Scrum