Documenting Your Agile Applications – YouTube

#124. When you’re using an agile approach, like Scrum, how and when should you document your Dynamics 365 or Power Platform applications? After all, the Agile Manifesto says, “We value working software over comprehensive documentation”, right?

Before projects start, my teams document requirements in a product backlog, visualise the backlog in a user story map, and discuss the project during a solution blueprint review workshop.

During sprints, we’re writing unit tests, functional test cases, describing our features in wiki pages and tracking our decisions in a decision register.

Towards the end of the project or before a production release, we’ll export the wiki as an as-as-built solution design document  and hand it over the axe-wielding psychopaths who will be supporting and maintaining our applications.

And, of course, we’ll produce all the other documentation our product owner asks us to if she create documentation-related items and prioritises them in the product backlog.

Customery Academy student celebrations
Congratulations to Olha Kucheriava ( for completing my Scrum for Microsoft Business Apps, to Adeel Arshad ( and Simon Williams ( for achieving their Professional Scrum Master certification, and to the teams from ITK Consulting ( , SynSci and AppRising ( for completing my Winning Agile Projects masterclass.

Visit Customery Academy ( to find out more about our programs to help customers and partners build amazing, agile Dynamics 365 and Power Platform applications.


• Microsoft Learn: Create a solution blueprint for Dynamics 365 solutions (
• FastTrack Solution Blueprint presentation template (
• Write unit tests with FakeXrmEasy ( Support the show (

🌏 Amazing Apps ( website
🟦 Customery on LinkedIn (
🟦 Neil Benson on LinkedIn (

🚀 Agile Foundations for Microsoft Business Apps (
🏉 Scrum for Microsoft Business Apps (
📐 Estimating Business Apps (

Keep experimenting 🧪


Author: Neil Benson

Share This Post On
Share via
Copy link
Powered by Social Snap