Development Sprint Planning 24.03 - 04.04

From ZUGSEIL Wiki
Revision as of 07:36, 4 April 2025 by Davorciric (talk | contribs)
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 24.03 25.03 26.03 27.03 28.03 31.03 01.04 02.04 03.04 04.04
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

Sprint-12 10.03.-14.03. Sprint-12 17.03.-21.03. Sprint-13 24.03.-28.03. Sprint-13 31.03.-04.04. Promises / Customer Info / Comments
Orders overview app (responsive) (SBB) FE 70% QA testing 90% QA testing Practically done, but there are feedbacks from client that are considered
BE 80% QA testing 90% QA testing
Staff based data (SBB) FE 50% Done
BE 50% Done
SOS to newest CoreClient BE 10% Done
Export/import products (Classifications and catalog extensions) (KOR) FE 30% Done
BE 30% Done
Pick up manager: Manipulate shipments extension (AUA) FE 90% 90% 90% 90%
BE 90% 90% 90% 90%
Abstract controller BE 30%
Appointments (responsive) FE 80%
BE
Regular shop - responsive (SBB) FE 5%
BE
Catalogs (skinny version) FE
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