Artículo educativo · ejemplo ficticio
From a software backlog ticket to a release.
Este ejemplo describe una forma de estructurar una tarea de software. Es ficticio; no representa un cliente, una entrega ni un resultado de Telar.
Submit a ticket1. State the current behavior
Describe what happens today, where it happens and who or what is affected. Separate observations from assumptions.
2. Define a bounded change
Write the desired behavior, constraints and acceptance checks. A narrow boundary makes review and testing easier.
3. Check the change
Run the tests that cover the changed behavior, inspect the diff and note any dependency or data migration that needs separate review.
4. Hand off the result
A useful handoff explains what changed, what was checked and any follow-up work. A pull request or release should be reviewed through the team’s existing process.