Project In A Week / development bootcamp [closed]

Question

Our team is thinking of doing a "Project In A Week" (bootcamp), and I'm interested to know if anyone else has experience of doing this or has any advice?

The idea behind it is to get away from the distractions of the office, motivate each other, and build our bonds within the team, in order to come up with an innovative and profitable product in a short space of time.

The plan is to get the whole of the dev team (about 5 devs), a designer, a project manager, couple of sales and marketing people staying in a conference centre/hotel for a full working week. We'll be completely focused on building one web app (planned in advance) and getting it live and on the market within the week. We'll work quite long days but in the evenings we'll have some fun together as a team. There would be a couple of members of the team left in the office to ensure we're not distracted by day to day client support. Similar 'immersive' approaches are used by training companies such as Firebrand.

Good idea? Terrible idea? What should we do to incentivise the team?

Any thoughts/experiences/advice would be greatly appreciated.

Cheers

Answer 1

I was on the "Coding by the Sea" team from Red Gate that thecoop mentioned.

I, and I think everyone else on the team, had an absolutely amazing time, and I'd be first in line to put my name down to do it again. We built the beta version of SQL Search, a relatively small tool, from scratch in a week, though it was certainly of beta quality and not ready for general release at that point.

Here's a few caveats I remember from our debrief:

• There were four of us on the team: 2 developers, one tester, and one UX specialist. We thought that five might work, probably adding a second tester, but six or more would start to become rather less useful. Once you get up to that kind of team size, you start needing some kind of project management, but with four of you, you can self-organize very effectively. I'm not sure having a project manager on this kind of thing would work!

• Having some kind of idea of what you're doing before you go is good, and we spent a day or so beforehand speaking to those within the company who wouldn't be on the team getting their input. This was really valuable! However, don't go with a rigid spec, as a) it takes a lot of the fun out, and b) it'll change anyway. We spent the first morning brainstorming the design and requirements, but kept them flexible throughout the project.

• Remember you need to organize infrastructure: we all took desktop PCs so we could easily run multiple monitors - don't scrimp on this, or you'll cause your developers unnecessary pain. How will you access other bits of the office infrastructure? Build systems? E-mail? Who on the team will put this together?

Answers to some of the questions raised by others - this is what we did; it worked for us; it might not work for you:

• Meals: we were in the house for six nights. The first night we did pizza for speed, another night we went out into town for a curry, and the remaining four we each cooked a meal for everyone else. This worked really well, and we all enjoyed both cooking and eating. For breakfast / lunch we just got a selection of stuff that meant we could throw together something appropriate. If you do this, all go shopping together at the start of the trip, and needless to say, the company pays! (That included a few bottles of wine, by the way. Don't be silly and set limits on how much they can spend: if you can't trust them not to be silly, you shouldn't be doing this...)

• Compensation: we didn't get paid for overtime, or time off in lieu. As part of the team, I didn't even consider for a moment that I should do. It was a totally amazing experience, and I know there were loads of people in the company who would have loved to go if any of us hadn't. I appreciate that some may have family commitments, and this could be problematic. If you think you'd enjoy or benefit from the experience, do it - if not, don't.

• Time: I think a week (5 working days) is about right. We arrived on the Sunday evening, and spent that just getting settled in and set up, then a bit of relaxation. We left the following Saturday morning after packing up, leaving us Monday through Friday for the actual project. There's no way we could've sustained what we did for two weeks, but any less than a week, and I think you'd be very limited in what you could achieve. I don't think a team hand-over would work.

• Productivity drops after 40 hours: for a week in isolation, we didn't find this to be too bad. Could I sustain it indefinitely? Certainly not. But for one week, running on adrenaline, coffee, and great teamwork, it worked. Though the code written at midnight after a couple of glasses of red wine did need a little attention the following morning ;-).

• Accommodation: make it amazing. Not some dodgy conference venue. Find the most amazing house, in the most beautiful location you can. We had a TV the size of a small planet (that never got used), a wood burning fire, a table football table, enormous kitchen, and definitely a bedroom each! It was in the middle of nowhere, and that was great too.

There's a very brief video we did of our adventure here, if you're interested: http://www.youtube.com/watch?v=29yz3v1OCIE

Cheers, Rob

Answer 2

I think that if you tried to pull me away from my family and all my personal responsibilites for an entire week of work promsing unpaid overtime and forced interaction with my co-workers I would do my best to opt out.

I like a lot of my coworkers, but there is no way your whole team likes each other that much.

If you have a bunch of single employees this might work.

Maybe if the location was amazing, and the activities planned had wide appeal, and you invited families along and paid for them to stay the weekend.

Answer 3

I like the idea and would love to participate in something like this, but in order to have that option, you would have to incentivize it heavily with time (not just money!). Keep in mind that, by having me stay overnight, you are also making my husband work overtime to care for our children. If you have primarily single or childless employees, this may be less of an issue. Also, if your employees all expected to travel and be away from home for the occasional week when they took their current positions, this would be less of an issue.

My idea of good compensation for this would be a week of vacation (which would also help me recoup from the overtime) and a bonus so I could afford to do something nice with the family . . . and bribe my husband to go along with this.

I would want a very clear plan for what we will do before we leave . . . basically, all the sprint planning (or other estimation techniques) gets done before we leave, with clear estimates.

Having one evening where the company treats us to dinner out with our entire families (if the event happens locally) could do wonders to keep me from worrying about my family by the end of the week.

I would much rather do a two-day event (suggested by someone else) during the week than on a weekend. My weekends are booked solid with family and church events. If you do choose a weekend activity, don't forget to leave time for religious obligations.

If your employees have to work overtime regularly already, this could backfire. Make sure the week before and the week after are fairly light so they start fresh and have time to recoup afterward.

ETA: I'm aware that my requirements to do something like this might be high. I'm offering them mostly to give an idea of how the employees for whom this would be most difficult might feel about spending a week away from home for a training exercise like this.

Answer 4

Personally I would not want to do something like that. In the first place, this would cost me as I would have to get a dog sitter. In the second place, my off-time is mine. I need it and I need to be away from co-workers. I have art classes and other activities I'm not willing to give up. Then there's the exhaustion factor. If you want me to come to a hotel and work well past my normal hours, no thanks. Tired people make mistakes, it is stupid and short-sighted to plan to work extra hours. Then what will the week you return and the week before you go be like? Extra work spent to get things in shape to leave for a week and come back to a whole host of things that didn't get done that are urgent. No thanks.

Maybe this sounds like fun to some young single guy, but to me it sounds like organizational torture.

Oh yeah, I forgot, so this once and they will expect you to be able to pull off all future development in a week as well. I'd consider this point very carefully if I were you.

Answer 5

While I can understand there being good intentions behind this, I'm not sure I'd see this working well in a lot of cases. Here are some initial questions, comments, and concerns:

1. How detailed out is that "planned in advance" part? There seems to be the want of "innovation" but with a specific time line that I'm not sure the world works that way. What if there isn't a shippable product at the end of the week?

2. No analysts. Is there a reason for having no testers, business analysts, and system administrators in on this?

3. "RSA Animate - Drive: The surprising truth about what motivates us" does mention a software company that gave employees 24 hours to do whatever they wanted to do that may be a better idea than trying to have someone be creative but within a box.

4. How would meals be handled in this arrangement? What about dietary restrictions or limits?

5. Would there be set working hours for the project or is this open to the team to decide? Some people may want to work really long days in a consistent push and others may prefer spurts.

6. How would the sleeping arrangements be structured,e.g. would there be pairs in hotel rooms or is each in their own room? For example, I sleep with a CPAP machine that was somewhat surprising to the person that I shared a room back in January which may or may not make this an easy thing for me to just up and go for a week away from the world.

---

Back in 2000, my boss and I went to a conference for a week in LA and shared a hotel room. I'm pretty sure he didn't enjoy getting first hand experience with my snoring capabilities. Thus it did happen to me but I'm not sure how likely I am to have that happen in the future.

Another thought is what kind of follow-up would be done to see what changes there are in relationships and process that could be taken from that week? While some of these intangible benefits may continue as relationships have changed, it may be worth noting them somewhere to acknowledge which lessons were learned on this kind of exercise.

Answer 6

I have no experience with doing it as a full week in a company environment. I've done some dev camps and taught at one, and they're great. Those typically run for a weekend. You start Friday night, you finish Sunday night. In between, you meet people, form a team, sort out an idea, and build something. It's at least educational, and it can be great fun.

I think part of what makes those work is that everybody present is doing it for fun. So don't force people, and don't pay people extra to do it. Figure out how to make it so exciting that you'll have to turn people away. And then, as others suggested, make it painless for them, so they have nothing that interferes with working.

Answer 7

I would split into 2 teams, each working 2 days. This makes it easier to cover back at the office, have enough time to complete the project and not burden everyone by being away for a week.

You also get the benefit of learning to build things so the next/another person can work with it and possibly take over. This is true for marketing & sales people who inherit closed or nearly closed accounts.

Now it sucks being the second team. You could just ask for volunteers without them knowing it. Have a contest to pick who gets to be the first team. Of course the second team gets final say in the project, so that may be a benefit. They could just redo everything.

Spend the last day with both teams together and debrief/fight it out.