Engineering Project Rules

Description

This project is not from the product team. It can be from the B2B marketing team, CRM, and other stakeholders.

Purposes

• Upgrade developer knowledge, soft skills, and communication.
• Increase cross-team collaboration and ownership.

Rules

• Prioritize existing critical product tasks before starting a new engineering project request.
• Define scope, owner, timeline, and success criteria before implementation starts.
• Use teamwork for implementation, while keeping clear individual ownership for deliverables.
• Submit a daily status update to the engineering lead.
• Rotate assignments across developers to distribute domain knowledge.
• Document decisions and handover notes in the task thread.

Roles

• Lead the assigned project request from planning through delivery (board requests from CRM team).
• Complete pending high-priority tasks first when required by sprint priorities.
• Collaborate with teammates during implementation and maintain accountability for assigned deliverables.
• Report daily progress updates to the engineering lead.
• Contribute learnings that improve KPI dimensions: technology skills, systems, people, process, and influence.

Example