...
 
Commits (6)
# 20% project # OlinData time
We have a 20% rule that was copied from Google's engineering team: you are allowed to spend 20% of your time (effectively one day a week) on some project that is not highest priority, and it can be anything you come up with, as long as there is some perspective of usefulness for OlinData (in the widest sense of the word). For instance (and this is just an example), Walter happened to have registered a domain called <http://divesitebuddy.com> years ago, which in his mind was going to be a tripadvisor for divesites worldwide. Richard, our Drupal expert back then took on himself to start designing and building this website and he blogged about his experiences weekly. Go and search back in the blog history if you want to see some of the results. If you think that that is what you would love to spend some time on, you could do that for your 20% work. Also, the 20% project is optional. If you feel like you want to not make use of the opportunity, that's cool too.
You're free to divide the number of hours assigned anyway you want. That said, it would be nice if you spread things out a bit. If you work better in evenings, mornings, weekends, etc. That is fine with us. The communication part we listed in [culture] should make it possible for us to work asynchronously. Most of us spend less than fulltime at projects with our clients. The rest of your time is called OlinData time and this page explains what it is and how we go about managing it.
# How do we organise this? ## Origin
It is important to us that you take the maximum advantage of the 20% rule and we are very interested in helping you to achieve this. Before you can get started with your project, we ask that you write up a small proposal on what you aim to work on. Discuss that with your direct lead for approval so we can determine together if and how this would work. We do this using periodic meetings where we discuss your next 20% project or follow up on your current progress. These meetings are used to set short-term goals regarding the 20% project. The meeting frequency is open to personal preference but we advise to have, at least, one each trimester.
# Goal Setting Originally, we copied the 20% project rules from Google's engineering team: you were allowed to spend 20% of your time (effectively one day a week) on some project you defined by yourself or with coworkers
We use Bamboo's functionality to keep track of the current progress, it is very important that you take your time to update your progress frequently. In Bamboo it is also possible to write comments about your goal. For instance (and this is just an example), Walter happened to have registered a domain called http://divesitebuddy.com years ago, which in his mind was going to be a tripadvisor for divesites worldwide. Richard, our Drupal expert back then took on himself to start designing and building this website and he blogged about his experiences weekly. Go and search back in the blog history if you want to see some of the results. If you think that that is what you would love to spend some time on, you could do that for your 20% work.
# Content production ## OlinData time projects are managed like any other project
One of the greatest overall perks of the 20% project is to have a shareable outcome, perhaps in the form of blog content. This content can also be a knowledge sharing session, a mini-project or even internal wiki track about the topic.
It is important to us that you take the maximum advantage of the OlinData time rules and we are very interested in helping you to achieve this. Before you can get started with your project, we ask that you write up a small proposal on what you aim to work on. Discuss that with your direct lead for approval so we can determine together if and how this would work. We do this using periodic meetings where we discuss your next OlinData time project or follow up on your current progress. These meetings are used to set short-term goals regarding the OlinData time project. The meeting frequency is open to personal preference but we advise to have, at least, one each trimester.
Each OlinData time project will have a manager (this is usually just the person who manages the OlinData time projects across the company or your direct lead)
## SMART
In order for your (and our) time to spend as optimal as possible it's important that the whole project is defined in a [SMART](https://en.m.wikipedia.org/wiki/SMART_criteria) way. Please hop over to wikipedia to read more on S.M.A.R.T. if you're unfamiliar with the term.
## Budgets for larger projects
In this situation and assuming there is a large project that you want to implement... before you set up a meeting with your project manager do a POC with an estimated budget
the project manager job is to give you the freedom and move out the way all the approvals you need (like budget and free time )
(For now we have only one project manager....[Gavriel Amira](@Gavriel))
# Personal development
Normally we use mavenlink to administer the goals and tasks for these projects, but if you fill your OlinData time with purely personal development like for instance studying for a certification you should also speak with your direct lead and add the goals to [bamboo](software-and-saas.md)
# sharing results
We love it when you share results. This can be on [friday's](fridays.md) or during a conference talk, meetup session or a webinar.
# Documentation
This will only work when everything we do is documented, that will bring us the transparency we need.
And of course if you're just tinkering with something for a day it doesn't matter that much.
\ No newline at end of file
# Knowledge sharing
We are an incredibly diverse and highly experienced team. While on
assignment, and during our OD-days we learn, and create amazing
things. To inspire and teach each other we organize a sharing
activity every week on [fridays](fridays.md). We all have something to share, so everyone is
required to present something once every cycle.
The schedule is managed in this shared google calendar:
https://calendar.google.com/calendar/embed?src=olindata.com_al1t8ln0iqmolkkd9diqi4jm3c%40group.calendar.google.com&ctz=Europe%2FAmsterdam
In preparation of this event we'd like you to come up with a subject
at least a week in advance. If you have any trouble thinking of
something, or need help preparing a talk don’t hesitate to ask for
help from any of your colleagues. There aren’t much restrictions to
what you can present, but the talk should preferably be at least 15
minutes unless there is good reason not to. A good session should take
30-45 minutes in total, with a maximum of an hour.
...@@ -19,23 +19,7 @@ space. ...@@ -19,23 +19,7 @@ space.
# Knowledge sharing # Knowledge sharing
We are an incredibly diverse and highly experienced team. While on see [Knowledge sharing](knowledge-sharing.md)
assignment, and during our OD-days we learn, and create amazing
things. To inspire and teach each other we will organize a sharing
activity every week. We all have something to share! So everyone is
required to present something once every cycle.
The schedule is managed in this shared google calendar:
https://calendar.google.com/calendar/embed?src=olindata.com_al1t8ln0iqmolkkd9diqi4jm3c%40group.calendar.google.com&ctz=Europe%2FAmsterdam
In preparation of this event we'd like you to come up with a subject
at least a week in advance. If you have any trouble thinking of
something, or need help preparing a talk don’t hesitate to ask for
help from any of your colleagues. There aren’t much restrictions to
what you can present, but the talk should preferably be at least 15
minutes unless there is good reason not to. A good session should take
30-45 minutes in total, with a maximum of an hour.
# Weekly overview # Weekly overview
......
# Knowledge sharing
We are an incredibly diverse and highly experienced team. While on
assignment, and during our OD-days we learn, and create amazing
things. To inspire and teach each other we organize a sharing
activity every week on [fridays](fridays.md). We all have something to share, so everyone is
required to present something once every cycle.
The schedule is managed in this shared google calendar:
https://calendar.google.com/calendar/embed?src=olindata.com_al1t8ln0iqmolkkd9diqi4jm3c%40group.calendar.google.com&ctz=Europe%2FAmsterdam
In preparation of this event we'd like you to come up with a subject
at least a week in advance. If you have any trouble thinking of
something, or need help preparing a talk don’t hesitate to ask for
help from any of your colleagues. There aren’t much restrictions to
what you can present, but the talk should preferably be at least 15
minutes unless there is good reason not to. A good session should take
30-45 minutes in total, with a maximum of an hour.