Check out the video below, which gives an example of the 10 minute / 1 minute / 10 second challenge (you can check out more of them here).
When given 10 minutes to sketch Spiderman, the result is far richer than when the artist is given only 10 seconds… well obviously!!
But let me pose a question. If Sketch B was compiled from 60 sequential 10s updates (ie Sketch B would also take 10 mins total sketching time) do you think the final sketch would look as impressive as the 1 x 10 min sketch (Sketch A)? The total sketching time is the same, but will the results be similar?
From the 10s sketch above, you can see that the composition is not as precise. Subsequent updates would have to work around the initial structural flaws.
Do you wonder whether this is somewhat analogous to creating OSS using continuous development frameworks like Agile or DevOps? By having tightly compressed (eg weekly) release cycles, are we compromising the structure from the start?
I’m a big believer in rapid prototyping with subsequent incremental improvements instead of the old than big-bang OSS delivery model. I’m also impressed with automated dev / test / release frameworks. However, I’m concerned that rapid release cycles can enforce unnecessary deadlines and introduce structural compromises that are difficult to fix mid-flight.Read the Passionate About OSS Blog for more or Subscribe to the Passionate About OSS Blog by Email