Folio Development Teams
Space shortcuts
Page tree

Versions Compared

Old Version 45

changes.mady.by.user Jakub Skoczen

Saved on

compared with

New Version Current

changes.mady.by.user Julian Ladisch

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.



Core Platform/DevOps Development Team



Panel
borderColor#DEE4E4
bgColor#F7FBFB
titleContents

Page Content:

Table of Contents

Childen Pages:

Children Display


Recent space activity

Recently Updated
typespage, comment, blogpost
max5
hideHeadingtrue
themesocial

Team Calendars
id5c9b23ff-e933-4270-bd59-7f87434b69a2,3d7ab27a-d490-4895-a9d2-8f8a618b054c,cb71f108-1ff5-4486-9d47-73d9c543f009,6572b2c5-14b2-422c-bebd-2b26db03fedf,14fea151-932c-4025-b6af-58216d2be391


Meet the Team 


Profile picture
Userjakub

Jakub Skoczen

jakub@indexdata.comProduct Owner / Tech Lead

Profile picture
Useradam

Adam Dickmeiss

adam@indexdata.dkBackend

Profile picture
Userjulianladisch

Julian LadishLadisch

julian.ladisch@gbv.deBackend

Profile picture
Userstevel

Steve Ellis

steve.ellis@colorado.edu

Backend


Barbara Löhle

barbara.loehle@bsz-bw.de

Backend





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
    serverFOLIO Issue Tracker
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyMODINVSTOR-190
  2. DevOps: 2 SP - 
    Jira
    serverFOLIO Issue Tracker
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    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

Core: Platform Sync Up