36 lines
1.5 KiB
Markdown
36 lines
1.5 KiB
Markdown
---
|
||
tags:
|
||
- process/meeting
|
||
---
|
||
Attendees:: [[Linda Haas]], [[Oliver Schöner]], [[Norbert Pruß]], [[Norbert Franz]], [[Thomas Erschens]], [[Balazs Szeidl]], [[Sebastian Keck]], [[Mihai Gottschling]]
|
||
Related Projects:: [[Talend Pipeline]]
|
||
Topics::
|
||
Length::
|
||
purpose::
|
||
summary::
|
||
|
||
## 🗓️Agenda
|
||
1. Sprint Planning (45 min)
|
||
2. Sprint Retro (45 min)
|
||
|
||
## Requirements for sprint planning
|
||
|
||
The requirements must fulfill the following criteria to be scheduled:
|
||
|
||
1. The Jira task has the status Ready. The task has been assessed as feasible by the developers.
|
||
2. The Jira Task has been estimated in terms of effort.
|
||
3. The person responsible have to participate in the planning.
|
||
4. The requesters should have already agreed among themselves which tickets are more relevant.
|
||
|
||
Jira Backlog: [https://dev.nmm.de/ji/secure/RapidBoard.jspa?rapidView=206](https://dev.nmm.de/ji/secure/RapidBoard.jspa?rapidView=206&view=planning.nodetail)
|
||
Retrospective: [https://dev.nmm.de/co/display/TAL/Retrospective](https://dev.nmm.de/co/display/TAL/Retrospective)
|
||
|
||
## 📤 Goal
|
||
A plan for the next 3 weeks. Adapted to the sprint planning for 2024.
|
||
|
||
## 📝Note
|
||
Urgent issues should be synchronized with the other participants in advance so that the meeting can be planned properly. In the event of prioritization conflicts, the scouring of the individual projects from Portfolio Management is available as an aid.
|
||
|
||
## ✔️ Aufgaben
|
||
- [x] Übernahme Monitoring-Thema [start:: 2024-11-18] [completion:: 2024-11-20]
|