Comprehensive Programming Team Structure Prompt

```markdown # Comprehensive Programming Team Structure > **Mission:** To establish a well-rounded, highly effective development process through clear role definitions, robust communication, and a culture of continuous innovation. As your Team Builder, I have structured this development squad to maximize efficiency, innovation, and collaboration. Below is the comprehensive guide to the five key roles (including the necessary Quality Assurance role to round out the team), the tools we will use, and the operational rules we will follow. --- ## The Core Team: Roles, Responsibilities, and KPIs To ensure clarity of goals and avoid task overlap, each role has been strictly defined with specific objectives, responsibilities, and Key Performance Indicators (KPIs). ### 1. Team Brain (Lead Architect / Strategist) * **Objective:** Drive strategic thinking, technical innovation, and high-level system design. * **Responsibilities:** * Architect the software foundation and make core technology choices. * Solve complex technical bottlenecks and foresee scalability issues. * Mentor the team on best practices and new technologies. * **KPIs:** System uptime, technical debt ratio, and successful implementation of innovative features. ### 2. Task Distributor (Scrum Master / Agile Coach) * **Objective:** Manage workflow, facilitate agile processes, and ensure an equitable workload. * **Responsibilities:** * Break down project milestones into actionable tickets. * Allocate tasks among team members efficiently to prevent burnout. * Clear blockers that hinder the development process. * **KPIs:** Sprint completion rate, cycle time, and team velocity. ### 3. Programmer (Software Engineer) * **Objective:** Execute coding tasks, build features, and maintain software quality. * **Responsibilities:** * Write clean, maintainable, and efficient code based on assigned tasks. * Participate in code reviews and collaborate closely with the Team Brain. * Debug and resolve software defects. * **KPIs:** Lines of code/Pull Requests merged, bug rate per feature, and code review turnaround time. ### 4. Manager (Project / Product Manager) * **Objective:** Oversee project timelines, stakeholder communication, and overall team collaboration. * **Responsibilities:** * Define the product roadmap and prioritize the backlog. * Ensure effective leadership to guide the team toward common business goals. * Maintain team motivation and secure necessary resources. * **KPIs:** On-time milestone delivery, stakeholder satisfaction score, and budget variance. ### 5. Quality Assurance Specialist (QA / Tester) * **Objective:** Ensure all deliverables meet the highest quality standards before deployment. * **Responsibilities:** * Design and implement automated and manual testing protocols. * Identify, document, and track bugs to resolution. * Validate that specialized technical skills translate into a flawless user experience. * **KPIs:** Defect escape rate, test coverage percentage, and time-to-resolve bugs. --- ## Team Needs & Ecosystem To facilitate a balanced workload and ensure seamless execution, the team will rely on a strictly defined operational ecosystem. | Category | Solution / Strategy | Purpose | | :--- | :--- | :--- | | **Project Management** | Jira, Trello | Tracking progress, managing backlogs, and assigning daily tasks. | | **Shared Workspace** | Slack, Microsoft Teams | Facilitating asynchronous collaboration and daily updates. | | **Technical Stack** | Git, CI/CD Pipelines | Version control and seamless integration of programming and QA efforts. | --- ## Operational Rules & Workflows ### 1. Synchronization & Meetings * **Daily Stand-ups:** A strict 15-minute meeting managed by the Task Distributor to discuss *what was done yesterday, what is planned for today, and any current blockers*. * **Sprint Planning & Retrospectives:** Bi-weekly meetings led by the Manager to align on goals, review KPIs, and adjust processes for continuous improvement. ### 2. Communication & Collaboration * **Radical Candor:** Fostering an environment of strong communication skills where feedback is given clearly and constructively. * **Documentation:** All architectural decisions (Team Brain) and process definitions (Manager) must be documented in a central wiki (e.g., Confluence or Notion). ### 3. Continuous Learning & Motivation * **Skill Development Time:** 10% of the workweek is dedicated to researching new technologies, attending webinars, or upskilling. * **Knowledge Sharing Sessions:** Monthly "Lunch & Learns" where team members present on new tools, design patterns, or testing methodologies. * **Workload Monitoring:** The Task Distributor and Manager will actively monitor Jira/Trello boards to ensure no single Programmer or QA specialist is overwhelmed, actively shifting resources to maintain high morale and motivation. ```

Comprehensive Programming Team Structure Prompt

プロンプト内容保存

使い方

参考資料

ノート