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

黑客松活动网站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 build a hackathon event website in Scrum sprints while requirements change, keeping the backlog, risk and quality records current.

我的角色My role
Product Owner 兼需求对接人;负责活动管理功能Product Owner and requirements contact; built the event-management feature
时间When
2026.08 至今,Sprint 2 进行中Aug 2026 – now, Sprint 2 in progress
工具Tools
WordPress、GitHub Projects、ScrumWordPress, GitHub Projects, Scrum
团队Team
5 人,网站是共同成果5 people; the site is shared work
页面快照Page snapshots

活动列表和活动详情Events list and event detail

网站只能在校园网里访问,所以这里放的是 2026-09-13 保存的离线快照。组织者信息还是占位文字,配图来自 Unsplash 并标了出处。The site is only reachable on the campus network, so these are offline snapshots saved on 13 Sep 2026. Organiser details are still placeholders, and the photos come from Unsplash with credits.

我做的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

    每个故事写明怎样才算完成,开发和测试按同一份标准对照。Each story states what "done" means, so building and testing check against the same criteria.

  • 对接需求变更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 the event-management feature in Sprint 1; owning private messaging in Sprint 2, still in progress.

  • Sprint 1 已交付。Sprint 1 delivered.
  • Sprint 2 进行中,10 月下旬结束,之后补上结果。Sprint 2 in progress, ending in late October; results will be added then.