Ga naar hoofdinhoud

Issue Flow and Sprint Planning Process

Scrum Ceremonies​

We follow Scrum with two-week sprints. Here's the recurring rhythm:

CeremonyWhenWhat
Retrospective & Sprint PlanningMonday 09:00Review last sprint on Miro (what went well / could be better), then plan the next sprint
StandupDaily 10:00 (except Monday)Quick round: what are you working on, any blockers?
Report-outDaily 16:30 (except Friday)Written in Slack #general — what you did, any impediments
Sprint Review & PresentationsFriday (every 2 weeks)Demo your work to the team
BorrelFriday (every 2 weeks), after the sprint reviewDrinks with the team to close the sprint

Office attendance: at least one day per week in the office. If you're scheduled for the office and can't make it, notify before the workday starts.

Rescheduling meetings: whoever cancels is responsible for rescheduling immediately.

Story Points​

We estimate complexity, not time. Story points measure how hard something is — a senior may finish faster than a junior, but the complexity is the same.

SizeStory PointsRoughly
Small5Half a day
Medium10A day
Large20Half a week
XL40A week
XXL80Two weeks
XXXL160A month

Rules:

  • A single story should not exceed 10 story points — break it down
  • Anything above 10 points is an epic
  • Use timeboxing: if you've spent a full day on a 10-point story, escalate at the standup
  • Average burn rate: 10 story points per developer per day

Epic Creation and Sizing​

  1. Create Epics in Jira, linked to specific goals
    • Epics should represent complete functional features
    • Each epic should deliver independent business value
    • Epics should be linked to specific goals
  2. Product Owner performs:
    • T-shirt sizing of epics
    • Priority setting
    • Deadline alignment with related goals

T-shirt Sizing Reference Table​

SizeHours RangeComplexity
XS1-4Very small, simple task
S4-8Small task, straightforward
M8-16Medium complexity
L16-32Large, complex task
XL32-80Very large, highly complex
XXL80+Major undertaking, needs breakdown

Roadmap Planning​

  1. Scrum Master creates initial roadmap based on:
    • Epic T-shirt sizes
    • Deadlines
    • Team capacity
    • Epic priorities
  2. Product Owner reviews and approves roadmap

User Story Development​

  1. Developers create user stories for planned epics with Scrum Master guidance
  2. Issue Flow:
    • Scrum Master reviews stories against issue criteria
    • If approved, status changes to "Ready for Development" (assigned to Product Owner)
    • Product Owner reviews for alignment with intended functionality
    • Product Owner either:
      • Returns with feedback
      • Sets to "Selected for Development" and unassigns himself

Code Development​

  1. Developers can pick up unassigned issues in "Selected for Development"
  2. After completion and code merge to main:
    • Status changes to "Review"
    • Tester can test the prerelease that the merge produces
  3. After successful testing, completed issues are:
    • Presented to Product Owner during sprint review (Friday)
    • Released from the app's stableX.Y branch, following Nextcloud's branch model

Apps move to this model one at a time. On an app that still uses development, step 2 merges to development, testers use the beta channel, and the release goes to main on the Monday after the review.

Versioning​

On the Nextcloud model, the version is the one committed in appinfo/info.xml on the release branch. On apps that still use development, label every pull request major, minor or patch to control the version bump; without a label it defaults to patch. See the Release process for full details on branching, versioning, and deployment.

Sprint Closure​

  1. Scrum Master prepares sprint review proposal including:
    • List of completed issues for review
    • Overview of unfinished issues
    • Recommendation per unfinished issue (keep or return to backlog)
  2. During sprint review (Friday):
    • Team reviews unfinished issues
    • Decision made per issue to either:
      • Keep in sprint (if aligned with roadmap and capacity)
      • Return to backlog
    • Decisions are made in accordance with roadmap priorities