Refinement & Prozess-Regeln 🚀
⚡ EXPRESS-REGEL: Items <= 3 Punkte Effort werden direkt zwischen PO & Entwickler geklärt – kein Refinement nötig!
PO (Business Need)
- Erstellt rein Business-Anforderungen.
- Verzicht auf Technik- oder Design-Vorgaben.
- Definiert Business/User Need & GIVEN/WHEN/THEN.
Team / Item-Owner
- Definiert technische Umsetzung & Mockups.
- Klärt Design-Fragen eigenständig.
- Vervollständigt das Item bis Meeting 2.
Zwei-Stufen-Modell (DI & DO)
| Meeting | Fokus | Ziel |
|---|---|---|
| 1. Pitch | PO erklärt Business Need. Keine Technik. | Verständnis "Was & Warum". Benennung Item-Owner. |
| 2. Ready-Check | Item-Owner präsentiert technische Lösung. | Finaler Check & Vergabe Status DoR. |
📌 DoR = Definition of Ready (Bereit für Umsetzung / Approved Board)
⚡ EXPRESS RULE: Items <= 3 points effort are handled directly between PO & Dev – no refinement needed!
PO (Business Need)
- Focus strictly on Business Requirements.
- No technical or design input.
- Defines Business/User Need & GIVEN/WHEN/THEN.
Team / Item-Owner
- Defines technical implementation & mockups.
- Handles design/technical questions.
- Prepares the item for Meeting 2.
Two-Step Model (TUE & THU)
| Meeting | Focus | Goal |
|---|---|---|
| 1. Pitch | PO explains Business Need. No tech talk. | Team understands "What & Why". Item-Owner assigned. |
| 2. Ready-Check | Item-Owner presents technical solution. | Final approval & Status DoR. |
📌 DoR = Definition of Ready (Ready for Implementation / Approved Board)
⚡ REGLA EXPRESS: Items <= 3 puntos se resuelven directamente entre PO y Desarrollador – ¡sin refinamiento!
PO (Necesidad de Negocio)
- Crea solo requisitos de negocio.
- Sin especificaciones técnicas o de diseño.
- Define Necesidad de Negocio/Usuario y GIVEN/WHEN/THEN.
Equipo / Item-Owner
- Define la implementación técnica y mockups.
- Resuelve dudas de diseño de forma autónoma.
- Completa técnicamente el ítem para la Reunión 2.
Modelo de dos etapas (MAR y JUE)
| Reunión | Enfoque | Objetivo |
|---|---|---|
| 1. Pitch | PO explica la necesidad de negocio. Sin técnica. | Entender el "Qué y Por qué". Nombrar Item-Owner. |
| 2. Ready-Check | Item-Owner presenta la solución técnica. | Validación final y estatus DoR. |
📌 DoR = Definition of Ready (Listo para implementación / Approved Board)
⚡ EKSPRESNO PRAVILO: Postavke <= 3 točke se rešujejo neposredno med PO in razvijalcem – brez refinementa!
PO (Poslovna potreba)
- Ustvarja izključno poslovne zahteve.
- Brez tehničnih ali oblikovnih navodil.
- Določa poslovne/uporabniške potrebe in GIVEN/WHEN/THEN.
Ekipa / Item-Owner
- Določi tehnično izvedbo in osnutke (mockups).
- Samostojno rešuje vprašanja glede dizajna.
- Tehnično dokonča postavko do 2. sestanka.
Dvostopenjski model (TOR in ČET)
| Sestanek | Fokus | Cilj |
|---|---|---|
| 1. Pitch | PO razloži poslovno potrebo. Brez tehnike. | Razumevanje "Kaj in Zakaj". Imenovanje Item-Ownerja. |
| 2. Ready-Check | Item-Owner predstavi tehnično rešitev. | Končna potrditev in status DoR. |
📌 DoR = Definition of Ready (Pripravljeno za izvedbo / Approved Board)
⚡ EKSPRESNO PRAVILO: Stavke <= 3 boda se rešavaju direktno između PO i programera – bez refinementa!
PO (Poslovna potreba)
- Kreira isključivo poslovne zahteve.
- Bez tehničkih ili dizajnerskih uputstava.
- Definiše poslovne/korisničke potrebe i GIVEN/WHEN/THEN.
Tim / Item-Owner
- Definiše tehničku implementaciju i mockups.
- Samostalno rešava pitanja dizajna.
- Tehnički kompletira stavku do 2. sastanka.
Dvostepeni model (UTO i ČET)
| Sastanak | Fokus | Cilj |
|---|---|---|
| 1. Pitch | PO objašnjava poslovnu potrebu. Bez tehnike. | Razumevanje "Šta i Zašto". Imenovanje Item-Ownera. |
| 2. Ready-Check | Item-Owner predstavlja tehničko rešenje. | Finalna provera i status DoR. |
📌 DoR = Definition of Ready (Spremno za implementaciju / Approved Board)
Item Template
TITLE: [Klarer Business Need Titel]
Business Need:
{Written by Product-Owner, clear and only without technical Input}
[PO] what is the Business need...
User Need:
{Written by Product-Owner, clear and only without technical Input}
[PO] What needs the User...
Technical Explanation:
{Written by Item-Owner, technical Input, when needed}
[DEV] If needed...
Mockups:
[PO] + [DEV] Link to Mockups...
Acceptance Criteria:
[PO] {Pure business view}
GIVEN: .. | WHEN: .. | THEN: ..
Business Need:
{Written by Product-Owner, clear and only without technical Input}
[PO] what is the Business need...
User Need:
{Written by Product-Owner, clear and only without technical Input}
[PO] What needs the User...
Technical Explanation:
{Written by Item-Owner, technical Input, when needed}
[DEV] If needed...
Mockups:
[PO] + [DEV] Link to Mockups...
Acceptance Criteria:
[PO] {Pure business view}
GIVEN: .. | WHEN: .. | THEN: ..