Agile Software Development

(ASD) Lect-3
Prof. Daiwat Vyas

B.TECH SEMESTER 6TH CSE

Fundamentals Of Agile
• Overview of Scrum

• eXtreme Programming (XP)

• Feature driven development

• Lean Software Development

Overview of Scrum
•A

Fig 1.0 Overview of Scrum. Source images.google.com

Overview of Scrum
•A
Overview of Scrum
•A
Overview of Scrum
• Scrum is a project management technique that is actively used in
software development.

• Based on Scrum, it is possible to implement a flexible approach to

complex product development.

• It is a framework and not a methodology.

Overview of Scrum
• A methodology provides ready instructions on how to achieve
results, but the framework does not.

• People follow the rules of Scrum, but they make decisions on various
work processes themselves.

• It is based on an autonomous team (5 to 9 people) who make

independent decisions about how to carry out a task.
Overview of Scrum
• It should be a cross-functional team, meaning that:
• its members should possess enough knowledge and skills to fully
perform the project from the step where an idea is voiced to the final
stage where the ready product is released.
• Two more people have to join the team: a product owner and a Scrum
master.
• The former connects the team with the customer and monitors the
project development – this person is not a formal team leader but
rather a curator.
• The latter helps the former implement a business process.
Overview of Scrum
• This is not a rigid pattern of work on a product, but a technology that
allows changes to be made in the work process and provides the
customer with the work result in steps based on importance.

• The product features are built step by step, meaning that the most
necessary and basic things are done first, and all the rest
improvements follow them.
Overview of Scrum
• SCRUM principles and lessons can be applied to all kinds of
teamwork.

• This is one of the reasons Scrum is so popular.

• Often thought of as an agile project management framework, Scrum

describes a set of meetings, tools, and roles that work in concert to
help teams structure and manage their work.
eXtreme Programming (XP)
• eXtreme Programming (XP) is an Agile methodology consisting of
effective development practices to achieve client satisfaction.
• Mainly Focus on
• Constantly Delivering Software
• Responding to change
• Effective Team Work
• Self Organization
• Besides encouraging simplicity, communication, and feedback, XP
fosters respect and courage
eXtreme Programming (XP)
• It is specifically designed for improving the quality of the software,
the work process for the development team and increased customer
satisfaction.

• Why Extreme Programming (XP)?

• What is Extreme Programming (XP) made of?

eXtreme Programming (XP)
• Why Extreme Programming (XP)?
• Extreme Programming works towards providing iterative and
recurrent software releases throughout the project;

• Instead of everything together after a single, long project

development lifecycle.

• These short iterative cycles help both team members and customers
to assess and review the project’s progress throughout its
development.
eXtreme Programming (XP)
• What is Extreme Programming (XP) made of?

• XP incorporates the following 5 values:

• Communication: Software Development projects or projects in any

industry rely heavily on communication. XP focuses on effective
communication between the team and the customer.
eXtreme Programming (XP)
• What is Extreme Programming (XP) made of?
• Simplicity: XP looks for the simplest ways to get things done. This
means doing what is essential thereby reducing waste, address only
the known issues and keeping the design simple for effective creation
and maintenance.

• Feedback: Feedback plays an important role in project

improvement. XP encourages instantaneous feedback. This helps the
team identify room for improvement and revise practices.
eXtreme Programming (XP)
• What is Extreme Programming (XP) made of?

• Respect: The team must respect each other both personally and
professionally, to achieve goals.

• Courage: XP endorses courage at all levels. This can include speaking

up against what does not work and anything that affects the project’s
effectiveness, or accept feedback and improve methodologies.
eXtreme Programming (XP)
• The core of XP is an interconnected set of software development
practices.

• While it is possible to implement these practices in isolation, many

teams have found that some practices reinforce the others and should
be done in conjunction.
eXtreme Programming (XP)
• The original twelve practices for XP comprise:
Feature Driven Development
• It is iterative and incremental software development process.
• FDD is a model-driven short-iteration process that consists of five
basic activities
1. Develop overall model
2. Build feature list
3. Plan by feature
4. Design by feature
5. Build by feature
Feature Driven Development
• A
Lean Software Development
• Inspired by manufacturing industry “Toyota Production System”.
• Seven Principle of Lean
1. Eliminate the waste
2. Amplify the learning
3. Decide as late as possible
4. Deliver as fast as possible
5. Empower the team
6. Build quality
7. See the whole
• Think big, Act less, fail fast and learn rapidly