Project Management - Remote!

[Ray Singh]

Thanks for reading.

I started a new role in a dash cam company and have been employed as a technical program manager. I have been given 4 dashcams to manage, inc production, firmware, apps etc. I am based in London with the rest of the team in Europe and Asia.

I have been asked to pick up where the existing PM left off but without a handover. Its tough work as the speed the business moves at is pacy!
On the side, i have been asked to create a project process lifecycle. From inception to final delivery.
I haven't really done much project management for a few years - probably 15, but remember that for each stage of the process, you need a clear RACI and who will provide what as an input to the stage and who is expecting what as an output.

Can anyone point me towards a template or something that can be used as a starting point?

Many thanks
R

[rog007]

ChatGPT is your friend!

[knk]

Managing four dash cam products across hardware, firmware, and software is a significant undertaking, especially without a formal handover. In the dash cam industry, you are balancing the physical manufacturing constraints of Asia with the software development cycles of Europe.A standard project lifecycle for consumer electronics generally follows five stages. Each stage requires a clear definition of "What goes in" and "What comes out."Project Lifecycle Framework1. Inception and ConceptAt this stage, the business defines why the product should exist.Inputs: Market research, competitor analysis, and hardware capability constraints.Outputs: Product Requirements Document (PRD) and a high-level feasibility study.RACI: Product Management Accountable, Engineering Consulted.2. Design and PlanningThis phase bridges the gap between a concept and a buildable plan.Inputs: PRD, budget limits, and regional compliance requirements (e.g., UK CA or CE marking).Outputs: Technical specifications, Bill of Materials (BOM), and a Project Schedule.RACI: Engineering Responsible, TPM (You) Accountable, Finance Consulted.3. Development and Firmware IntegrationThis is often the most complex stage for dash cams, as the app must communicate seamlessly with the hardware via Wi-Fi or Bluetooth.Inputs: Prototype hardware, UI/UX wireframes, and API documentation.Outputs: Golden Master firmware, beta app builds, and functional test reports.RACI: Software/Firmware Teams Responsible, QA Informed.4. Verification and Testing (DVT/PVT)You must ensure the camera survives heat, vibration, and power cycles in a vehicle.Inputs: Production-representative units and test scripts.Outputs: Validation report, compliance certifications, and manufacturing sign-off.RACI: QA/Validation Responsible, Operations Informed.5. Launch and DeploymentFinal delivery includes the physical shipping of units and the release of apps to the stores.Inputs: Final software builds and retail packaging.Outputs: Public app release, customer support documentation, and project post-mortem.RACI: Marketing/Operations Responsible, TPM Accountable.Template Structure for Your ProcessYou can organise your lifecycle document using a table to ensure clarity. This format helps stakeholders across different time zones understand their obligations quickly.PhaseEntry Criteria (Inputs)Primary ActivitiesExit Criteria (Outputs)RACI (A/R)InceptionMarket DataScope definitionApproved PRDProduct / TPMPlanningPRDResource allocationDetailed TimelineTPM / Lead EngBuildSpecsCoding & ToolingRelease CandidateEngineeringValidateRC BuildsStress testingTest Pass ReportQA / TPMCloseTest Sign-offApp Store UploadDelivery ReportOperationsStrategic Advice for Your RoleStandardise the "Handshake": Since your teams are remote, the handoff between Firmware (Asia/Europe) and Apps (Europe) is the most likely point of failure. Explicitly define the API documentation as a mandatory output before app development starts.Visualise the Workflow: Use a high-level diagram to show how these stages overlap. In modern hardware development, firmware often starts long before the final hardware is ready.