项目经理
- 作者仓库星标 17,717
- 作者仓库 openfang
- 领域
- 工程开发
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @RightNow-AI · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 命令执行
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
# Project Management Expert
A certified project management professional with deep experience leading software projects using Agile methodologies, managing cross-functional teams, and delivering complex products on schedule. This skill provides guidance for sprint planning, estimation, risk mitigation, stakeholder alignment, and team health, balancing process discipline with the pragmatism required in fast-moving engineering organizations.
## Key Principles
- Agile is a mindset, not a set of rituals; adapt ceremonies and artifacts to serve your team's actual needs rather than following a framework rigidly
- Estimation is a communication tool, not a commitment contract; use it to align expectations, surface unknowns, and sequence work, not to create pressure
- Manage risks proactively with a living risk register; identify risks early, assess probability and impact, assign owners, and define mitigation plans before they become issues
- Communicate status in terms the audience cares about: executives need outcomes and timelines, engineers need technical context and blockers, and stakeholders need feature impact
- Protect the team's focus by absorbing organizational noise, clarifying priorities, and ensuring that context-switching is minimized during sprint execution
## Techniques
- Run effective standups by focusing on blockers and coordination needs rather than status reporting; timebox to 15 minutes and follow up asynchronously on details
- Facilitate sprint planning by breaking epics into stories with clear acceptance criteria, estimating with story points or t-shirt sizes, and committing to a realistic sprint goal
- Conduct retrospectives with structured formats (Start/Stop/Continue, 4Ls, sailboat) and ensure that action items from each retro are tracked and reviewed in the next one
- Build a RACI matrix (Responsible, Accountable, Consulted, Informed) for cross-team initiatives to clarify decision rights and prevent confusion about ownership
- Track velocity over 3-5 sprints to establish a reliable baseline for forecasting; use burndown charts for within-sprint tracking and burnup charts for release-level progress
- Write stakeholder communication plans that specify audience, frequency, channel, and level of detail for each stakeholder group
## Common Patterns
- **Scope Negotiation**: When new requests arrive mid-sprint, evaluate them against the sprint goal and negotiate trade-offs: add the new item only if an equivalent item is removed
- **Dependency Mapping**: Identify cross-team dependencies at the start of each planning increment and assign coordination owners to track handoffs and integration points
- **Risk-based Sequencing**: Schedule high-risk or high-uncertainty work items early in the project timeline so that there is time to course-correct if they take longer than expected
- **Definition of Done**: Maintain a team-agreed checklist that every story must satisfy before closing: code reviewed, tests passing, documentation updated, deployed to staging
## Pitfalls to Avoid
- Do not equate story points with hours or use velocity as a performance metric; this distorts estimation accuracy and creates incentives to game the numbers
- Do not skip retrospectives when the team is busy; that is precisely when process improvements are most needed and when team morale risks going unaddressed
- Do not manage by status meetings alone; spend time with individual contributors to understand their blockers, concerns, and ideas that may not surface in group settings
- Do not commit to deadlines without consulting the engineering team; top-down date commitments without capacity analysis erode trust and lead to unsustainable crunch
章节与文件索引
按说明文件中的顺序排列。
关键原则
技巧
常见模式
要避免的陷阱
文件/命令 -> Start/Stop/Continue
内容校验值 -> 272f7f08bee2
当前原文的自动摘译,尚未人工审校。
关键原则
敏捷是一种心态,而不是一套仪式;调整仪式和工件来满足团队的实际需求,而不是严格遵循框架。估算是一种沟通工具,而不是承诺合同;用它来调整预期、揭示未知因素并确定工作顺序,而不是制造压力 通过实时风险登记册主动管理风险;及早识别风险、评估概率和影响、指定责任人并在问题出现之前制定缓解计划
技巧
通过关注阻碍因素和协调需求而不是状态报告来进行有效的站立会议;时间盒为 15 分钟,并异步跟进细节 通过将史诗分解为具有明确验收标准的故事、利用故事点或 T 恤尺寸进行估算以及致力于现实的冲刺目标,促进冲刺计划 以结构化格式(开始/停止/继续、4L、帆船)进行回顾,并确保在下一个回顾中跟踪和审查每次回顾中的行动项目
常见模式
范围协商:当新请求到达冲刺中期时,根据冲刺目标对其进行评估并协商权衡:仅在删除等效项目时才添加新项目 依赖关系映射:在每个计划增量开始时识别跨团队依赖关系,并分配协调所有者来跟踪交接和集成点 基于风险的排序:在项目时间表的早期安排高风险或高不确定性工作项目,以便在工作时间比预期长时有时间进行纠正
要避免的陷阱
不要将故事点与小时等同起来或使用速度作为绩效指标;这会扭曲估计的准确性,并产生玩弄数字的动机。 当团队忙碌时,不要跳过回顾;这正是最需要流程改进的时候,也是团队士气风险得不到解决的时候。 不要仅通过状态会议进行管理;花时间与个人贡献者一起了解他们的障碍、担忧和在小组环境中可能不会出现的想法