Project Progress Tracking in Electronic Device Development

The development of electronic devices is a complex and dynamic process that demands detailed planning, precise execution, and effective project management.

Keeping track of project progress is crucial to ensure that the project stays on schedule and within budget while not diminishing the fact the final product meets its objectives.

Because of this, every project should have some kind of project management planning and progress tracking tool.

One invaluable tool in this regard is the Gantt chart. In this blog, we'll explore how Gantt charts can significantly enhance project progress tracking in electronic device development.

What is a Gantt chart?

A Gantt chart is a horizontal bar chart that visually represents a project’s schedule, milestones, and their interdependencies over time – they show which tasks should be done and the time needed to complete them. Gantt chart is helpful for project management for the following reasons:

• Progress monitoring – project managers can see if tasks are going according to the plan and depending on that adjust the project schedule. This also helps managers to see which goals were met on the schedule – which can help them to improve project plans in the future.
• Project planning – project managers can see the deadlines, milestones, and schedules for various project components.
• Resource management – The Gantt chart can help with resource allocations.
• Bottlenecks detection – Helps to detect which tasks can cause problems and delays.

Gantt chart can be used both in the Waterfall and Agile methodology approach.

In Waterfall methodology, a Gantt chart is commonly used as a linear, sequential project planning tool that provides a clear timeline for each phase of the project. Waterfall Gantt charts typically are inflexible and do not easily accommodate changes or newer requirements.

On the other hand, in Agile methodology, Gantt charts are more flexible. They are often used as high-level roadmaps – they help to provide an overview of milestones and iterations, focusing on delivering value incrementally.

How to use the Gantt chart?

Gantt charts are essentially task-scheduling tools. Key components of a Gantt chart are:

• Tasks/Activities - individual work items or activities needed to be completed to accomplish the project. Tasks are typically listed on the vertical axis of a chart
• Timeline – The horizontal axis represents time, usually divided into days, weeks, or months – depending on the project scale.
• Dependencies – arrows or lines connecting tasks indicate their sequence or relationship – some tasks must be completed before others can begin.
• Milestones – significant points in the projects, such as project kick-off, major deliverables, and project completion.
• Critical Path – This is a sequence of tasks that determines the project’s overall duration. They can be highlighted to draw special attention to critical tasks that, if delayed, would impact on the project’s completion date.

Step-by-step guide on how to build a Gantt chart

1. Identify tasks – start by listing all the tasks required for the project: research, design, prototyping, testing, and manufacturing. Considering that electronic device development includes the development of firmware (software), hardware, and production, the tasks should be classified according to the department to which the task belongs:

· Software division for firmware development tasks: software architecture, features, documentation, test plan, firmware for testing purposes in production, etc.

· Hardware division for hardware development tasks: hardware architecture, schematic design, component selection, documentation, s, test plan, design of housing, print technology research, etc.

· Production division: ordering components, housings, packaging, test plan, assembling devices, production testing, etc.

When creating tasks, you should divide one big task into as many smaller tasks as possible – this will help estimate duration and check progress later.

2. Sequence tasks – determine the order in which tasks should be completed and identify all task dependencies – what task cannot be done until the other task is finished. Consider that some tasks from one division need to be done e before other tasks from another division can be started, for example - components cannot be ordered until the design of hardware is finished and BOM is confirmed, etc. Also, some tasks need support from more than one division – e.g. test plan task – all, software, hardware, and production divisions should work together to put on the test plan document.

3.  Estimate durations – Estimate the duration, start, and finish date of each task.

4.  Allocate resources – decide who will be responsible for each task.

5. Draw/Fill your chart – you can create your own Gantt chart using Microsoft Excel, or you can use some of the available project management software tools like Microsoft Project, Zoho Projects, Trello, Asana, or similar.

6.  Include Milestones – identify key milestones in your project. These are significant points that mark the completion of major phases or tasks.

7.  Share the Gantt chart – share it with your team members and stakeholders so they are aware of the current situation at every moment.

Once you have taken these steps, as the project progresses, you should regularly update your chart to reflect actual progress.

To use the Gantt chart more effectively you should keep it simple, update it regularly, include buffer time for unexpected delays or challenges, and ensure that all resources are allocated effectively.

Figure 1. presents a Gantt chart of a fictitious electronic device development that includes firmware development, hardware design and development, development of test JIG for production, design of housing, and at the end, production.

As you can see, the development of the firmware can go in parallel with hardware design and prototyping, but some tasks depend on the other ones – for example, PCB design cannot be done until Schematic design is done.

Also, manufacturing cannot start until procurement is done, etc.

In software development, you can see that after the implementation of the features is completed, maintenance starts – that means resolving bugs that are found in the meantime, etc.

Pros of using the Gantt chart

• Clear visual representation of a project’s timeline and tasks.
• Clear dependency view.
• Gantt charts help in planning and sequencing tasks.
• Gantt charts facilitate communication among team members, stakeholders, etc.

Cons of using the Gantt chart

• Creating and maintaining Gantt charts can be time-consuming (although some PM tools do it automatically).
• For large projects with numerous tasks and dependencies, Gantt charts can become overwhelming.
• Lack of flexibility.