Scratch

If this doesn't belong in Collabs, please move it.

I made this topic because a lot of collabs don't do well. I'm writing from experience. I can't tell you how many collabs that were 3D, multiplayer, or had some other difficult concept failed. The collab owners realize that it won't succeed. I would like to prevent this from happening to other Scratchers in the future. However, I don't want to discourage people from attempting such projects. They should just take caution when doing so, and incorporate some tips discussed to help gain success.

Section 1) Introduction
A lot of collabs are huge. And yet, a lot of collaborations don't get very far. The reason? The scale. I have nothing against high-expectations, but if you're goals are too high, the project will never get done. This guide will provide some tips on making successful collabs, especially large-scale collabs. I'll also provide some tips on making large-scale projects more efficient, whether it's a collab or not.

Section 2) Why large projects often fail.
The answer is very simple, actually: a lack of resources. Whether the resources that the collab may be lacking is programming skills, art skills, time, good ideas, or whatever else, the lack will push the project back. In a normal collab, this just won't happen. The reason for that is a bit more complex. But the simple answer is complexity. In a small project, the collab will require less resources, and the required resources will be more common. For instance, if you are making a 3D game, your resources might be the best programmers on Scratch. But if your making pong, you could do with any new scratcher. Who's collab is more likely to succeed? Clearly, the pong collab.

Here's a scenario: You run a collab for a 3D FPS, which is one of the hardest Scratch games you can attempt. You have a dozen team members who all master whatever job they are taking on. Your collab started great, and the first draft of the prototype is epic. You're so impressed that you decide your team should take a little bit of rest from the collab. When you come back from your mini-vacation, development halts.

The reason for development halting isn't completely a lack of resources. As a matter of fact, your prototype had all the resources it needed. But the vacation changed some resource drastically. In real life, things happen. People fall in love, people die, people change, and in some ways, that applies to your collab, too. You can't plan for your head programmer to quit and still expect your collab to succeed. The truth is, it won't. But the reason for something drastic like this to happen to your collab isn't always clear.

Section 3) Knowing if you're project might fail
Before you can prevent your project from failing, you need to know whether it will fail. Make sure that your project doesn't require things that you cannot provide--I've seen collabs where it's a new Scratcher leading...and attempting 3D, multiplayer, or some other tremendous task. I'm not saying you need to master everything, just make sure that you have mastery in something, and that you have a little skill in others. (I love programming, but I still pass Art class)

Once you know that you can do most tasks moderately, it's a matter of who else can. Try judging how hard your collab is, on a scale of 1-10, 1 being pong, 10 being MMOFPS. (that'd probably be an 11) Here is a quick table of success I put together

+--------------------------------------+                                       
|     Number       |      Chance|                                       
+--------------------------------------+                                       
|        1         |        95%        |                                       
+--------------------------------------+                                       
|        2         |        90%         |                                       
+--------------------------------------+                                       
|        3         |        85%         |                                       
+--------------------------------------+                                       
|        4         |        80%         |                                       
+--------------------------------------+                                       
|        5         |        60%         |                                       
+--------------------------------------+                                       
|        6         |        40%         |                                       
+--------------------------------------+                                       
|        7         |        20%         |                                       
+--------------------------------------+                                       
|        8         |        10%         |                                       
+--------------------------------------+                                       
|        9         |        5%          |                                       
+--------------------------------------+                                       
|       10         |        1%          |                                       
+--------------------------------------+                                       
                                                                                 
If you're project has a low percentage on the table, you might want to re-think your collab. Anything under about 50% requires special care, and under 20%, you need to be an expert.


To be continued

Last edited by bobbybee (2012-03-09 18:30:49)