Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Project Manager:
    • Tracking status
    • "The accountability piece": main artifact is the Burn-down chart
    • Red flags (ie: people are going beyond what they estimated, totals add up to more time than is allotted, etc) should be raised to Janet
    • Coordinate Biz issues
    • Include PM tasks in the chart, with estimates and dates
    • Collect information off-line, not in meetings
  • Product Owner - responsible for vision/priorities:
    • Roadmap: higher level timeframe
    • Themes for each sprint: put this out to group before sprint planning
    • Takes first pass through feature/bug queue before sprint planning to organize/prioritize in light of larger roadmap (business value)
    • Primary artifact is the product backlog, prioritizing
  • Team Manager:
    • Resource management
    • Performance
  • Release Engineer:
    • Releases to QA
    • produce QA release notes
    • branches and tags code
    • Coordinate with isda-ops for release date (open RT ticket)
    • prepare the final release candidate for isda-ops
  • Developers:
    • Estimates of tasks
    • Reporting exceptions in the scrum: task is taking longer than is expected, etc
    • Manage own bug queue
    • Do feature work, then bugs - we need to assign these in appropriate size chunks, so this is possible within a given sprint
  • QA:
    • Owns JIRA
    • First pass at new bugs, assign:
      • Component and developer
      • Severity
      • Priority
      • Does this needed to be added to this round of changes? If so, raise it with team, in triage. If it seems really urgent, and a potentially large issue, might raise it in scrum as a red flag.
    • Developers can pushback as needed, disagree with priority, severity, assignment
    • Triage: mainly during QA phase, not during feature work; responsible for raising red flags, if there are issues that need to be addressed immediately/with greater urgency
    • QA decides when final release is ok to go to prod
  • Customer Support:
    • First response
    • Customer messaging
    • Customer Advocate
    • In communication with "Product Owner" about customer needs, priorities as they come up

Useful links:
svn guide
jira guide
thalia release process
thalia release communication