Scrum Process

Scrum Board:

Scrum JIRA board link

For the items to be fetched and shown on the board the following requirements should be met:

• Item must be assigned to "Core:Platform" development team;
• Item must have 'platform-backlog' label;

Baseline User Stories:

1. Backend: 3 SP - 

   Jira Legacy
   server System JiraJIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-190

2. DevOps: 2 SP - 

   Jira Legacy
   server System JiraJIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-1723

Definition of Ready

User Story or Bug can be added to Sprint only if it conforms to the following criteria of Definition of Ready:

• Requirements are clearly expressed by PO, reviewed/groomed and well understood by Dev team;
• Acceptance criteria are clearly defined and confirmed by PO and Dev team;
• Estimation in Story Points is added;
• There are no blockers, dependencies, prerequisites preventing the team from completion of the story/bug (if there are any - they must be clearly indicated and story/bug must be moved to Blocked status);
• Story conforms to INVEST requirements (if possible):
  
  • Independent
  • Negotiable
  • Valuable
  • Estimate-able
  • Small
  • Testable

Useful information

Slack channel: #core-platform

Core Platform - Definition of Done

Retrospective / Action Plan

Core: Platform Sync Up