Skip to content

Team & Stakeholders

Team Members

  • Alex — Product Owner
  • Most experienced user of SyRF
  • Primary decision maker for product questions
  • Approves user-facing scope and acceptance criteria

  • Performs UAT sign-off

  • Gill — Scrum Master & Helpdesk Manager

  • Coordinates sprints and user support/triage
  • Ensures helpdesk/user feedback flows into backlog

  • Tracks approvals workflow

  • Nuri — Junior Developer

  • Very junior, full-time developer
  • Assigned simpler implementation tasks initially
  • Working on more complex tasks with detailed technical plans and senior review

  • Learning and growing under Chris's mentorship

  • Chris — Senior Full-Stack Developer

  • Part-time on this project
  • Creator of SyRF
  • Technical lead for guidance and complex tasks
  • Nuri's mentor and supervisor
  • Handles complex cross-cutting changes, API design, infrastructure-sensitive work

Delegated Roles

Note: There are no dedicated UX or methodologist roles on the team:

  • UX/Product Design (delegated to Chris and Nuri)
  • Responsibilities: wireframes, prototypes, interaction specs, accessibility reviews

  • Support: LLM provides templates, checklists, examples, and review feedback

  • Methodologist (delegated to Alex and Gill)

  • Responsibilities: methodology/open science guidance, protocol alignment
  • Areas: inclusion/exclusion rules, inter-rater plans, RoB framework selection, export/licensing
  • Support: LLM provides methodology guidance, templates, and review feedback

Resourcing & Ownership

Task Ownership Guidelines

Nuri (Junior Dev):

  • Well-scoped UI tasks
  • Smaller backend endpoints
  • Test writing
  • Pairs with senior developer as needed
  • May take on complex coding tasks (domain logic, model changes) with proper planning:
  • Must produce detailed technical plan first
  • Plan includes: scope, design, schema/model impacts, tests, risks/rollback
  • Senior review and approval required before implementation
  • Aim: accelerate learning while ensuring quality and safety

Chris (Senior Dev):

  • Complex cross-cutting changes
  • API design
  • Infrastructure-sensitive work
  • Reviews and mentors junior developer
  • UX/design work (delegated role)

Gill (Scrum Master):

  • Coordinates sprint scope
  • Ensures helpdesk/user feedback integration
  • Tracks approval workflow
  • Methodology support (delegated role)

Alex (Product Owner):

  • Approves user-facing scope and acceptance criteria
  • UAT sign-off
  • Product decisions
  • Methodology support (delegated role)

Approval Workflow

Code Review Requirements

  • Junior-authored PRs: Require at least one senior code review (Chris) before merge
  • Complex domain/model changes (junior-led):
  • Upfront plan review/approval checkpoint required
  • Post-implementation review with knowledge capture
  • Security/data-sensitive changes:
  • Additional security/privacy review required
  • Explicit PO sign-off if user-visible
  • Definition of Done: Passing tests + updated docs + required approvals

Capacity & Sprint Planning

Sprint Structure

  • Duration: One-week sprints
  • Assignments: Fit individual availability
  • WIP Limits: Limit work-in-progress to maintain flow

Working Practices (Neurodiversity-Aware)

ADHD Support:

  • Chunk work into smaller tasks
  • Provide explicit checklists and acceptance criteria
  • Minimize context switching
  • Short, regular check-ins preferred
  • Written feedback encouraged
  • Pairing/mob sessions for tricky parts
  • Feature flags to decouple delivery from release
  • Reduce pressure while enabling incremental progress

Best Practices

For Planning

  • Consider team experience and capacity
  • Clear task ownership
  • Explicit acceptance criteria
  • Regular communication

For Implementation

  • Proper technical planning for complex work
  • Code reviews as learning opportunities
  • Documentation as part of DoD
  • Feature flags for gradual rollout

For Collaboration

  • Written communication preferred
  • Regular but short check-ins
  • Pairing when beneficial
  • Knowledge sharing and capture