Regroup Pres

8/3/2019 Regroup Pres

1/13

Get Ready for Agile Methods, with Care

Marc Dragon, Daniel Shi Ke,Shakya Ganguly, Julie Makelberge

February 08, 2012


2/13

Marc Dragon, Daniel Shi Ke, Shakya Ganguly, Julie Makelberge


Outline

Purpose Our ThoughtsGetting The Point Across


3/13



Purpose

Suggests a hybrid ofagile & plan-driven

methods

Educates usabout the good

and bad of each

Informs us how to

achieve the right

balanceAddress the riskmanagement for

such a blend


4/13



Comparing the Methods

Home ground for agile and plan-driven methods.

Home-ground area Agile Methods Plan-driven methods

Developers Agile, knowledgeable, collocated, andcollaborative

Plan-oriented; adequate skills; access toexternal knowledge

Customers Dedicated, knowledgeable, collocated,

collaborative, Access to knowledgeable,collaborative, representative, andrepresentative, and empowered

Access to knowledgeable, collaborative,

representative, andrepresentative, and empoweredempowered customers

Requirements Largely emergent; rapid change Knowable early; largely stable

Architecture Designed for current requirements Designed for current and foreseeablerequirements

Refactoring Inexpensive Expensive

Size Smaller teams and products Larger teams and products

Primary objective Rapid value High assurance


5/13



An objective view on both methods

Developers

Tacit knowledge?Yes.


6/13



Where plan-driven method can't be beaten


7/13



Agile method works best at


8/13



Both have their own advantages and disadvantages.

One cannot be replaced by the other.

Home-ground area Agile Methods Plan-driven methods

Developers Agile, knowledgeable, collocated, andcollaborative

Plan-oriented; adequate skills; access toexternal knowledge

Customers Dedicated, knowledgeable, collocated,

collaborative, Access to knowledgeable,collaborative, representative, andrepresentative, and empowered

Access to knowledgeable, collaborative,

representative, andrepresentative, and empoweredempowered customers

Requirements Largely emergent; rapid change Knowable early; largely stable

Architecture Designed for current requirements Designed for current and foreseeablerequirements

Refactoring Inexpensive Expensive

Size Smaller teams and products Larger teams and products

Primary objective Rapid value High assurance


9/13



How Much Planning Is Enough?

- A risk analysis approach Risk Exposure RE = Prob (Loss) * Size (Loss)

Loss financial; reputation; future prospects,

For multiple sources of loss:

RE = S [Prob (Loss) * Size (Loss)]source


10/13




11/13



Conclusions: CMMI and Agile Methods

Agile and plan-driven methods have best-fit home groundsIncreasing pace of change requires more agility

Risk considerations help balance agility and planning

Risk-driven How much planning is enough?

Risk-driven agile/plan-driven hybrid methods available

Adaptive Software Development, RUP, MBASE, CeBASE Method

CMMI provides enabling criteria for hybrid methods

Risk Management, Integrated Teaming


12/13



What It's All About

How It Makes Its Point

What We Thought


13/13



Thank You For Listening

Documents

Regroup Pres