Re: Roll Your Own Agile?

"Adam Sroka [email protected] [SCRUMDEVELOPMENT]" <[email protected]>
Newsgroups gmane.comp.programming.scrum.general
Message-ID <CALaPUVdb_x0hVyOv1wxr3ZdGPgQu=BO9L=SKXPsJyQfyOKGX3Q@mail.gmail.com>
Historically all of the “established Agile methods” were “RYOA” before
there was an “A.” Before Snowbird they were calling them “lightweight” but
nobody really cared for that.

More to the point, I think that any method that has been mindfully applied
and adapted to a particular team/product/organizational context will look
different from every other one. If your Scrum continues to be by-the-book
Scrum after months or years then your retrospectives are probably a waste
of time.

One of the problems I have with the current status quo in the Agile
consulting industry is that we send out consultants who don’t know the
difference between useful adaptations and “not doing it right.” That takes
a number of years to cultivate and a deliberate discipline of listening
before giving advice.


On Tue, Nov 24, 2015 at 11:06 AM, Charles Bradley - Professional Scrum
Trainer and Coach [email protected] [SCRUMDEVELOPMENT] <
[email protected]> wrote:

>
>
>
> I define "Roll Your Own Agile" (RYOA) as roughly ~~ being an attempt at
> being/doing Agile software development that is not based on(or has a
> history of) one of the major well defined Agile approaches (XP, Scrum,
> Crystal, AUP, etc, et al.)... (for purposes of our discussion, let's
> consider Kanban as a well defined Agile approach -- even tho that might be
> highly debatable by some-- but let's not get distracted/hijacked by that
> side conversation!)
>
> For instance, I don't really consider Spottify RYOA since what they do is
> very close to Scrum, and I believe they started out with Scrum. (CMIIW)
>
> I would assume that anyone out there trying to do RYOA would be basing
> their approach almost solely on the Agile Manifesto principles and
> values... a sort of "clean room" approach if you will.  (Obviously all of
> the well defined approaches probably started as RYOA, but I'm not
> interested in those)
>
> (Remember, I'm talking only about software teams here)
>
> Has anyone out there in Scrum-land ever seen what you consider to be a
> good RYOA approach work out well for a company?  Or is RYOA essentially a
> unicorn?
> -------
> Charles Bradley
> Chief Executive Officer
> Professional Scrum Trainer
> http://AgileSoftwareTraining.com <http://agilesoftwaretraining.com/>
> Agile Software - Training, Consulting, Coaching
>
> 
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.