Task Assignment & Management

3. Task Assignment and Management 3. 任务分配与管理

Fair Task Distribution Principles 公平分配任务原则

Assign Specific Roles 分配特定角色

Clarify ownership for feature delivery, code review, testing, and facilitation. 明确功能交付、代码评审、测试与主持等角色的责任归属。

Task Diversity 任务多样性

Blend technical, documentation, design, and testing work so contributions stay balanced. 综合技术、文档、设计与测试工作，保持贡献平衡。

Verbal Fair Agreements 口头公平协议

Confirm with teammates that workloads feel equitable before moving on. 在继续之前，确认队友对工作量的公平性感受。

                    
                        Post-Assignment Confirmation Questions
                        任务分配后的确认问题
                    
                    Is everyone satisfied with their tasks? Capture concerns in minutes for visibility.每个人都对自己的任务满意吗？将疑虑写入会议纪要，提升透明度。
Are workloads comfortable given other courses, jobs, and wellbeing?考虑其他课程、兼职与健康状况，这个工作量是否可承受？
Does the distribution feel fair in terms of impact, not just hours?分工是否在影响力层面而不仅仅是工时上体现公平？

Building the Assignment Matrix 构建任务分配矩阵

Adapt the lecture idea of categorising tasks beyond “write code”. Use four columns—Implementation, Quality, Communication, Operations—to ensure each sprint includes work that keeps the team healthy. 把讲座中“任务不止写代码”的思维落地。建立四列：实现、质量、沟通、运维，确保每次迭代都有维持团队健康的工作。

Implementation 实现

Feature endpoints, multi-file architecture, npm script wiring.功能端点、多文件架构、npm 脚本接入。
Pair programming for complex imports to distribute knowledge.在复杂导入场景下结对编程，分享知识。

Quality & Support 质量与支持

Jest suite authoring, reviewing design-by-contract assumptions.编写 Jest 测试，复核契约式设计假设。
Facilitating meetings, updating documentation, posting stand-up summaries.主持会议、更新文档、发布站会摘要。

Leadership Behaviours 领导行为

The lecture stresses “a team will not lead itself”. Rotating a team lead role each iteration spreads facilitation experience while preventing burnout. A lead’s job is to keep tasks moving, not to become the sole contributor. 讲座强调“团队不会自动自我管理”。每次迭代轮换负责人，可以推广主持经验并避免疲劳。负责人的使命是推进任务，而非成为唯一贡献者。

Set explicit deadlines; leverage commitment bias by asking teammates to restate their due date aloud.设定明确截止日期，并通过让成员当面复述时间来利用承诺偏差。
Avoid social diffusion—record who will act so the group does not assume “someone else” will do it.避免责任扩散——记录具体负责人，防止出现“别人会做吧”的心理。
Check-in mid-iteration; if tasks slip, facilitate scope cuts or resource swaps quickly.在迭代中途检查，若任务延期，立即协调缩减范围或调换资源。

Module Ownership & Multi-file Collaboration (Lecture 2.2) 模块归属与多文件协作（讲座 2.2）

Nominate owners for each module and record their responsibilities in the assignment matrix. Multi-file architecture works best when someone curates exports, reviews import usage, and keeps documentation aligned with the actual code structure. 为每个模块指定负责人，并把职责写入分工矩阵。多文件架构要有专人维护导出、审核导入使用情况，并让文档与真实代码结构保持一致。

Assign reviewers to audit new imports so alias decisions follow the plan.安排评审审核新增导入，确保别名策略符合规划。
Ensure each module owner pairs with a backup to spread knowledge.每个模块负责人都要有备份搭档，分散单点风险。
Track shared utilities that multiple squads depend on for testing or data formatting.追踪多组依赖的工具函数，例如测试或数据格式化所用的工具。

Package Management & Automation Stewards (Lecture 2.3) 包管理与自动化负责人（讲座 2.3）

Treat npm work as a first-class assignment. Someone must own npm init, dependency installation, package-lock reviews, and custom scripts so every teammate works from a reproducible environment. 把 npm 工作视为一等公民的任务。必须有人负责 npm init、安装依赖、检查 package-lock 以及维护自定义脚本，确保所有成员在可复现的环境中协作。

Rotate a "package steward" who verifies npm install runs cleanly after merges.轮流设立“包管理员”，在合并后验证 npm install 是否顺利。
Assign owners to review package.json and scripts before committing changes.在提交变更前安排负责人审查 package.json 与脚本。
Capture upgrade decisions (e.g. moving to a new major version) as explicit tasks with rollback plans.把升级决定（如 major 版本更新）记录为明确任务，并附带回滚方案。

Testing & Quality Leads (Lecture 3.3) 测试与质量负责人（讲座 3.3）

Dynamic verification needs dedicated attention. Appoint quality leads who write Jest suites, enforce design-by-contract requirements, and coordinate black-box tests for major flows. 动态验证需要专人负责。设立质量负责人，负责编写 Jest 测试、落实契约式约束，并为关键流程统筹黑盒测试。

Split testing duties: one lead handles test data fixtures, another monitors CI results.划分测试职责：一人负责测试数据与假体，另一人监控 CI 结果。
Include regression suites as deliverables in the assignment matrix, not just “nice to have”.把回归测试列为分工矩阵中的交付物，而非“可选项”。
Schedule pair reviews of failing tests to keep everyone familiar with the code paths.在测试失败时安排结对排查，让所有成员熟悉相关代码路径。

Documentation & Transparency 文档与透明度

Mirror your assignments in written agreements. Store the matrix in your repo, reference it in meeting minutes, and link cards in the task board. Transparency reduces conflict when assessments ask you to reflect on contribution. 将分工体现在书面协议中。把矩阵放入仓库、在会议纪要中引用，并与任务板卡片关联。透明度越高，面对评估时谈贡献就越少冲突。

Capture capacity constraints (e.g. exams, work shifts) so resourcing adjusts proactively.记录考试、排班等精力限制，提前调整资源。
Add acceptance criteria to each task to avoid “done” meaning different things.为每项任务写清验收标准，避免“完成”含义不一。
Summarise reassignments in stand-up threads to maintain shared awareness.在站会线程里总结新版分工，确保团队同步。

Growing Each Contributor 培养每位贡献者

Improve collective capability by aligning tasks with stretch goals. Encourage teammates to take on new areas—maybe leading an npm setup, writing Jest tests, or drafting a dependency diagram—while pairing them with support. 通过将任务与成长目标匹配来提升整体能力。鼓励成员尝试新领域，例如主导 npm 配置、编写 Jest 测试或绘制依赖图，并安排支持。

Celebrate progress and adjust assignments at retrospectives. When load feels heavy, swap tasks rather than letting burnout accumulate. A healthy distribution is dynamic, not set-and-forget. 在回顾会议中庆祝进步并调整分工。当有人感到负担过重时，及时交换任务，避免倦怠。良好的分工是动态的，而非一成不变。