Podchaser Logo
Home
Should You Design Upfront When Scaling Development?

Should You Design Upfront When Scaling Development?

Released Monday, 15th February 2021
Good episode? Give it some love!
Should You Design Upfront When Scaling Development?

Should You Design Upfront When Scaling Development?

Should You Design Upfront When Scaling Development?

Should You Design Upfront When Scaling Development?

Monday, 15th February 2021
Good episode? Give it some love!
Rate Episode

#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:

  1. We can know all the requirements upfront.
  2. We can design all the components upfront.
  3. 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

Show More

Unlock more with Podchaser Pro

  • Audience Insights
  • Contact Information
  • Demographics
  • Charts
  • Sponsor History
  • and More!
Pro Features