Understanding Agile Principles, Slides of Business

Download Understanding Agile Principles and more Slides Business in PDF only on Docsity!

Understanding Agile Principals

Content

• Brief Overview
  • Agility in Government
  • Agile Timeline
  • The Agile Manifesto
  • 12 Principles of Agile Methodology
  • Four Values
  • Scrum
• Lean Principles
• Hybrid Agile Example
• Value Streams
• Agile Frameworks
• Questions and Answers

A

Overview

L

G I^

L

E

What it means?

• A term used to describe "light- weight" development
• A methodology for iteratively developing products
• Based on Scrum and the subsequent Agile Manifesto for Software Development

“Agile is a time boxed, iterative approach that

builds software incrementally from the start of

the project”.

AGILITY IN GOVERNMENT

• Waterfall Development has not traditionally worked well on large development projects in Government

“THE AGONY OF

DEFEAT”

Summary of Unsuccessful Projects

• Federal IT spending is 3.9 of the U.S. Federal budget. 78 Billion USD
• 90% of large IT projects in government are unsuccessful.
• Over half were delayed, over budget and didn’t meet user expectation.
• 41% failed completely. 32 Billion Waste.

2012/2015 Standish (most used) Chaos Report:

18f

A “Feedback-based, epic generation determines themes = Evaluate themes; objectives, KPIs and produce value streams” - A services agency built on the lean start-up model and based within the Federal Government. Their purpose is to support agencies in transforming the way they deliver services and technology.

1. First Federal Scaled-Agile Transformation
2. Development of Agile Procurement Process (GSA)

OVERVIEW OF AGILE SOFTWARE DEVELOPMENT

THE AGILE MANIFESTO

• On February 11-13, 2001, at The Lodge at Snowbird ski resort, 17 people met to drink beer, ski, relax, and try to find common ground.,and of course, to eat. What emerged was the Agile ‘Software Development’ Manifesto.
• Representatives from Extreme Programming (XP), SCRUM, DSDM, Adaptive Software Development, Crystal, Feature-Driven Development, Pragmatic Programming, and others participated. A bigger gathering of organizational anarchists would be hard to find, so what emerged from this meeting was a signed Manifesto for Agile Software;
• Alistair Cockburn’s initial concerns reflected the early thoughts of many participants. He didn't expect that this particular group to ever agree on anything. But his post-meeting feelings were also shared, "Speaking for myself, I am delighted by the final phrasing. I was surprised that the others appeared equally delighted”.

THE AGILE MANIFESTO The Agile Manifesto lists 12 principals to guide teams on how to execute with agility. These are the principles:

• Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
• Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
• Deliver working software frequently, from a couple of weeks to a couple of months, with preference to the shorter timescale.
• Business people and developers must work together daily throughout the project.
• Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
• The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
• Working software is the primary measure of progress.
• Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
• Continuous attention to technical excellence and good design enhances agility.
• Simplicity -- the art of maximizing the amount of work not done -- is essential.

Definition of Scrum

• Definition of Scrum (n): A framework within which people can

address complex adaptive problems, while productively and

creatively delivering products of the highest possible value.

Scrum is:

• Lightweight
• Simple to understand
• Difficult to master

Definition of Scrum

 Roles: In Scrum there is a Development Team, Scrum Master and Product Owner.

 Ceremonies:

• Daily Scrum
• Sprint Planning
• Sprint Review
• Sprint Retrospective

 A Typical sprint will last between 2 and 4 weeks but no more than one month; A

Sprint needs to be;

• Short enough to keep business risk acceptable
• Short enough to synchronize development

Responsible for the product backlog

and maximizing the product ROI.

• Represents the users

• Clearly expresses backlog items

• Orders them by value

• Ensures visibility

Definition of Scrum

Responsible for the scrum process

• Removes impediments

• Facilitates scrum events

• Facilitates communication

Definition of Scrum