Skip to end of banner
Go to start of banner

Core Platform team

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 42 Next »



Core Platform/DevOps Development Team



Contents

Page Content:

Childen Pages:

Recent space activity


This calendar is read-only. Please ask your administrator to renew your Team Calendars subscription.


Meet the Team 


Jakub Skoczen

jakub@indexdata.comProduct Owner / Tech Lead

Adam Dickmeiss

adam@indexdata.dkBackend

Julian Ladish

julian.ladisch@gbv.deBackend

Steve EllisBackend

Hongwei Jihji@ebsco.comBackend

Mikhail Fokanovmikhail_fokanov@epam.comBackend

Dilshod Khusanovdilshod_khusanov@epam.comScrum Master





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 -  MODINVSTOR-190 - Getting issue details... STATUS
  2. 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



  • No labels