Hello,

One such method is using a Work Breakdown Structure (WBS). A WBS is a hierarchical list of all the tasks and sub-tasks that need to be completed for a project. The WBS breaks down the project into manageable, smaller parts, making it easier to assign tasks and track progress. To create a WBS, the project manager begins by identifying the main deliverables of the project. Deliverables are the end results that the project is intended to achieve. For example, if the project is to develop a new software product, the deliverables might be the design document, software code, testing report, and user manual. Once the deliverables are identified, the project manager breaks them down into smaller, manageable tasks. For example, for the design document, the tasks might include researching the requirements, creating a design prototype, and reviewing and finalizing the document. The project manager then breaks down each of these tasks into smaller sub-tasks, creating a detailed list of all the tasks required to complete the project. After creating the WBS, the project manager can assign tasks to team members and track progress using project management software. This allows team members to collaborate and communicate effectively, making it easier to manage the project and ensure that it stays on track.

Another way to brainstorm and assign tasks for a project would be taking the project in its entirety and separating parts from each other. For example, for my senior project we made the entire modeled figure and then separated it into the acrylic casing, the arduino/coding, the mechanics and the well plate. And once the main parts were separated we then worked on the specific details and assigned the main people in charge of their parts. Each person was also placed into their secondary roles to assist the main person in charge of specific tasks. This allowed everyone to help each other and for there to be enough ‘back up’ for each part. 

Similar to what some of my peers have mentioned, I think that the best way to break up a project and figure out what tasks will be required is to first break up the project into sections. That would be like literature research, device design (prototyping), software (if needed), electrical, ordering parts, testing components, and testing assembled product. From there, once you get a better understanding of what your device will need, you can break it down further. After the major tasks are established, a meeting should be held to assign these tasks to either individuals who have the background for it, or to teams that have that background. If teams, then the team leaders need to be chosen to assign work for each team member.