I've never met anyone who has this luxury, quick poll: Do you have 20% time?
If we are hitting targets, yes
Making 20% Time Work
11–20 of 142 posts
Re: Making 20% Time Work
#12I love this BASEDEF acronym. I have an IRC bot that I've been working on for 3 years on Github. I've also tossed it on up-for-grabs.net. About 7 people have submitted contributions, I think because of up-for-grabs.
I think that acronym perfectly describes what a successful open-source project needs to thrive.
Re: Making 20% Time Work
#13I've never met anyone who has this luxury, quick poll: Do you have 20% time?
no
Re: Making 20% Time Work
#14I've never met anyone who has this luxury, quick poll: Do you have 20% time?
If I sandbag estimates
Re: Making 20% Time Work
#15I've never met anyone who has this luxury, quick poll: Do you have 20% time?
I don't even have 0% time.
Re: Making 20% Time Work
#16I've never met anyone who has this luxury, quick poll: Do you have 20% time?
Our old CTO used to laugh (somewhat derisively) if anyone asked.
No.
Re: Making 20% Time Work
#17Love the idea of trying to a) make 20% time better and b) encourage it to be open source. Wonderful stuff!
Re: Making 20% Time Work
#18I've never met anyone who has this luxury, quick poll: Do you have 20% time?
Not formally. However, if I was getting my job done and was productive, I don't think anyone would complain about 20% time. Although my employer is quite flexible and I have unlimited vacation as well, though that is a privilege and not a right, of course.
Re: Making 20% Time Work
#19We have successfully pulled off 20% for 5+ years now at Kiva, doing some of the things suggested here.
However, the key thing we do is actually make the 20% be a full two-week sprint, it just happens every 5th sprint. That way, you can have the time to do some planning, suggesting, and documentation before setting out to build something and you get the full amount of time you needed to build it. We purposefully do try to keep features limited to something shippable during that time period, though some folks will spread it out over a few for bigger efforts. It's pretty great and a key part of our culture that I'm happy we've been able to keep. It's also produced some of the best features Kiva has (as well as served as a great time for engineers that like to tidy things to clean up the codebase).
http://pages.kiva.org/buildkivablog/2011/02/10/kiva-engineer...
Re: Making 20% Time Work
#20We have successfully pulled off 20% for 5+ years now at Kiva, doing some of the things suggested here. However, the key thing we do is actually make the 20% be a full two-week sprint, it just happens every 5th sprint. That way, you can have the time to do some planning, suggesting, and documentation before setting out to build something and you get the full amount of time you needed to build it. We purposefully do tr…
I like the idea of every 5th sprint being devoted to this – a day week is barely enough to just switch context and get into gear. I can see how getting a couple of days distance between "real" work and the 5th sprint would be beneficial just to clear your mind and start fresh, knowing there are two glorious weeks of focus ahead.