Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Coe:Platfrom team roster



Core Platform/DevOps Development Team



Panel
borderColor#DEE4E4
bgColor#F7FBFB
titleContents

Page Tree Search

Table of Contents


Recent space activity

Recent updates
typespage, comment, blogpost
max5
hideHeadingtrue
themesocial




Meet the Team 


Profile Picture
User557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d

Jakub Skoczen

jakub@indexdata.comProduct Owner / Tech Lead

Profile Picture
User5f8314dfbdef80006f6f572d

Adam Dickmeiss

adam@indexdata.dkBackend

Profile Picture
User61cd0ca0bce5e00069e98be7

David Crossley

david@indexdata.comDevOpsprofile-picture
User5c38e8d616ac1e4f7cbc660a

Kurt Nordstrom

kurt@indexdata.comBackend


Ian Hardyian@indexdata.comDevops

Profile Picture
User5f9abc1eb45b2e007453f423

John Malconian

malc@indexdata.comDevOps

Profile Picture
User5c706fbb47a54a6728e59df2

Wayne Schneider

wayne@indexdata.com DevOps

Profile Picture
User5fca8bef7cc1030069d4f186

Mark Stacy

Mark.Stacy@colorado.eduDevOps

Profile Picture
User5ee89462f7aa140abd82d11d

Julian Ladisch

julian.ladisch@gbv.deBackend

Profile Picture
User557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c

Hongwei Ji

hji@ebsco.comBackend

Profile Picture
User5d8a51e1bcc5480dd6ddfec7

Eric Valuk

evaluk@ebsco.comBackend

Profile Picture
User5c10cd488ce9b546efc4d9c4

Oleksii Popov

oleksii_popov@epam.com


Scrum Master


Team Calendar


calendar
id5c9b23ff-e933-4270-bd59-7f87434b69a2,6572b2c5-14b2-422c-bebd-2b26db03fedf



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
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyMODINVSTOR-190
  2. DevOps: 2 SP - 
    Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyFOLIO-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



Spikes / Investigations

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyCQLPG-95

Spike related to foreign key handling in CQLPGJson