Moustachir
IT ProtocolsTeam Protocols

Internal IT Protocol

Specialized operational guide for Internal Product Teams at Moustachir Com

1. INTRODUCTION

This document is the specialized operational guide for Internal Product Teams. It builds upon the General IT Protocol to define the specific workflows, governance structures, and technical leadership responsibilities required for our internal staff.

2. ORGANIZATIONAL MODEL & TEAMS

2.1 Dynamic Team Structure

To support our growing portfolio, we operate with a flexible and scalable organizational model based on Squads and Domains.

  • Project-Based Squads: Teams are formed dynamically around specific projects or product features.
    • Composition: Cross-functional (Product, Design, Engineering).
    • Lifecycle: Squads may be long-lived (for core product maintenance) or short-lived (for specific client projects).
  • Resource Pooling:
    • Team members are not rigidly locked into a single unit forever.
    • Allocation: Assignments are based on skill requirements, availability, and professional growth goals.
    • Multi-Tenancy: A senior member might lead one squad while contributing as a specialist in another.

2.2 Accommodation Modes

We support flexible work arrangements to attract the best talent:

  • On-site: Working from the HQ.
  • Online: Fully remote collaboration.
  • Hybrid: A balanced mix of office and remote work.

Note: While flexible, the specific mode for each member must be agreed upon and validated by the Team Lead, IT Director, and Operations Director.

3. ROLES & RESPONSIBILITIES (DETAILED)

3.1 IT Projects Manager (PM)

  • Strategic Ownership: Defines the "What" and "Why" of every project.
  • Commercial Interface: Acts as the sole bridge between the Technical Team and the Commercial Team. All client requirements, feedback, and scope changes must flow through the PM.
  • Backlog Guardian: Holds the ultimate authority on task prioritization.
  • Resource Allocation: Decides which internal members or freelancers are assigned to a project.

3.2 IT Director

  • Technical Vision: Defines the "How" at a high level.
  • Validation: Approves architectural decisions, technology stacks, and security protocols.
  • Protocol Enforcer: Ensures that this protocol is being followed.

3.3 Operations Director

  • Business Alignment: Ensures IT output aligns with company operational goals.
  • Resource Management: Validates budget and resource availability.

3.4 Engineering Lead / Team Lead

  • Codebase Stewardship:
    • Maintains the GitHub Organization.
    • Manages Submodules to ensure code reuse.
    • Updates Project Templates to reflect best practices.
  • Quality Control:
    • Performs mandatory code reviews for critical features.
    • Enforces coding standards defined in the Engineering Protocol.

3.5 UI/UX Lead

  • Design System Stewardship:
    • Maintains the Figma Design System.
    • Updates UI Kits and templates.
  • Visual Quality: Validates that implemented UIs match the design specifications defined in the UI/UX Protocol.

4. GOVERNANCE & MEETINGS

4.1 Periodic Squad Sync

  • Schedule: Weekly (Day/Time defined by each Squad, e.g., Tuesday 10 AM).
  • Agenda:
    1. Review: What was shipped last week?
    2. Blockers: What is stopping progress?
    3. Plan: What are the goals for this week?
  • Attendance: Mandatory for all members of the specific Squad.

4.2 Code Review Schedule (Internal Team)

To maintain code quality and knowledge sharing, internal team members follow a structured code review process:

  • Daily Quick Check-Up: At the end of each workday, the Team Lead performs a quick review of the day's commits and Pull Requests.
    • Purpose: Catch obvious issues early, provide quick feedback.
    • Duration: 15-30 minutes.
  • Monday Full Review: Every Monday, the Team Lead conducts a comprehensive code review of the previous week's work.
    • Purpose: Deep dive into architecture decisions, code quality, and technical debt.
    • Preparation: For the Tuesday squad sync meeting.
    • Duration: 1-2 hours.

4.3 Backlog Management

  • Location: Notion.
  • Authority: Only the PM and IT Director can add or re-prioritize high-level items in the backlog.
  • Process:
    1. Inbox: New ideas/requests go to the Inbox.
    2. Refinement: PM details the requirements.
    3. Scheduling: Items are moved to "Next Up" or assigned to a Sprint.

5. TECHNICAL WORKFLOWS

For specific "How-To" guides on Development and Design, please refer to the specialized protocols.

5.1 Project Creation Process

  1. Initiation: PM defines the project in Notion.
  2. Repo Setup: Team Lead creates a new repo from the Standard Template.
  3. Design Setup: UI/UX Lead creates a new Figma file from the Master Template.

5.2 Onboarding New Internal Members

  1. System Access: IT Director provisions accounts (Google Workspace, Notion, GitHub, Discord).
  2. Protocol Deep Dive: New hire reads General, Internal, and their Role-Specific protocols.
  3. Environment Setup: Team Lead assists in setting up the local dev environment.
  4. First Commit: New hire is assigned a minor bug fix or task to practice the Git workflow on Day 1 or 2.

General IT Protocol

Foundational guide for all Engineering, Design, and Product operations at Moustachir Com

External IT Protocol

Operational guide for Freelancers and External Partners at Moustachir Com

Table of contents

1. INTRODUCTION2. ORGANIZATIONAL MODEL & TEAMS2.1 Dynamic Team Structure2.2 Accommodation Modes3. ROLES & RESPONSIBILITIES (DETAILED)3.1 IT Projects Manager (PM)3.2 IT Director3.3 Operations Director3.4 Engineering Lead / Team Lead3.5 UI/UX Lead4. GOVERNANCE & MEETINGS4.1 Periodic Squad Sync4.2 Code Review Schedule (Internal Team)4.3 Backlog Management5. TECHNICAL WORKFLOWS5.1 Project Creation Process5.2 Onboarding New Internal Members