This is an interesting idea... One I see a real need for. Some of these features are available on CH already, but you seem to have improved upon them. Good work. I'll be voting this one up in the next round! =]

I like it too
Tommy

Interesting ideas! You've got my vote.

I like the idea, but it'd need some fairly decent-to-heavy proj mgmt tools in it in order to support a variety of projects. Otherwise you're forcing people to divide the project up amongst various applications and communications channels.

yes good idea

KPeff- I see you're pretty savvy when it comes to proj. management and business documentation. Oddly enough, I've had the pleasure of working for a company that's been attempting to manage a merger (including development and management teams).

We've found that the documentation types aren't the most important aspect because they are all fundamentally pretty similar. What's really important is a high-level web-based documentation and team management center that can chunk projects into tasks and releases.

That said, I agree it's not an easy project to do right and will require a fair amount of sophistication... but the upside is huge and there are plenty of existing and low-cost systems to leverage (especially if worked out on a bulk contract deal... after all, the marginal cost on software is zero).

Definately, I think it's smarter not to reinvent the wheel with the management tools. Some features will absolutely have to be custom, but leveraging an existing flexible system seems like the most cost effective and viable route.

Use a job board and a project management tool. My favorites:

Ruby programmer job board (free) ~ http://jobs.rubynow.org/
Graphic designer job board ~ http://authenticjobs.com/
Project management software ~ http://basecamphq.com/

It needs to be more than a job board- it's needs to be a way to turn larger jobs into manageable tasks by having the specialists estimate and bid out on large job components. Even a simple website requires graphic design, coding, copywriting, and etc., but all of them are interelated and share the same goal. Unfortunately, when someone is looking to build, they don't think in terms of the components, they think of the overall job.

That's why there needs to be a web 2.0 resume style profiles, basic project management tools, and a way for potential team members to self-identity/ estimate job components and bid on them.

I think it's a great idea. You did a good job of explaining it, and it seems doable.

A lot of people here are idea people and there are a lot technical people aswel.
I would love to use such a team. To give 80% of the shares to a team to get the job done.
20% for the original idea.
Tommy

I think we could combine our projects as they seem to be quite symbiotic and address some of the same issues.

I agree dukenstein... they seem along the same lines.

This idea lends well to the mobility aspect I am pitching. To self assemble a team and in particular execute on project management is a bit of a hurdle especially if they are regionally remote...

I remember reading someting in Business 2.0 a few months ago about a firm who had done this for creation of advertising. They provide tools for companies to manage the process of designing creatives for ads.

If you can track down that article, it might help refine this idea. I think it's a good one.

would you have the management teams broken down so they can "bid" on projest, like inthe freelance tech world?

How is this so different from now?

Hi Kevin- There's no resume type profiles for crowdsourcing teams to self-assemble on freelance projects that don't start as ideas and aren't meant to become multi-million dollar companies.

There needs to be payment facilitation, team selection, team management, and project management tools.

How could we at CH crowdsource a $50k web dev. job and make the project initiator, be it a company or otherwise, feel comfortable about the individual and team skills?

Great idea - the follow through on this is going to be key. Are you committed to the idea? What is your project plan for this business - what are the steps to implementation. Can it be done on-line?

Hi Squint,

I am committed to the idea- I believe it's a big part of the future. Here's where I see the major components:

1) User Profile Page: With Work Experience and Skills, (Client, Team Member, and Other) Recommendations, Project Abstracts/Histories, and Portfolio (especially important for creative types like Graphic Designers). Very Web 2.0 and mostly doable with off the shelf and possibly open source Social Network software.

2) Project Board: With overall goals and specs + budget/ equity compensation. Equity in Projects could be purchased for cash on any terms acceptable to the Project Initiator by Community Investors (this will allow Team Members who are risk averse to get cash compensation for projects where the Project Initiator doesn't have Cash). Each project would have a Wiki format where people who want be involved can show their interest, subscribe to project updates, and lend voluntary non-compensated expertise (into the major components/ aspects/ needs, etc.) including how realistic the budget and equity compensation are for the idea.

3) Team Management: The Project Initiator would need to assign or elect to be the Project Manager (note: the Project Manager does not have to be a Project Manager by trade... the Project Manager is the one who takes the responsibility/ risk for projects that miss deadlines or go over budget- and gets compensated accordingly. In many cases, the Project Manager will be the Project Initiator). The Project Manager would assemble/ recruit the team (hopefully, there would be a good pool to pick from in the wiki), determine the compensation for each member, and moderate the wiki.

4) Team Collaboration: The wiki, being public, would additionally have a private team collaboration set of tools. Dukenstein would probably be a great person to help fill this part in. Mostly, from my perspective, it should have task management w/ action items, hold all project documentation, automatically track iterations, and provide the Team (including Project Initiator) with regular automated reports.

The tricky aspects are resolving issues where someone isn't happy (Project Initiator, Team Member, Investor, etc.). Hopefully, open communication will go a long way into preventing discord, but I'm a realist and know that there's going to be issues. Everyone who wants to get involved will need to agree to accepting mediation, including the cost of mediation. Also, each team member will need to agree to accept whatever legal responsibility comes with their role.

That's my outline- I think it's very doable and will give Project Initiators with large and interesting projects (not just the startup type, but also ones with big corporate budgets) the ability to confidently crowdsource a great team, get honest and critical feedback/ realistic expectations for their Project. The Crowdsource Management tool will take a predefined cut of all Project compensation (if it's all equity, then equity- all cash, then cash- hybrid, then hybrid)- I'd recommend about 5%.

dew2105 - I like where you are going but I am having trouble understanding whether you are proposing a product or a skill set or something else.

I am not negative about your idea, but just to be clear, I "think" you are proposing to assemble a suite of products, possibly things that already exist, and set up a few rules about how these products will be used together.

What I see you proposing is like a protocol for conducting projects. So, if a bunch of people wanted to get involved in a project, and they knew it was going to be run according to the "dew2105" protocol, they would know what to expect in terms of methodology and what software tools were going to be used by the team.

It would set up the mechanics and resolve some of the things you might typically expect in a project charter.

There is lots of literature on project management and there are organizations like the Project Management Institute which propound their own ways of doing things. I think your protocol can exist alongside of and draw on the expertise of the pre-existing bodies.

Seems like a good idea but I am not clear about what "new" you would need to create, beyond a written list of the rules.

Example of a rule: "The project will use Microsoft Project version x.x to track the content, status, responsible persons, and other information of the project". This rule just identifies what s/w the project group will standardize on for certain functions.

Would be interested in your comments if you have time, dew2105. Thanks.

I dont wnat to be redundant...but i posted the same quesiton in the GAme Devlt Reosurce:
How do you guarantee the collaboration will have a fair share on the income and credits? And loyalty? what if someone run a project in the nearest Copyright office as hiw own?

Hi Jill,

No, it's not mostly protocol.

We need to create a marketplace centered around pooling individual skills. Even a relatively simple website requires multiple skills these days.

eBay didn't reinvent the auction house, they just brought it to the rest of us over the internet. We will reinvent the freelance market.

For example, lets say you are a Not For Profit that wants to build a potentially award-winning website- and you have a $50k budget for approximately 50 pages of content. Without a marketplace utilizing Crowdsource Management protocol and tools, they would only consider agencies that bill at $150+ per hour. I'm using an example from personal experience.

Now, what if we had a pool of people who have impressive resumes and work histories, who recommend each other (similar to LinkedIn in that sense), and whose work samples you could see? What if people who want to participate can show interest and the Not For Profit could manage the team themselves, or hire someone from the pool of talent to do it for them? Also, what if they recieved automated updates as to the progress of their website, creative, etc.? I think the Not For Profit would give it a shot and people like us can have our pick of jobs and compensation.

It's not about creating protocol. It's about creating a marketplace that will give quality jobs to groups of people with important, but not all-encompassing skill (like who has that?) skill sets.

I hope that helped.

Daniel

Hi White Tulip,

Each project will have an overall budget and/or equity compensation (which can be sold to investors if desired). The Project Manager is responsible for putting together a team. Members of the team will estimate the work needed and negotiate directly with the Project Manager as to their compensation (cash and/or equity).

As to the loyalty aspects, just like CH requires that each idea we post is our own, members working on a project will sell all their rights to whatever component they work on (unless otherwise agreed to by the Project Initiator). I'm more worried about disputes- which are covered in a prior post.

Thanks,

Daniel

Obviously, better individual talent will be able to negotiate a better cut.

Hi Dew,

I think what Jill is getting at is: most of these tools exist and a protocol or set of standards, which could come in the form of "a web marketplace," would define how projects were ministered, managed and as you mentioned: adjudicated.

Perhaps rather than a judging (adjudicated), a process of conflict resolution. Using the forms software/website I mentioned, build a button to click if anyone has an issue, a red flag. It stimulates a discussion amongs the team which each member must see, comment and vote with their position. Once all members have weighed in, a snapshot of where the team stands is evident. A split vote will basically lock them out of any other functionality until the issue is resolved to the team's satisfaction.

Should someone decide to leave the project ...

At the start of the project when putting out the call for skills on a project, keep a short list of others who are interested but didn't get chosen (this could work for investors too.) If someone decides they want out or the team wants them out, the ask the next person in line ... and the next until you find someone to fill the role.

If you don't have a short list for that role then re-put out the call.

My two bits worth.

Dukenstein