课程项目 · 软件过程与管理 · 5 人团队 · 2026.08–2026.10Coursework · Software Processes and Management · team of 5 · Aug – Oct 2026

黑客松活动网站Hackathon Event Website

WordPress · 我是 Product OwnerWordPress · I'm the Product Owner

课程模拟一个真实的客户项目：教学团队扮演客户，我们按 Scrum 分两个 Sprint 开发一个黑客松活动网站。需求会中途变化，待办、风险和质量记录要一直保持更新。The course simulates a real client project: the teaching team plays the client, and we built a hackathon event website over two Scrum sprints while requirements changed, keeping the backlog, risk and quality records current.

我的角色My role
Product Owner 兼需求对接人；Sprint 1 做活动管理，Sprint 2 做站内私信Product Owner and requirements contact; built event management in Sprint 1 and private messaging in Sprint 2
时间When
2026.08–2026.10，两个 Sprint 都已交付Aug – Oct 2026; both sprints delivered
工具Tools
WordPress、GitHub Projects、ScrumWordPress, GitHub Projects, Scrum
团队Team
5 人，网站是共同成果5 people; the site is shared work
网站画面Screens

Sprint 2 交付后的网站The site after Sprint 2

网站只能在校园网里访问，这里放的是 2026-10-19 录演示视频时的画面。人物、团队和对话都是测试数据，照片头像做了模糊；配图来自 Unsplash，网站上标了出处。The site is only reachable on the campus network, so these are frames from the demo video recorded on 19 Oct 2026. People, teams and messages are test data, and photo avatars are blurred; the illustrations come from Unsplash and are credited on the site.

活动首页，菜单上的 Messages 显示 1 条未读
活动首页Events 按关键词、场地和类别找活动。有人发来私信时，菜单上的 Messages 显示未读数，右下角弹出提示。Find events by keyword, venue or category. When a private message arrives, Messages in the menu shows the unread count and a notice pops up at the bottom right.
团队目录，列出两个黑客松团队
找团队Team directory 每个团队写明在做什么、经理是谁、还剩几个名额；满员的团队标 Team full。Each team shows what it is building, who manages it and how many places are left; full teams are marked Team full.
团队页，显示项目想法、协作方式和人数
团队页Team page 项目想法、协作方式、经理和人数上限，参与者在这里加入团队。Project idea, how the team works, the manager and the member limit; participants join the team from here.
站内私信页，左边是会话列表，右边是对话
私信Messages 我负责的站内私信：会话列表、按姓名或内容搜索，时间按本地时区显示。The private messaging I owned: conversation list, search by name or message, times shown in the local time zone.
我做的What I did

当 Product Owner，也自己写功能Product Owner, and building features too

  • 排优先级Prioritise

    用 MoSCoW 给 Sprint 2 的 7 个用户故事排优先级，先保证“必须有”的能交付。Prioritised the 7 user stories of Sprint 2 with MoSCoW so the must-haves ship first.

  • 写清验收标准，按它验收Write acceptance criteria, then check against them

    每个故事写明怎样才算完成，开发和测试按同一份标准对照。Sprint 2 收尾时我逐个验收：找队友的结果卡片没显示筛选用到的技能和兴趣，退回修改后才接受。Each story states what "done" means, so building and testing check against the same criteria. At the end of Sprint 2 I checked each story: the teammate search did not show the skills and interests being filtered on, so it went back for a fix before I accepted it.

  • 对接需求变更Handle changing requirements

    跟进客户（教学团队）的需求变化，同步到待办列表。As requirements contact, I tracked changes from the client (the teaching team) and kept the backlog in step.

  • 自己也写功能Build features too

    Sprint 1 开发了活动管理功能；Sprint 2 做了站内私信，包括会话列表、搜索和未读提醒。Built event management in Sprint 1 and private messaging in Sprint 2, including the conversation list, search and unread alerts.

  • Sprint 1 已交付。Sprint 1 delivered.
  • Sprint 2 已于 10 月 18 日交付：7 个用户故事（32 个故事点）在看板上全部完成。Sprint 2 delivered on 18 Oct: all 7 user stories (32 story points) done on the board.