Development Sprint Planning 10.03 - 21.03

From ZUGSEIL Wiki
Revision as of 15:59, 14 March 2025 by Davorciric (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Team availability

This map holds the ZUGSEIL product development team and its planned availability during the upcoming days. If anything changes to this availability, please notify the line and the product manager as soon as possible.

Mon Tue Wed Thu Fri Mon Tue Wed Thu Fri
Name Function 10.03 11.03 12.03 13.03 14.03 17.03 18.03 19.03 20.03 21.03
Stefan Seiler Product Owner
Rene Schneider Process Quality Manager
Christiane Hornemann UI Quality Manager
Davor Ciric Senior Delivery Manager
Tijana Bezbradica Delivery Manager
Ilija Bubanj Quality Engineer
Nikola Kerkez Backend Developer
Petar Ilic Frontend developer
Aleksandar Lazic Frontend developer
Zivko Rankovic Frontend developer
Ivan Juras Backend developer
Nebojsa Trajkovic B-Op developer

Regular vacation requests are applied to over this page, please.

TOPIC/Project

Task creation

WBS / Project FE

BE

W-xx

Sprint-12 10.03.-14.03.

W-xx

Sprint-12 17.03.-21.03.

Promises / Customer Info / Comments
FE Should be implemented

Presentation with SBB 16.09.

BE
App:Purchase order pool manager (Open Feature Requests, see versions page) FE 80%blocked 25.10.2024: Check account functionality still NOT specified
BE 80%blocked
SBB Forgotten Features

May 2024

ZS-CI-0003 New appointment Connector & Final BE with caching BE Also holds two minor tasks on the forgotten Feature list

Integration not scheduled yet

Stocktaking (AUA) - minor fixes DEV-524 FE Done Yes Done Rene confirmed
BE

Development tasks

This contains the tasks at the entire team. Each week contains these information according to the progess of the task:

  • Phase 1: RFD Ready for Development
  • Phase 2: In development --> Progress in %
  • Phase 3: DEV testing - Developers finished development but are doing QA on their code
  • Phase 4: QA testing - QA is having this on their table
  • Phase 5: Fixing - QA returned with some flaws
  • Phase 6: Code review - The code will be reviewed
  • Phase 7: Done - Ready for deployment

Planned Tasks

Related articles