# data[].attributes.headline
“Como padre de familia, quiero recibir alertas de temperatura para saber si mi hijo tiene fiebre en tiempo real.”

# data[].attributes.subject
“Como padre de familia, quiero recibir alertas de temperatura para saber si mi hijo tiene fiebre en tiempo real.”

# data[].attributes.body
“Como docente, quiero un panel de monitoreo para detectar emergencias de salud entre estudiantes.”

# data[].attributes.body
Sprint 1: Diseño del prototipo y selección de sensores.

Sprint 2: Desarrollo de la app móvil.

Sprint 3: Integración GPS y alertas en tiempo real.

Sprint 4: Pruebas con usuarios piloto.

# data[].attributes.body
“Seleccionar proveedor de sensores biométricos.”

“Diseñar mockups de la app móvil.”

“Definir arquitectura de conectividad (Bluetooth, WiFi o datos móviles).”

# data[].attributes.body
“Programación del módulo de alertas en tiempo real.”

“Diseño de la interfaz gráfica de usuario.”

# data[].attributes.body
“Investigación de normativas sobre dispositivos médicos no invasivos.”

“Estudio de prefactibilidad técnica y económica.”

Revisión: Demo del prototipo a padres y docentes.

Retrospectiva: Identificación de mejoras en la comunicación del equipo y tiempos de entrega.

# data[].attributes.attachment_link.readable_text
Press enter or click to view image in full size

Let me say it loud for the people in the back: just because someone asks for it, doesn't mean we do it. But also - just because it's not ready for delivery doesn't mean we ignore it either.

See, I don't treat the backlog like a Christmas wishlist. But I also don't treat it like an elite VIP club where only shiny, ready-to-ship stories get in. I treat it like what it's meant to be - the single source of truth for everything that takes effort from the team.

Why? Because if we don't track it, we fall prey to chaos.

I'm not adding stories to micromanage or to flood Jira. I'm doing it to protect the focus of the sprint. Because if it's not in the backlog, some random stakeholder will drop by, yell something urgent, and hijack the team. And someone on the team, in the name of being "agile," will jump on it.

Agile doesn't mean do everything instantly. It means do the right things at the right time. The backlog is how I manage that time.

# data[].attributes.attachment_link.title
Agile lesson #12: The product backlog is not a wish list, here's how I make it strategic

# data[].attributes.attachment_link.description
Let me say it loud for the people in the back: just because someone asks for it, doesn't mean we do it. But also - just because it's not ready for delivery doesn't mean we ignore it either. See, I...

# data[].attributes.attachment_link.description
If Your Planning Sessions Feel Like a Game of Agile Charades, You’re Not Alone

# data[].attributes.attachment_link.title
This Is How We Do: Agile For Small Distributed Teams

# data[].attributes.attachment_link.description
In some of my earlier blog posts I have already touched the topic of using Scrum as a project management framework and me becoming a…

# data[].attributes.attachment_link.title
Tracking the Untrackable: Reporting Progress in Agile and Complex Projects

# data[].attributes.attachment_link.description
Nearly every developer has experienced that moment: working under pressure on a so-called “highest priority” task — one that was supposed…

# data[].attributes.attachment_link.title
Mastering the Definition of Done in Agile for Project Success

# data[].attributes.attachment_link.description
The journey through Agile methodologies often highlights certain principles that consistently steer projects toward success. One such…