Task Board Management - COMP1531 Week 2

4. Task Board Management 4. 任务板（Task Board）

Progress Visualisation 可视化进度

See iteration status at a glance and communicate with mentors transparently. 一眼掌握迭代状态，与导师保持透明沟通。

Clear Responsibility 责任明确

Assign every card to owners to avoid diffusion and uncover capacity issues. 给每张卡片指定负责人，避免责任扩散并识别产能问题。

Priority Management 优先级管理

Highlight urgent work, upcoming demos, and test coverage gaps. 突出紧急工作、临近演示与测试覆盖缺口。

Time Management 时间管理

Visualise deadlines and ensure hand-offs happen before stand-ups. 可视化截止日期，确保交接在站会前完成。

                    
                        Course Expectations for Task Boards
                        课程期望
                    
                    Designated assignee: every task card names one or two owners.明确负责人：每张卡片都应标明 1–2 位负责人。
Concise title: describe work such as “Iter2 – authRegister endpoint”.简洁标题：例如 “迭代2 – authRegister 端点”。
Detailed description: include sub-tasks, acceptance criteria, and links to specs.详细描述：列出子任务、验收标准及规格链接。
Clear iteration: label the card with iteration tags or prefixes.明确迭代：使用标签或前缀标识所属迭代。
At least three stages: To Do → In Progress → Review → Done.至少三个阶段：待办 → 进行中 → 评审 → 完成。

                

Designing Your Board Layout 设计任务板布局

Start simple with To Do, Doing, Done, then evolve to match your workflow. Align columns with milestones highlighted in your GANTT chart so visual cues reinforce the plan. 先从“待办-执行-完成”这类简单泳道开始，再根据流程逐步演进。让列与甘特图的里程碑一致，使视觉线索强化计划。

Add quality gates such as “In Review” or “Awaiting Testing” before Done.在“完成”前添加“评审中”或“等待测试”等质量门。
Create swimlanes for front-end, back-end, infra/testing to expose bottlenecks.为前端、后端、基础设施/测试设置泳道，暴露瓶颈。
Use labels to indicate npm/package work, meeting follow-ups, or risk spikes.使用标签标注 npm/依赖工作、会议行动项或风险高点。

Link cards to Git commits, merge requests, or meeting minutes. When tutors evaluate teamwork evidence, a board with traceable artefacts speaks louder than verbal updates. 将卡片与 Git 提交、合并请求或会议纪要相连。导师评估团队协作时，有可追踪产物的任务板比口头汇报更有说服力。

Updating the Board Daily 每日更新任务板

Lecture guidance emphasises “check in regularly and send reminders”. Use the board during stand-ups: move cards live while answering the three stand-up questions to reinforce accountability. 讲座提醒“定期签到并发送提醒”。在站会期间使用任务板：边回答三问边实时移动卡片，强化责任感。

Spot stalled work: if a card sits in progress for more than two stand-ups, escalate or reassign.发现停滞：卡片在“进行中”超过两次站会，就要升级或重新分配。
Record blockers directly on the card, linking to npm errors, failing Jest tests, or review feedback.在卡片上记录阻碍，并链接 npm 报错、Jest 失败或评审意见。
Close the loop by posting completion summaries and attaching demo screenshots or logs.在卡片上写完成总结，并附上演示截图或日志，形成闭环。

NPM Workflow Lanes (Lecture 2.3) NPM 工作流泳道（讲座 2.3）

Create dedicated cards for package management so the board shows whether npm init, dependency installs, and script updates are complete. This keeps reproducible environments visible instead of hidden in terminals. 为包管理创建专门卡片，让任务板清晰反映 npm init、依赖安装与脚本更新是否完成，把可复现环境从终端搬到看板上。

Add checklist items for verifying package-lock.json and document the npm command that should run at review.在清单中加入检查 package-lock.json 的步骤，并记录评审时要执行的 npm 命令。
Tag cards that touch external libraries so tutors can confirm licensing and version choices.给涉及外部库的卡片打标签，方便导师确认授权与版本选择。
Capture automation ideas (e.g. npm run lint, npm run test) as separate tasks to reduce future manual effort.把自动化想法（如 npm run lint、npm run test）作为独立任务记录，减少后续人工操作。

Test Suite Tracking (Lecture 3.3) 测试套件追踪（讲座 3.3）

Add columns or labels that mirror dynamic verification stages: unit tests, integration tests, regression suites. When a card moves to Review, it must link to the Jest results or screenshots proving the behaviour. 为动态验证阶段建立列或标签：单元测试、集成测试、回归套件。卡片进入评审时必须附上 Jest 结果或截图，证明行为正确。

Track flaky tests as their own cards so the team allocates time to stabilise them.将不稳定测试单独建卡，确保团队安排时间进行修复。
Log design-by-contract assumptions in card comments to clarify what inputs were validated.在卡片评论中记录契约式假设，说明已验证的输入。
Sync CI status badges with the board to show “tests pending”, “tests running”, or “tests passed”.同步 CI 状态徽章，直观看到“测试排队”“测试运行”或“测试通过”。

Connecting with Planning & Testing 与规划和测试的联动

Tie your board to the dependency graph and test strategy. Cards should reference the module they touch (from Lecture 2.2), the npm scripts required (Lecture 2.3), and the Jest suites verifying completion (Lecture 3.3). 让任务板与依赖图与测试策略联动。卡片应注明涉及的模块（源自讲座 2.2）、所需 npm 脚本（讲座 2.3）以及验证完成的 Jest 测试（讲座 3.3）。

Create template checklists with sub-items: design review, implementation, unit tests, integration tests, documentation.制作模板清单，涵盖设计评审、实现、单测、集成测、文档等子项。
Use automation (e.g. GitHub Actions or webhook integrations) to update card status when CI passes.利用自动化（如 GitHub Actions 或 Webhook）在 CI 通过时自动更新状态。
Sync retrospective insights back into card templates to drive continuous improvement.将回顾会议的洞察同步到卡片模板中，推动持续改进。

Showcasing Progress to Stakeholders 向干系人展示进度

Before labs or demos, filter the board to highlight newly completed cards and upcoming deadlines. Screenshots or exports can be embedded in meeting minutes so stakeholders see objective proof of momentum. 在实验课或演示前，筛选任务板以突出新增完成的卡片和临近的截止项。将截图或导出文件嵌入会议纪要，让干系人看到客观的推进证据。

A disciplined board turns anecdotal updates into verifiable data, keeps team morale high, and demonstrates professional engineering practice from Week 2 onwards. 严谨的任务板能将口头更新转化为可验证的数据，维持团队士气，并从第二周起就展现专业工程实践。