Open Stack

On 04/24/2013 02:26 PM, Russell Bryant wrote:
> On 04/24/2013 02:13 PM, Kurt Griffiths wrote:
>>> but if one of the lenses you look at it through is "how can the
>>> openstack infrastructure, process or tooling be improved" I'd greatly
>>> appreciate it!
>>
>> Sure thing. Right now I'm using blueprints as a nexus, tying things
>> together (wiki, trello, etherpad), but what I haven't found (yet) in the
>> OpenStack ecosystem was a de-facto way to manage day-to-day work given a
>> scrum-style process.
>>
>> I think it's healthy to experiment with a few different ways to do things,
>> learn from that, and merge useful bits over time.
> 
> My concern with this type of process in an open source project is that
> it comes with fundamental assumptions that just aren't true.  For
> example, you can't assume that the people working on the project can be
> available for a daily standup due to other commitments, time zones,
> whatever.  You also can't assume that someone's availability to work on
> tasks is consistent, so sprint planning is ... challenging and less
> useful.  Contributors just aren't resources that you control.
> 
> The end result that I'm afraid of is that you have some contributors
> 'in' the process and others that aren't, making it a less inviting
> project to get involved with.

I also had those concerns as soon as you said the word Scrum - which I
believe, while a valid approach, is generally speaking a different
approach from how Open Source projects usually work. The biggest issue
there is the "in" vs. "out" of the project that Russel brings up. If you
have a stand up call, then the folks who are on IRC are not in that
call, etc.

> I'm obviously a bit pessimistic, but by all means experiment and report
> results.  :-)

I concur. There is actually, thus far, no existing solution that marries
Agile with Open Source. It's possible you'll find something. :)