'scrum' 검색 결과

Your team has high autonomy — and standups are vague, weekly meetings drift into status reports, and 1:1s produce nothing but "I'm fine." This playbook fixes all three layers at once. What's inside: • Daily Standup system — 3-field format, good sample, 4 COO principles to keep it honest • Weekly Meeting — strict 25-min agenda, Scrum Master rotation, 0–10 pulse check • 1:1 Framework — 9-dimension quantified pulse, 5-group deep question bank, bilateral feedback structure • Diagnostic layer — "stuck-at" detection: info / authority / collaboration / capability / direction • FAQ for 4 common failure modes (dead standups, status-report meetings, "I'm fine" 1:1s, scaling beyond 10 people) 🇨🇳 你的团队自由度很高——但 standup 越来越糊，例会变成汇报，1:1 问不出真话。这套三层 Motivation 操作手册解决的正是这件事：standup 是信息层，例会是对齐层，1:1 是个人层。三件事做好了，motivation 不是管出来的，是长出来的。 🇯🇵 チームの自律性は高いのに、スタンドアップは曖昧で、週次ミーティングは進捗報告になり、1on1では「大丈夫です」しか返ってこない——このプレイブックは、その3層すべてを同時に解決します。 🇰🇷 팀의 자율성은 높은데 스탠드업은 두루뭉술하고, 주간 회의는 진척 보고가 되어버리고, 1:1에서는 진심을 들을 수 없다면 — 이 플레이북이 세 레이어 모두를 동시에 해결합니다. Triggers: "团队 motivation" | "standup 没人写" | "例会变成汇报" | "1:1 问不出真话" | "高自由度团队管理" | "COO 如何管人" | "team motivation" | "standup best practices" | "1on1 framework" | "weekly meeting template" | "チームモチベーション" | "팀 동기부여" | "AI startup team ops" | "remote team alignment" | "engagement下降"

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Stand up or reset project governance for new, complex, or troubled initiatives using PMBOK 8 value delivery, OKR alignment, and Scrum or SAFe cadence choices where relevant. Use when a project needs a charter, decision rights, stakeholder map, RAID logic, escalation path, or reporting rhythm. Do not use for simple task lists, isolated sprint notes, or code implementation planning.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze Kanban flow metrics to identify bottlenecks and improve team throughput. Covers Cycle Time, Throughput, WIP, and Flow Efficiency using Little's Law and Theory of Constraints. Use when a team wants to optimize delivery flow or improve predictability. Do not use for sprint-based Scrum planning — use sprint-planning-assistant instead.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

四路交叉验证工具 - 检查 Design Spec ↔ Scrum ↔ Code ↔ Tests 对齐一致性。当用户需要验证代码实现是否符合设计文档、Story AC 是否完整、测试覆盖率是否达标、Story 开发完成检查、MR 前验证、代码审查一致性验证时，必须使用此技能。适用于开发阶段的质量保证，防止设计文档与实现不一致的事故。⚠️ 实验性质技能，建议结合人工审查使用。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

PM (Project Manager / Scrum Master) agent. Reads BA and TechLead artifacts and produces sprint plan, task breakdown, and story point estimates. Creates one tracked todo/checklist item per sprint task for live pipeline tracking (FR-42). Part of the Virtual Team Skill pipeline.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

PM (Project Manager / Scrum Master) agent. Reads BA and TechLead artifacts and produces sprint plan, task breakdown, and story point estimates. Creates one TodoWrite entry per sprint task for live pipeline tracking (FR-42). Part of the Virtual Team Skill pipeline.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

AI Agile/Scrum Coach — sprint ceremony, velocity tracking, retrospective, team coaching รองรับทีม dev + non-dev

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Interactive daily standup/meeting update generator. Use when user says 'daily', 'standup', 'scrum update', 'status update', 'what did I do yesterday', 'prepare for meeting', 'morning update', or 'team sync'. Pulls activity from GitHub, Jira, and Claude Code session history. Conducts 4-question interview (yesterday, today, blockers, discussion topics) and generates formatted Markdown update.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use after intent is known to route build, fix, review, debug, docs, or Scrum requests into ordered workflow steps with exit criteria.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Knowledge base from the GAO Agile Assessment Guide (GAO-24-105506, 2023). Use for assessing and managing Agile software development in federal programs: the Agile Manifesto and framework family (Scrum, Kanban, XP, SAFe, DA, DSDM, Lean, DevOps); the three adoption perspectives (team dynamics, program operations, organization environment); requirements decomposition (epics, features, user stories, INVEST, MoSCoW, definition of done); Agile-aware federal contracting (FAR, modular contracting, SOO/PWS/SOW, product owner vs. COR); program monitoring and control (WBS, cost, schedule, EVM at the feature level); Agile metrics (velocity, lead/cycle time, CFD, burn charts); and the auditor's key-question bank. Oversight- and acquisition-oriented: it tells you how to *assess and govern* Agile programs, not how to code. Thin on hands-on engineering practice, deep cost/schedule checklists (see gao-cost, gao-schedule), and any non-US-federal context.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use quando o usuário quiser criar um GitHub Project — 'criar um project no github', 'novo board', 'project a partir de template', 'copiar project modelo' — a partir de um preset (roadmap-produto, kanban, scrum) apresentado e personalizável antes de criar, ou copiando um Project-modelo. Não use para publicar um roadmap (github-publish) nem para mexer em issues (github-issues).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.