Actions
Engagement
  • Author Author: tariq.ahmad
  • Date Created: Date Created
  • Last Updated Last Updated:
  • Views 1428 views
  • Likes 0 likes
  • Comments 15 comments
Related
Recommended

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

We are discussing doing something different that involves more advanced projects and engineers working collaboratively as part of a team.  If we were to do project competitions around past themes which of the following contests would you like to revisit to work on a collaboratively with other members?  You can use this as a forum to pitch your ideas to other members to help you finish a project in 4 month period of time.  Or,  you could take an existing project from a past contest and work together as a team to build that project into a finished prototype.

 

image

Parents

  • I just have seen this poll and the concept is interesting along with the discussion about it on the comments. I would like to add my two cents, though.

    - I think that 2 or 3 general topics (like wearables, robots, automation, monitoring networks, etc) should be selected at the start, instead of specific projects or technologies (solar panels, RFID)
    - One person should be in the leader/manager role and would be in charge of the architecture, system design, and tasks assignment. I think the success of the team project is 50 % dependant on this role -- modules, assignments, and tasks should be clearly defined.

    - If the tasks are split into hardware and software, members of the team should at least have the main dev board/platform for the testing to be consistent between them.

    - If the hardware tasks are split, for example, if one member is in charge of power (energy harvesting, solar) and another is in charge of communication (BLE, WiFi), those modules should be duplicated if development is in parallel. Otherwise, modules should be clearly designed from the beginning, and once one of them is ready, it could be sent to the next member if possible.

    - Version control systems should be mandatory for both hardware and software.

    - Documentation (posting, video editing, writing) could be done by everyone or could be assigned to someone.

     

    A point of start could be a project application by someone in the lead role, with a draft plan about the project indicating which profiles or tasks are needed from other members (skills, experience, location (?), etc). This will foster the communication between members and will help to align interests.

     

    After 2 or 3 weeks of team formation and discussion, a final project plan including team description, schedule, goals, and deliverables will be submitted and the project starts. At this point, each team should have defined how shipping, spending, and prizes will be handled.

     

    I hope to see this team projects working this year.

Comment

  • I just have seen this poll and the concept is interesting along with the discussion about it on the comments. I would like to add my two cents, though.

    - I think that 2 or 3 general topics (like wearables, robots, automation, monitoring networks, etc) should be selected at the start, instead of specific projects or technologies (solar panels, RFID)
    - One person should be in the leader/manager role and would be in charge of the architecture, system design, and tasks assignment. I think the success of the team project is 50 % dependant on this role -- modules, assignments, and tasks should be clearly defined.

    - If the tasks are split into hardware and software, members of the team should at least have the main dev board/platform for the testing to be consistent between them.

    - If the hardware tasks are split, for example, if one member is in charge of power (energy harvesting, solar) and another is in charge of communication (BLE, WiFi), those modules should be duplicated if development is in parallel. Otherwise, modules should be clearly designed from the beginning, and once one of them is ready, it could be sent to the next member if possible.

    - Version control systems should be mandatory for both hardware and software.

    - Documentation (posting, video editing, writing) could be done by everyone or could be assigned to someone.

     

    A point of start could be a project application by someone in the lead role, with a draft plan about the project indicating which profiles or tasks are needed from other members (skills, experience, location (?), etc). This will foster the communication between members and will help to align interests.

     

    After 2 or 3 weeks of team formation and discussion, a final project plan including team description, schedule, goals, and deliverables will be submitted and the project starts. At this point, each team should have defined how shipping, spending, and prizes will be handled.

     

    I hope to see this team projects working this year.

Children
No Data