BRIDGING THE

RAD-TO-AGILE GAP

Mark Hutchinson, ICP

Presentation at TriAgile 2016 conference

June 30, 2016

version 1.0

Introduction

• Mark Hutchinson

– ICAgile

Professional

– Consultant in

Durham, NC

– Been there. Done

that.

Introduction

• This presentation

– What I see

– What you can do as

an Agilist

– What not to fear as a

manager

Introduction

• Agenda

– History

– Definitions

– RAD

– Agile

– Benefits & Goals

– Tools

– Bridging the gap

– Conclusion

History

• Fred Brooks

– Earliest work at IBM (1950s)

– Mythical Man-Month

– o Silver Bullet

– The Design of Design

• CASE tools (1982+)

• James Martin (1991)

History

• UI wars (1992+) - (GUIs and browser)

• Model-Driven Engineering

• XP (1996-1999)

• Agile Manifesto (2001)

�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.

History

• All those Agile Frameworks and stuff

– Scrum

– “Scrum is not Agile and Agile isn’t scrum” - DH

– Kanban

– SAFe

– ICAgile

– Lean

– DevOps - sort of

• GROWS - back to basics (2015)

Definitions

• RAD

• Agile (1994)

• Frameworks

– how we implement Methodologies

Definitions

• Similar to Agile

– Kanban

– Lean IT/Lean Software Development

– Crystal Clear (mid-1990s)

• https://en.wikiversity.org/wiki/Crystal_Methods

• Methodologies – guiding principles

– The Original Agile Manifesto

– GROWS

© 2016 The GROWS™ Method Institute www.growsmethod.com

GROWS is...

© 2016 The GROWS™ Method Institute www.growsmethod.com

• Inspired by Dreyfus Model of Skill Acquisition

• Driven by Intentional Experimentation

• Everyone is included from executives to customers

• Achieves instant results with Tracer Bullet

Development

• Steers with the Right Thing, Right Way, Right

Rhythm

© 2016 The GROWS™ Method Institute www.growsmethod.com

Empirical

• Experiments for

process adoption

• Experiments to

answer technical

questions

© 2016 The GROWS™ Method Institute www.growsmethod.com

Empirical• Experiments are:

• Cheap to run

• Very short term, with a time-boxed deadline (no more

than a few weeks at most)

• Generate specific, measurable outcomes of value

• Conditions of test and outcomes must be agreed by

the team/involved parties

• Only include a subset of the team if you can

• No experiment fails; all experiments generate data to

inform the next experiment

© 2016 The GROWS™ Method Institute www.growsmethod.com

Steady, Nested

Rhythms

From Practices of an Agile Developer,

by Dr. Venkat Subramanium and

Andy Hunt

RAD

• Best/Appropriate Uses

• What Does PMI think?

– Great if fast is your primary goal

– Single or individual (autonomous) teams

• Pros

• Cons

• Tools

Agile

• Best/Appropriate Uses

• Pros

• Cons

• Tools

Tools

• Model-Driven development

• Tests and Behaviors

– TDD

– BDD

• Source code control and versioning

• Communication

Synonyms

• Retrospective = Post Mortem

• Sprint = Iteration

• Principal = User

• Tracer Bullet = Proof-of-Concept

• Experimentation = Prototype

Squinting at Agile, I see

• User-centric requirements and approval

• Short iterations and cycles

• Working results - minimal viable product

Bridging the Gap

• Find the means/path to

– the fastest iteration cycles at all stages of

development (design, coding, testing, etc.)

– the least amount of team overhead (fewest

people required)

– the least amount of developer overhead (think

lean principles and lean time tracking)

– the quickest path to a minimal viable product

(MVP)

Conclusion

– Thank you

– Thanks to Jared and Andy

– Thanks to our conference sponsors

– Slides and links available at conference site

– Any final questions?