Core Platform/DevOps Development Team
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Page Content:
Childen Pages:
|
Recent space activity
| Recent updates | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| calendar | ||
|---|---|---|
|
Meet the Team
| Jakub Skoczen | jakub@indexdata.com | Product Owner / Tech Lead | ||||
| Julian Ladisch | julian.ladisch@gbv.de | Backend | ||||
| Steve Ellis | Backend | |||||
| Barbara Löhle | Backend |
Scrum Process
Scrum Board:
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:
- Backend: 3 SP -
Jira Legacy server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-190 - DevOps: 2 SP -
Jira Legacy server System JIRA 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