3 User Story Traps to Avoid with Power Platform and Dynamics 365
No se pudo agregar al carrito
Solo puedes tener X títulos en el carrito para realizar el pago.
Add to Cart failed.
Por favor prueba de nuevo más tarde
Error al Agregar a Lista de Deseos.
Por favor prueba de nuevo más tarde
Error al eliminar de la lista de deseos.
Por favor prueba de nuevo más tarde
Error al añadir a tu biblioteca
Por favor intenta de nuevo
Error al seguir el podcast
Intenta nuevamente
Error al dejar de seguir el podcast
Intenta nuevamente
-
Narrado por:
-
De:
#80. Richard asks about working with user stories in a Dynamics 365 or Power Platform agile project.
I'll spend this episode talking about user stories on Dynamics 365 and Power Platform projects and I’ll share three traps to avoid when working with user stories when building Power Platform and Dynamics 365 apps using Scrum.
- The first trap is the level of detail.
- The second trap is splitting and combining stories.
- The third trap is managing changes to the backlog of users stories.
Resources
- User Stories Applied: For Agile Software Development
- User Story Mapping: Discover the Whole Story, Build the Right Product
- Amazing Applications podcast page on LinkedIn
- Amazing Applications podcast page on Podchaser
- Scrum for Microsoft Business Apps online course at Customery Academy
- Agile Foundations for Microsoft Business Apps free online mini-course at Customery Academy
Support the show
CONNECT
🌏 Amazing Apps website
🟦 Customery on LinkedIn
🟦 Neil Benson on LinkedIn
MY ONLINE COURSES
🚀 Agile Foundations for Microsoft Business Apps
🏉 Scrum for Microsoft Business Apps
📐 Estimating Business Apps
Keep experimenting 🧪
-Neil
Todavía no hay opiniones