Core Platform/DevOpsĀ Development Team
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
|
Recent space activity
Recent updates | ||||||||
---|---|---|---|---|---|---|---|---|
|
Meet the TeamĀ
| Jakub Skoczen | jakub@indexdata.com | Product Owner / Tech Lead | ||||
| Adam Dickmeiss | adam@indexdata.dk | Backend | ||||
| David Crossley | david@indexdata.com | DevOps | ||||
| John Malconian | malc@indexdata.com | DevOps | ||||
| Nassib Nassar | nassib@indexdata.com | Backend | ||||
| Wayne Schneider | wayne@indexdata.com | DevOps | ||||
| Mark Stacy | Mark.Stacy@colorado.edu | DevOps | ||||
| Julian Ladisch | julian.ladisch@gbv.de | Backend | ||||
| Hongwei Ji | hji@ebsco.com | Backend | ||||
| Eric Valuk | evaluk@ebsco.com | Backend | ||||
| Aleksandr Arkhipov | Scrum Master |
Team Calendar
calendar | ||
---|---|---|
|
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 'core-backlog' label;
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
| Just an example - will be removed later |