http://jstahl.org/archives/2009/10/13/even-more-sprint-wisdom/ Politics, the environment, technology, activism. And stuff. Sat, 13 Mar 2010 22:49:31 -0800 http://wordpress.org/?v=2.9.2 hourly 1 http://jstahl.org/archives/2009/10/13/even-more-sprint-wisdom/comment-page-1/#comment-394252 Tweets that mention Jon Stahl's Journal » Blog Archive » Even more sprint wisdom -- Topsy.com Tue, 13 Oct 2009 16:22:25 +0000 http://jstahl.org/?p=1976#comment-394252 <p>[...] This post was mentioned on Twitter by enzus. enzus said: RT @diefenbach:Nice write-up about sprinting: http://bit.ly/2Dvi5K [...]</p> [...] This post was mentioned on Twitter by enzus. enzus said: RT @diefenbach:Nice write-up about sprinting: http://bit.ly/2Dvi5K [...]

]]> http://jstahl.org/archives/2009/10/13/even-more-sprint-wisdom/comment-page-1/#comment-394251 Chris Calloway Tue, 13 Oct 2009 16:02:46 +0000 http://jstahl.org/?p=1976#comment-394251 <p>Ah, glad to see my spelling errors were cut and pasted intact. :) (Finally, got them fixed in the linked post.) Just want to comment on the description of ZopeSkel as "the code generator for Plone integrators and developers." It has been heavily developer-centric, naturally, because it came from developers. The purpose of the sprint was to somewhat add a space in ZopeSkel for themers and integrators as well. Some of the sprinters were selected specifically because there were less developer-centric and had more experience with themers and integrators on the ground. I felt the need to list the lessons learned because this was the most insanely productive sprint I've ever seen or heard of. I had no idea going in that it was going to be like it was and thought it was going to be some kind of disaster. Keeping it small, focused, and selective were the three most important things. We called it the "No-Fun" sprint because we wanted to emphasize the sprint would be about work and results rather than about having a sprint vacation. But we managed to have a lot of fun because it is fun to see results. That and the BBQ.</p> Ah, glad to see my spelling errors were cut and pasted intact.
(Finally, got them fixed in the linked post.)
Just want to comment on the description of ZopeSkel as “the code generator for Plone integrators and developers.” It has been heavily developer-centric, naturally, because it came from developers. The purpose of the sprint was to somewhat add a space in ZopeSkel for themers and integrators as well. Some of the sprinters were selected specifically because there were less developer-centric and had more experience with themers and integrators on the ground.
I felt the need to list the lessons learned because this was the most insanely productive sprint I’ve ever seen or heard of. I had no idea going in that it was going to be like it was and thought it was going to be some kind of disaster. Keeping it small, focused, and selective were the three most important things.
We called it the “No-Fun” sprint because we wanted to emphasize the sprint would be about work and results rather than about having a sprint vacation. But we managed to have a lot of fun because it is fun to see results. That and the BBQ.

]]>