Should You Design Upfront When Scaling Development?
Amazing Apps - learn how to build agile Dynamics 365 and Power Platform business apps using Scrum · Neil Benson
Audio is streamed directly from the publisher (podcasts.captivate.fm) as published in their RSS feed. Play Podcasts does not host this file. Rights-holders can request removal through the copyright & takedown page.
Show Notes
#72. Michael Nunes asks, "When multiple systems are being delivered by different parties, I find that we have to design the details upfront, then use agile for the delivery of the Dynamics 365 systems. Is this your experience too?"
Michael's question has two layers that we address in this episode: upfront design and team composition.
Upfront design is based on three assumptions:
- We can know all the requirements upfront.
- We can design all the components upfront.
- There won't be any changes.
We challenge those assumptions and investigate the drawbacks. Then describe an alternative approach: emergent design.
Nexus is a scaled Scrum framework used when there are multiple Scrum teams working on a single application. We discover how to reconsider the composition of developers in our scrum teams when scaling beyond one team.
Resources
- Michael Nunes on LinkedIn
- The Nexus Framework for Scaling Scrum (affiliate link)
- 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