Iteration 1

Due: Oct 6, 2026

Planned scope: Research and scope definition

Item	Description
Research (#23)	Explore the problem space, the Omerlo platform and candidate data sources to ground the scope.
Ticket creation (#37)	Create the epics, features and user stories on the GitHub Projects board using the issue templates.
High-level interactions	Describe how the main actors and components interact at a high level.
Study of the market	Review competitors and comparable products, and position Pulse against them.
README	Project overview, team and how to get started.
User manual	First outline of how a user will use Pulse.
Discord bot (#44)	Team Discord bot for work logging, deadline and meeting reminders, and GitHub notifications. Done.
Tech stack (#15)	Select the tech stack and justify the frameworks and libraries.
Repository setup (#16)	Repository structure and contribution conventions.
Personas (#31)	Personas that the user story backlog is written for.
Problem statement and risks (#32)	Problem statement and the risk register. See Risks.

Tickets

Ticket	Title	Type	Status
#15	Select tech stack and justify frameworks and libraries	Spike	Open
#16	Set up repository structure and contribution conventions	Task	Open
#23	Identify and validate 2 to 3 real data sources with the sponsor	Spike	Open
#31	Write personas and the full user story backlog	Documentation	Open
#32	Write the problem statement and risk register	Documentation	Open
#37	Plan Iterations 1 to 4 on a GitHub Project board	Project management	Open
#44	Build a team Discord bot for work logging, reminders and GitHub notifications	Task	Done

Overall summary

Velocity and contractor estimate

• Planned vs. done:
• What slipped:
• Done early:
• Contractor estimate for this iteration:

Retrospective

• What went well:
• What went wrong:
• Improvements:

Breakdown by individual

Member	Contributions (issues / PRs / commits)