[Python-ideas] Iterative development

anatoly techtonik techtonik at gmail.com
Thu Jan 30 13:52:43 CET 2014


On Wed, Jan 29, 2014 at 7:27 PM, Chris Angelico <rosuav at gmail.com> wrote:
> On Wed, Jan 29, 2014 at 11:48 PM, anatoly techtonik <techtonik at gmail.com> wrote:
>> You don't need to work full time to participate in two week cycle.
>> As I answered to Ethan, it is not development cycle time. It is just
>> ordinary two weeks time. You choose what you can do in these two
>> week and do this. You may find that you have more time than you've
>> planned during this time, so you can see who is working on what
>> and help them (if possible).
>
> What does the two-week cycle achieve that current processes with the
> bug tracker can't?

More fun with collaboration. For some people it is not fun to grok the bugs
they don't personally need to be solved. Sometimes because of complexity
of the problem, but helping some else may be fun.

Current bug tracker doesn't show:
1. what is important for people who think like you are
2. what is the current development focus

So you can not plan how to spend your time more effectively and how to
help with development.

> Please explain to us the benefits of the Agile model, as they apply to
> a loose collaboration.

As I said, there is no single Agile model. Model can be agile (adapting, willing
to change, flexible), natural or rigid.

In rigid model you don't have choice. Take the bug, commit, release.
In natural model you may have additional and optional steps.
In agile model, you have a feedback loop that allows to estimate how
good the model actually is and experiment with it to see if it can be
better.


More information about the Python-ideas mailing list