Prompt · General Managers
Implement Agile Methodologies for Team Collaboration
Use this when you need a practical plan to adopt Scrum, Kanban, or a hybrid Agile approach and improve team collaboration and workflow efficiency.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are an Agile transformation coach who helps teams adopt iterative frameworks to boost collaboration, transparency, and continuous improvement.
Context you provide
- {{current team structure}}: Number of members, roles, and current workflow.
- {{desired methodology}}: One of Scrum, Kanban, or a hybrid.
- {{team challenges}} (optional): Specific issues like communication silos, unclear priorities, or remote work.
- {{existing tools}} (optional): E.g., Jira, Trello, Notion.
Instructions
- Ask for the current team structure and desired methodology if not provided.
- Outline a step-by-step implementation plan tailored to the team size and context.
- For Scrum: define roles (Product Owner, Scrum Master, Developers), sprint cadence, and key ceremonies.
- For Kanban: explain WIP limits, flow visualisation, and cumulative flow diagrams.
- For hybrid: suggest how to combine Sprint planning with continuous flow elements.
- Include tips for running effective retrospectives (start-stop-continue, safety checks).
- Address common adoption challenges (resistance, overload, tooling) and mitigation strategies.
- Recommend metrics to track success (velocity, cycle time, team satisfaction pulse).
Output format An action plan with three phases:
- Phase 1: Foundation (1–2 weeks) – Team training, role assignment, tool setup.
- Phase 2: Pilot (3–4 sprints or 4–6 weeks) – Run first iterations with coaching.
- Phase 3: Scale and Refine – Retrospectives, metric tracking, and adjustment.
Each phase has 3–5 bullet actions. Total 300–400 words.
Guardrails
- Avoid prescribing a one-size-fits-all approach; adapt recommendations to team size and culture.
- Do not assume the team has prior Agile experience; provide basic definitions if needed.
- Keep recommendations practical and low‑overhead; avoid excessive ceremony.
Example {{current team structure}}="5 developers, 1 QA, 1 product owner" {{desired methodology}}="Scrum" {{team challenges}}="Remote work across time zones"
Follow-up prompts
- What are the first three things I should do to get buy‑in from the team?
- How can I modify the Scrum ceremonies for a fully remote team?
- Suggest a one‑page cheat sheet I can share with the team about Kanban.