Scribd
Upload
6 views

Agile Class Presentation (1)

Agile is a methodology originally developed for software development that emphasizes collaboration, flexibility, and customer satisfaction, guided by the Agile Manifesto's values and principles. It includes frameworks like Scrum, which focuses on iterative development and continuous improvement through prioritized tasks and regular team reviews. Agile methodologies are now applied beyond software development, impacting various fields such as marketing and customer success.

Uploaded by

Sanjana Dwivedi
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
6 views

Agile Class Presentation (1)

Agile is a methodology originally developed for software development that emphasizes collaboration, flexibility, and customer satisfaction, guided by the Agile Manifesto's values and principles. It includes frameworks like Scrum, which focuses on iterative development and continuous improvement through prioritized tasks and regular team reviews. Agile methodologies are now applied beyond software development, impacting various fields such as marketing and customer success.

Uploaded by

Sanjana Dwivedi
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 11

Chapter AGILE

DEVELOPMENT
5
What Is Agile?
Agile was originally developed by software developers as
a better process for managing their work, but today, it
encompasses a range of different Agile methodologies
used in disciplines from marketing to customer success
and beyond.

Agile refers to a set of “methods and practices based on


the values and principles expressed in the
Agile Manifesto,” which includes things like collaboration,
self-organization, and cross functionality of teams.
The Agile Manifesto

The Agile Manifesto characterizes Agile values as:


• Individuals and interactions over processes and tools

• Working software over comprehensive documentation

• Customer collaboration over contract negotiation

• Responding to change over following a plan


Twelve Principles of Agile Manifesto

• Customer Satisfaction − Highest priority is given to satisfy the requirements of customers through early and continuous

delivery of valuable software.

• Welcome Change − Changes are inevitable during software development. Ever-changing requirements should be welcome,

even late in the development phase. Agile processes should work to increase customers' competitive advantage.

• Deliver a Working Software − Deliver a working software frequently, ranging from a few weeks to a few months, considering

shorter time-scale.

• Collaboration − Business people and developers must work together during the entire life of a project.

• Motivation − Projects should be built around motivated individuals. Provide an environment to support individual team

members and trust them so as to make them feel responsible to get the job done.

• Face-to-face Conversation − Face-to-face conversation is the most efficient and effective method of conveying information

to and within a development team.


Twelve Principles of Agile Manifesto …cntd

• Measure the Progress as per the Working Software − Working software is the key and it should be the primary

measure of progress.

• Maintain Constant Pace − Agile processes aim towards sustainable development. The business, the developers,

and the users should be able to maintain a constant pace with the project.

• Monitoring − Pay regular attention to technical excellence and good design to enhance agility.

• Simplicity − Keep things simple and use simple terms to measure the work that is not completed.

• Self-organized Teams − An agile team should be self-organized and should not depend heavily on other teams

because the best architectures, requirements, and designs emerge from self-organized teams.

• Review the Work Regularly − Review the work done at regular intervals so that the team can reflect on how to

become more effective and adjust its behavior accordingly.


Agile History
• Agile was born out of the techniques utilized by innovative
Japanese companies in the 70’s and 80’s (companies like
Toyota, Fuji, and Honda).
• In the mid-90’s, a man by the name of Jeff Sutherland found
himself frustrated by companies who were continually plagued
by projects that were behind schedule and over budget. He
sought to find a better way.
• His research brought him to these Japanese companies and
their Agile methods. Basing his work on this, Sutherland created
the Scrum framework. After a series of successes using his new
methods, Scrum began to quickly spread throughout the
product development world.
Scurm
• Scrum is a framework that is used to implement Agile development.

• One of the core features of Scrums is the idea of iteration and


improvement. This is regarding both the product being worked
on, and the efficiency of the team itself.

• Scrum is built on iterative deliveries of your product. Rather


than waiting until the project is 100% complete to deliver it to
the user, you deliver useable chunks of the project over time.
This helps avoid wasted efforts when needs change or things
get lost in communication.
Scurm …cntd
• But beyond the importance of iterations and
improvements for the product, Scrum also focuses on
improving the process with each new cycle.

• Using the Scrum Agile methodology, a Product Owner


sets a list of priorities, the Product Backlog, to be
completed by a cross-functional team. The team works
to deliver “potentially shippable increments” of software
in 2-4-week sprints, at the end of which the Product
Backlog is reevaluated and prioritized.
•Scrum starts with a Product Owner. This is the person who represents the final user’s
best interest, and has the authority to say what goes into the final product.
•That Product Owner is in charge of making the Backlog, a list of tasks and requirements
the final product needs. Here’s an important part: The backlog MUST be prioritized. That’s
the job of the Product Owner.
• If I were using Scrum to design a car, items like “Must have an engine” would be
near the top of my prioritized list, because the car can’t work without it. “Must be
painted red” would be lower on my priority list; it might still be important to me, but
it’s not a requirement for the car to run.
•Next up is the Sprint. A Sprint is a predetermined timeframe within which the team
completes sets of tasks from the Backlog. The length of time depends on the needs of the
team, but two weeks is pretty typical.
•Teams meet every day to give progress updates in the Daily Scrum. Many people also
call these “Daily Stand-Ups.”
•Each Sprint ends with a review, or Retrospective, where the team reviews their work and
https://www.youtube.com/watch?v=4QtC65GvfT0 - 1. Agile Introduction

https://www.youtube.com/watch?v=sNRhSoLeVPw –2.Agile scrum for beginners

https://www.atlassian.com/agile/scrum ----3. Scrum details

You might also like