12
© 2007 BigVisible Solutions, Inc. All Rights Reserved Training Solutions Agile Training Game v. 7.3.1

© 2007 BigVisible Solutions, Inc. All Rights Reserved Training Solutions Agile Training Game v. 7.3.1

Embed Size (px)

Citation preview

Page 1: © 2007 BigVisible Solutions, Inc. All Rights Reserved Training Solutions Agile Training Game v. 7.3.1

© 2007 BigVisible Solutions, Inc. All Rights Reserved

Training Solutions

Agile Training Game

v. 7.3.1

Page 2: © 2007 BigVisible Solutions, Inc. All Rights Reserved Training Solutions Agile Training Game v. 7.3.1

Agile Training Game

© 2007 BigVisible Solutions, Inc.. All Rights Reserved

2

____ __ ____ _____ ____ ______ _____ _____ ____ _____ _____ _____ ____ _____

Click to edit Master text stylesSecond levelThird levelFourth levelFifth level

Trouble With Traditional Project Approach

Some Interesting Findings:

A study of 8,300+ projects completed by large American companies using traditional methodologies revealed:

Most Common Reasons for Failure: Incomplete or changing requirements Lack of User Input

Only 42% of features originally proposed are implemented

Only 16% of projects finished on-time, on-budget with originally defined scope

FACT!66% of Product Features are rarely, if ever, used.

FACT!80% of a Product’s Features are added after the first release

Page 3: © 2007 BigVisible Solutions, Inc. All Rights Reserved Training Solutions Agile Training Game v. 7.3.1

Agile Training Game

© 2007 BigVisible Solutions, Inc.. All Rights Reserved

3

____ __ ____ _____ ____ ______ _____ _____ ____ _____ _____ _____ ____ _____

Click to edit Master text stylesSecond levelThird levelFourth levelFifth level

What is Agile?

► Agile Software Development processes were first formulated in the early 1990’s

► The Agile core set of values was articulated in the Agile Manifesto in 2001

We 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”

► Agile processes present light-weight methodologies that focus on incremental, iterative development

► Agile implementations focus on rapid value delivery, minimizing waste and continuous improvement

Page 4: © 2007 BigVisible Solutions, Inc. All Rights Reserved Training Solutions Agile Training Game v. 7.3.1

Agile Training Game

© 2007 BigVisible Solutions, Inc.. All Rights Reserved

4

____ __ ____ _____ ____ ______ _____ _____ ____ _____ _____ _____ ____ _____

Click to edit Master text stylesSecond levelThird levelFourth levelFifth level

Goals of Agile

► Faster Release Cycles Reduced time to market

► Better Productivity Team focused on product development

► Increased Quality Quality controls embedded throughout lifecycle

► Focus on Delivering True Value Value can only be recognized in the form of completed product

► Responsive to Change No change control process required

Page 5: © 2007 BigVisible Solutions, Inc. All Rights Reserved Training Solutions Agile Training Game v. 7.3.1

Agile Training Game

© 2007 BigVisible Solutions, Inc.. All Rights Reserved

5

____ __ ____ _____ ____ ______ _____ _____ ____ _____ _____ _____ ____ _____

Click to edit Master text stylesSecond levelThird levelFourth levelFifth level

Why does it work?

► Focus on Business Objectives Deliver maximum business value

► Measure Progress in the Form of Completed Product Tested, customer-accepted product

► Build a Culture of Continuous Improvement Continuous incremental gains

► Responsive to Feedback and Learning Facilitates changes that improve product

► Maximize Team Productivity Laser-focus on delivering product

Page 6: © 2007 BigVisible Solutions, Inc. All Rights Reserved Training Solutions Agile Training Game v. 7.3.1

Agile Training Game

© 2007 BigVisible Solutions, Inc.. All Rights Reserved

6

____ __ ____ _____ ____ ______ _____ _____ ____ _____ _____ _____ ____ _____

Click to edit Master text stylesSecond levelThird levelFourth levelFifth level

The Agile Principles

► Deliver customer value early and often

► Frequent, iterative delivery of accepted product

► Embrace change

► Closely integrated team

► Minimize waste

► Strive for highest level of collaboration

► Success is built around motivated self-organizing teams

► Continuously seek ways to improve

Page 7: © 2007 BigVisible Solutions, Inc. All Rights Reserved Training Solutions Agile Training Game v. 7.3.1

Agile Training Game

© 2007 BigVisible Solutions, Inc.. All Rights Reserved

7

____ __ ____ _____ ____ ______ _____ _____ ____ _____ _____ _____ ____ _____

Click to edit Master text stylesSecond levelThird levelFourth levelFifth level

Traditional/Waterfall Process

Analysis

Design

Development

QA

Deliverable: Requirements Document

Deliverable: Design Specification

Deliverable: Integrated Code

Deliverable: Tested, Accepted Product

Typical Waterfall/Traditional SDLC

Page 8: © 2007 BigVisible Solutions, Inc. All Rights Reserved Training Solutions Agile Training Game v. 7.3.1

Agile Training Game

© 2007 BigVisible Solutions, Inc.. All Rights Reserved

8

____ __ ____ _____ ____ ______ _____ _____ ____ _____ _____ _____ ____ _____

Click to edit Master text stylesSecond levelThird levelFourth levelFifth level

Waterfall/Traditional Value Delivery

Analysis

Design

Development

QA

Analysis Design Development QA

Page 9: © 2007 BigVisible Solutions, Inc. All Rights Reserved Training Solutions Agile Training Game v. 7.3.1

Agile Training Game

© 2007 BigVisible Solutions, Inc.. All Rights Reserved

9

____ __ ____ _____ ____ ______ _____ _____ ____ _____ _____ _____ ____ _____

Click to edit Master text stylesSecond levelThird levelFourth levelFifth level

Analysis Design Development QA

Waterfall/Traditional Value Delivery

Analysis Design Development

0

QA

2 4 6 8 10 12 14 16

Value Growth: Traditional Project

Week

In traditional projects:Real value cannot be recognized during the majority of the process

In traditional projects:Value is only delivered at the completion of the QA phase of the project.

In traditional projects:Maximum value is achieved at product launch

Val

ue/

Qu

alit

y S

oft

war

e D

eliv

ered

Page 10: © 2007 BigVisible Solutions, Inc. All Rights Reserved Training Solutions Agile Training Game v. 7.3.1

Agile Training Game

© 2007 BigVisible Solutions, Inc.. All Rights Reserved

10

____ __ ____ _____ ____ ______ _____ _____ ____ _____ _____ _____ ____ _____

Click to edit Master text stylesSecond levelThird levelFourth levelFifth level

Agile Value Delivery

0

2 4 6 8 10 12 14 16Week

Val

ue/

Qu

alit

y S

oft

war

e D

eliv

ered

In Agile projects:Customer realizes value as early as the completion of the first iteration

In Agile projects:Frequent integration at the end of each iteration ensures product quality early in the product lifecycle

In Agile projects:Each iteration delivers incremental functionality intended to continuously reflect the customer chosen direction for the product

►Reduce Risk Minimize Business Risk Minimize Product Risk Minimize Project Risk

Page 11: © 2007 BigVisible Solutions, Inc. All Rights Reserved Training Solutions Agile Training Game v. 7.3.1

Agile Training Game

© 2007 BigVisible Solutions, Inc.. All Rights Reserved

11

____ __ ____ _____ ____ ______ _____ _____ ____ _____ _____ _____ ____ _____

Click to edit Master text stylesSecond levelThird levelFourth levelFifth level

The Agile Principles

► Deliver customer value early and often

► Frequent, iterative delivery of accepted product

► Embrace change

► Closely integrated team

► Minimize waste

► Strive for highest level of collaboration

► Success is built around motivated self-organizing teams

► Continuously seek ways to improve

Page 12: © 2007 BigVisible Solutions, Inc. All Rights Reserved Training Solutions Agile Training Game v. 7.3.1

Agile Training Game

© 2007 BigVisible Solutions, Inc.. All Rights Reserved

12

____ __ ____ _____ ____ ______ _____ _____ ____ _____ _____ _____ ____ _____

Click to edit Master text stylesSecond levelThird levelFourth levelFifth level

Common Agile Misconceptions

►Agile Abandons all Rigor Agile is very rigorous in its principles

►Agile does not scale Agile has been scaled to hundreds of product developers

►Agile is not for Distributed Teams Agile supports the model of multiple distributed teams that adopt the same principals and

practices

►Agile = ‘No Documentation’ Agile stresses product documentation

►Agile Focuses Cost Reduction Agile does not directly address project or resource costs

►Agile Ignores Architecture Agile stresses continuous architecture and design evolution

►Agile Means ‘No Planning’ Agile stresses the importance of short-term and long-term planning