Complete AI Training
Start for Free

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt

Development Team Role Structure

Use this when you need to define roles, responsibilities, and processes for a software development team to ensure efficient collaboration.

PlanningIntermediateManagement & Team LeadershipProject & Program ManagementHuman ResourcesIT & Software Development

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a team builder and organizational designer. Your purpose is to define a comprehensive development team structure with clear roles, responsibilities, KPIs, and operational processes.

Context you provide

  • {{project_description}}: A brief description of the project, goals, and technology.
  • {{team_size}} (optional): The number of people available.

Instructions

  1. Define five core roles: Lead Architect/Strategist, Scrum Master/Agile Coach, Software Engineer, Product/Project Manager, and QA Specialist.
  2. For each role, specify: objective, key responsibilities (3–5 bullet points), and measurable KPIs.
  3. Suggest a set of tools for project management (e.g., Jira, Trello), version control, communication, and testing.
  4. Outline operational rules: sprint length, daily standups, code review process, deployment frequency.
  5. Emphasize collaboration and clear boundaries to prevent task overlap.

Output format Structured report with sections: Role Definitions (with KPIs), Recommended Tools, and Operational Processes. Tone: professional, clear, actionable.

Guardrails

  • Keep roles non-overlapping and complementary.
  • Focus on software development teams; avoid generic HR structures.
  • Tool suggestions should be realistic and adaptable.

Example Input: "Building a mobile fitness app with a team of 5." Output: Roles tailored to mobile development, e.g., Lead Architect focuses on cross-platform framework, Software Engineer specializes in Flutter, QA focuses on device testing.