0% found this document useful (0 votes)
35 views31 pages

Agile Background

Uploaded by

Sdhffj Skafkdf
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
35 views31 pages

Agile Background

Uploaded by

Sdhffj Skafkdf
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 31

Agile Supporting Rolls Royce …

… a pre-eminent engineering company focused


on world-class power and propulsion systems
Date: 09/10/2017
Agile Enabling Engineering Improvements …
… to keep Rolls Royce Engineering improving at a
sustainably fast pace and in the right direction
Objective of this Agile Training Workshop:
- Introduction to the Agile Manifesto
- Introduction to Agile
- Look at how project delivery can improve using Agile
- Undertake workshop exercises to familiarise with Agile working
Introduce ourselves
Introduction to the to
the Agile
Agile Manifesto
Manifesto
First a little History and Some High Level Definitions

History: The Agile Manifesto. On February 11-13, 2001, at The Lodge at Snowbird ski resort in the
Wasatch mountains of Utah, seventeen people met to talk, ski, relax, and try to find common ground -
and of course, to eat. What emerged was the Agile 'Software Development' Manifesto.

Agile management, or agile process management, or simply agile refers to an iterative, incremental
method of managing the design and build activities of engineering, information technology and other
business areas that aim to provide new product or service development in a highly flexible and
interactive manner

Agile Software Development is an umbrella term for a set of methods and practices based on the
values and principles expressed in the Agile Manifesto. Solutions evolve through collaboration
between self-organizing, cross-functional teams utilizing the appropriate practices for their context.
Manifesto for Agile Software Development
We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:

Individuals and interactions over processes and tools


Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on
the right, we value the items on the left more.
The Agile Manifesto, also called the Manifesto for Agile Software Development,
is a formal proclamation of four key values and 12 principles to guide an iterative
and people-centric approach to software development.
Principles behind the Agile Manifesto

We follow these principles:


1) Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

2) Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.

3) Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

4) Business people and developers must work together daily throughout the project.

5) Build projects around motivated individuals.

6) Give them the environment and support they need, and trust them to get the job done.

7) The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

8) Working software is the primary measure of progress.

9) Agile processes promote sustainable development.

10) The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

11) Continuous attention to technical excellence and good design enhances agility.

12) Simplicity--the art of maximizing the amount of work not done--is essential.

The best architectures, requirements, and designs emerge from self-organizing teams.

At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly.
Good Practice
1. Active user involvement is imperative
2. The team must be empowered to make decisions
3. Requirements evolve but the timescale is fixed
4. Capture requirements at a high level; lightweight & visual
5. Develop small, incremental releases and iterate
6. Focus on frequent delivery of products
7. Complete each feature before moving on to the next
8. Apply the 80/20 rule
9. Testing is integrated throughout the project lifecycle – test early and
often
10. A collaborative & cooperative approach between all stakeholders is
essential
Introduce ourselves to
Agile
the Agile Manifesto
Extreme Programming
(XP) is a software development
Scrumban methodology which is intended to
is an Agile management improve software quality and
methodology describing hybrids of responsiveness to changing
Scrum and Kanban and was customer requirements. As a type
originally designed as a way to of agile software development, it
transition from Scrum to Kanban. advocates frequent "releases" in
short development cycles, which
is intended to improve
productivity and introduce
checkpoints at which new
customer requirements can be
adopted.

Agile Software Development


Is an approach employed to build a project in phases. The first
Scrum
phase involves constructing the most important functionality and
is an iterative and incremental
then more features are added or the system is improved during
agile software development
later iterations.
framework for managing Lean
product development. creates more value for customers with
fewer resources. A lean organization
understands customer value and focuses
Feature-Driven its key processes to continuously increase
Development (FDD) is a client-centric, it. The ultimate goal is to provide perfect
architecture-centric, and pragmatic value to the customer through a perfect
software process. The term "client" in value creation process that has zero
Kanban FDD is used to represent what Agile waste.
is a scheduling system for lean Modeling (AM) refers to as project
manufacturing and just-in-time stakeholders or eXtreme Programming
manufacturing. Kanban is an (XP) calls customers.
inventory-control system to
control the supply chain.
Dynamic Systems
Development Method
is an agile project delivery Crystal Methodology
framework, initially used as a is one of the most lightweight, adaptable approaches to software development. Crystal is actually comprised of a family of agile
software development method. methodologies such as Crystal Clear, Crystal Yellow, Crystal Orange and others, whose unique characteristics are driven by several
First released in 1994, DSDM factors such as team size, system criticality, and project priorities. This Crystal family addresses the realization that each project may
originally sought to provide require a slightly tailored set of policies, practices, and processes in order to meet the project ‘s unique characteristics.
some discipline to the rapid Several of the key tenets of Crystal include teamwork, communication, and simplicity, as well as reflection to frequently adjust and
application development, RAD, improve the process. Like other agile process methodologies, Crystal promotes early, frequent delivery of working software, high user
method. involvement, adaptability, and the removal of bureaucracy or distractions.
Scrum
is an iterative and incremental agile software development framework for managing product development.
Kanban
is a scheduling system for lean manufacturing and just-in-time manufacturing. Kanban is an
inventory-control system to control the supply chain.
Scrumban
is an Agile management methodology describing hybrids of Scrum and Kanban
and was originally designed as a way to transition from Scrum to Kanban.
Dynamic Systems Development Method
is an agile project delivery framework, initially used as a software development method. First
released in 1994, DSDM originally sought to provide some discipline to the rapid application
development, RAD, method.
Feature-Driven
Development (FDD) is a client-centric, architecture-centric, and pragmatic software process. The
term "client" in FDD is used to represent what Agile Modelling (AM) refers to as project
stakeholders or eXtreme Programming (XP) calls customers.
Extreme Programming
(XP) is a software development
methodology which is intended to
improve software quality and
responsiveness to changing customer
requirements. As a type of agile
software development, it advocates
frequent "releases" in short
development cycles, which is
intended to improve productivity and
introduce checkpoints at which new
customer requirements can be
adopted.
Agile Software Development
Is an approach employed to build a project in phases. The first phase involves constructing the most
important functionality and then more features are added or the system is improved during later
iterations.
Lean
creates more value for customers with fewer resources. A lean organization understands
customer value and focuses its key processes to continuously increase it. The ultimate goal is to
provide perfect value to the customer through a perfect value creation process that has zero
waste.
Crystal Methodology
is one of the most lightweight, adaptable approaches to software development. Crystal is actually
comprised of a family of agile methodologies such as Crystal Clear, Crystal Yellow, Crystal Orange and
others, whose unique characteristics are driven by several factors such as team size, system criticality,
and project priorities. This Crystal family addresses the realization that each project may require a
slightly tailored set of policies, practices, and processes in order to meet the project ‘s unique
characteristics.
Several of the key tenets of Crystal include teamwork, communication, and simplicity, as well as
reflection to frequently adjust and improve the process. Like other agile process methodologies, Crystal
promotes early, frequent delivery of working software, high user involvement, adaptability, and the
removal of bureaucracy or distractions.
Not a methodology! The Agile movement seeks alternatives to
traditional project management. Agile approaches help teams
respond to unpredictability through incremental, iterative work
cadences and empirical feedback. Agilists propose alternatives to
waterfall, or traditional sequential development.
How Agile can improve
projects and daily activities
Team Challenge 1
with prizes ! ! !
Build a Helicopter
Build a Helicopter
With the materials provided in two/four??? teams,
one using a Waterfall approach and one using an
Agile approach the object of the challenge is to:

Safely helicopter-down a cup of water from a chair


at outreached arm height - or from the first floor
balcony if we’re allowed!

The winning helicopter will be judged on the


length of time the helicopter takes to land in
seconds, multiplied by the fullness of the cup of
water upon landing.
Team Challenge 2
with prizes ! ! !
Create a Rolls Royce
Orientated Board Game
With the materials provided in two teams, one using a
Waterfall approach and one using an Agile approach:

Create a game for which an independent panel of


people will judge the winner after a 5 minute
presentation from each team.
Whole Group Challenge
Develop/Discuss an Agile approach which will
improve the operation of Engineering Improvements
And … the main prize goes to …
For their significant
contribution to the day
Thank You
The End

You might also like