Project14 | Which Past Themes Would You Like to Work On as a Team?

I am interested in this type of project, but there are significant issues to address such as:

How to form  a team.

• How big should the team be?
• How to find synergy.

How does a team decide what project to do?

• One way to handle this is for individual members to publish proposals and see who else is interested in contributing and then form a team.
• Another way is for a pre-formed team to brainstorm a bunch of ideas then vote on which is preferred.

How to decide who does what.

• Tasks need to be defined and assigned.
• Interfaces between each contribution need to be defined.

How to ensure the project gets done.

• weekly meetings with action items and deliverables
• a schedule with milestone dates

How to transfer hardware between team members

• Does each member duplicate the build?
• Does it all get put together in one place?
• Does it get shipped from member to member?

How to deal with expenses

• How to decide on a budget? Everyone has a different tolerance.
• Who pays?

I'll give my opinion on how I think some of your questions could be solved:

How to form  a team.

• How big should the team be?

     I suppose that all teams should have the same amount of members, and 2 is probably the best size number unless we later find there are too many E14 members interested in the team contest.

• How to find synergy.

     We could use the forum to publish what we are good at and what kind of other members we would like to work with, or maybe just message directly other members. Many members are quite active in the community and its easy to check from past projects what their strenghts and weakenesses are

How does a team decide what project to do?

• One way to handle this is for individual members to publish proposals and see who else is interested in contributing and then form a team.

     Yeah that's one solution, a different one could be to communicate directly with prospective team members and see if there is any project both members (assuming the teams are of 2)  would be intersted in working on.

• Another way is for a pre-formed team to brainstorm a bunch of ideas then vote on which is preferred.

   Thats another alternative but I it would require teams bigger than 2, and I think it could make many things more complex, I think that for a attempt of this kind of competition teams should be of 2, as it would make the team more agile and flexible.

How to decide who does what.

• Tasks need to be defined and assigned.

     I would leave that to the team itself, members should discuss how they will contribute to the project development.

• Interfaces between each contribution need to be defined.

     I don't understand what you mean with interfaces here

How to ensure the project gets done.

• weekly meetings with action items and deliverables
• a schedule with milestone dates

    Each team could decide this...

How to transfer hardware between team members

• Does each member duplicate the build? 

• Does it all get put together in one place?
• Does it get shipped from member to member?

     As you have suggested there are many alternatives, I would leave this up to each team too.

How to deal with expenses

• How to decide on a budget? Everyone has a different tolerance.
• Who pays?

     Each member would pay just like each member pays on the development of a project14. This point and many others should be discussed with the prospective team member so that things go smooth...

I'll give my opinion on how I think some of your questions could be solved:

How to form  a team.

• How big should the team be?

     I suppose that all teams should have the same amount of members, and 2 is probably the best size number unless we later find there are too many E14 members interested in the team contest.

• How to find synergy.

     We could use the forum to publish what we are good at and what kind of other members we would like to work with, or maybe just message directly other members. Many members are quite active in the community and its easy to check from past projects what their strenghts and weakenesses are

How does a team decide what project to do?

• One way to handle this is for individual members to publish proposals and see who else is interested in contributing and then form a team.

     Yeah that's one solution, a different one could be to communicate directly with prospective team members and see if there is any project both members (assuming the teams are of 2)  would be intersted in working on.

• Another way is for a pre-formed team to brainstorm a bunch of ideas then vote on which is preferred.

   Thats another alternative but I it would require teams bigger than 2, and I think it could make many things more complex, I think that for a attempt of this kind of competition teams should be of 2, as it would make the team more agile and flexible.

How to decide who does what.

• Tasks need to be defined and assigned.

     I would leave that to the team itself, members should discuss how they will contribute to the project development.

• Interfaces between each contribution need to be defined.

     I don't understand what you mean with interfaces here

How to ensure the project gets done.

• weekly meetings with action items and deliverables
• a schedule with milestone dates

    Each team could decide this...

How to transfer hardware between team members

• Does each member duplicate the build? 

• Does it all get put together in one place?
• Does it get shipped from member to member?

     As you have suggested there are many alternatives, I would leave this up to each team too.

How to deal with expenses

• How to decide on a budget? Everyone has a different tolerance.
• Who pays?

     Each member would pay just like each member pays on the development of a project14. This point and many others should be discussed with the prospective team member so that things go smooth...