Core Platform/DevOps Development Team
Contents
Recent space activity
-
-
Telepresence on Rancher contributed yesterday at 4:43 PM
-
-
-
Inventory app Version history commented yesterday at 3:29 PM
-
Inventory app Version history contributed yesterday at 3:23 PM
-
-
-
Kubernetes Example Deployment contributed yesterday at 1:40 PM
-
-
-
Create Eureka environment contributed yesterday at 1:23 PM
-
Meet the Team
 | Jakub Skoczen | jakub@indexdata.com | Product Owner / Tech Lead |
| Adam Dickmeiss | adam@indexdata.dk | Backend |
| Julian Ladish | julian.ladisch@gbv.de | Backend |
| Oleksii Popov | oleksii_popov@epam.com | Devops |
| John Malconian | malc@indexdata.com | DevOps |
| Wayne Schneider | wayne@indexdata.com | DevOps |
| Mark Stacy | Mark.Stacy@colorado.edu | DevOps |
| Julian Ladisch | julian.ladisch@gbv.de | Backend |
Team Calendar
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 - MODINVSTOR-190 - Getting issue details... STATUS
- DevOps: 2 SP - FOLIO-1723 - Getting issue details... STATUS
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
Spikes / Investigations
CQLPG-95 - Getting issue details... STATUS | Spike related to foreign key handling in CQLPGJson |