[OSList] FAST Agile - A proposed experiment for a new Agile Scaled Method built on OST

[Ron Quartel via OSList]

Hi everyone,

Last year at the Scrum Gathering in New Orleans, the last day was an Open
Space. It was not my first exposure to OST and I was already in love the
format the from my first experience at an Agile Open Northwest conference
years before. But what was different this time was the realization that no
one has yet used this proven technology to organize software development on
a large scale. And so was the birth of an idea for such a methodology.

After running the idea by some small groups earlier this year - Agile Open
Northwest 2015 in Portland, The Scrum Gathering Phoenix 2015, a Seattle
SaFE meetup, I was encouraged to proceed with the idea and began piecing it
all together into a methodology/framework (frameology?).

Last week at the Agile Roots conference in Salt Lake City I made the
official launch of FAST with my presentation there. You can see the slide
deck over at
http://www.slideshare.net/RonQuartel/continous-deliver-and-agileatscale
though you will not get much from these as most of the content was on the
white board, demonstrations, conversations and Q&A. (I'm not a big fan of
slide heavy presentations.)

At the same time I launched a Google group (FAST Agile), a website
http://www.fast-agile.com and a twitter account with hashtag @FAST_software
#FASTAgile. The website is in minimal viable state still and I wouldn't be
surprised to find that there are some mistakes in there. But I will be
spending time tending this garden and bringing it to bloom hopefully as
this is my new baby and passion.

FAST differs to Daniel Mezick's Open Agile Adoption as they have a very
different focus. As I understand it (and please feel free to correct me
Daniel), Open Agile Adoption uses OST as the means for helping with the
transformation of an organization to adopt an agile method - Scrum. FAST
uses OST as a replacement for Scrum. So you could in fact use Daniel's Open
Agile Adoption to implement FAST. FAST relies on the strengths of OST to
essentially ensure self organization, collaboration and a pull model of
work. All things that scrum pays lip service to but seems to fail at
actually implementing time and time again. (As well as Code Craftsmanship
which I have addressed by building it in as a core value.)

Don't get me wrong about scrum. The theory is good and if done well
produces good results. But as an agile coach I rarely have seen Scrum done
well and so was inspired to create a methodology that will not lend itself
to be so poorly implemented time and time again.

FAST uses a variation of OST. You will recognize the inspiration behind the
values and principals directly attributed to OST's principles and strengths
:-

FAST Values

   - Face to face communication (includes/implies *Collocation*)
   - Code Craftsmanship (includes/implies Code Quality and *Technical
   Excellence*)
   - Self-organization (includes/implies *Trust *and *Collaboration*)
   - Shared vision (includes/implies *Shared Single Purpose* and *Alignment*
   )




FAST Principles

   - The right people will work on the right stories
   - The right discussions will happen at the right time, with the right
   people to resolve dependencies and emerge the design
   - Whatever happens, is the only thing that could have
   - Stories will start and be completed at the right time and in the right
   sequence



FAST stands for Fast Agile Scaled Technology. The Technology refers to OST.
I'm not really pushing the acronym aspect to the name so you won't see it
published anywhere but wanted to share it with this small group.

I hope you like FAST, will join the FAST community and help evolving it
into the methodology that produces software faster than anything on the
planet today!

Ron Quartel
Summer Solstice 2015
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openspacetech.org/pipermail/oslist-openspacetech.org/attachments/20150621/ac833891/attachment-0002.htm>