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提供。所有播客内容（包括剧集、图形和播客描述）均由 Neil Benson 或其播客平台合作伙伴直接上传和提供。如果您认为有人在未经您许可的情况下使用您的受版权保护的作品，您可以按照此处概述的流程进行操作https://zh.player.fm/legal。

5y ago 12:47

MP3•单集首页

#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

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