Navigating the role of an architect in a Dynamics 365 Scrum team with Allan de Castro – YouTube

#141. On this episode of Amazing Apps, podcast host Neil Benson is joined by Allan de Castro, a senior technical consultant for the Power Platform at Avanade France.

They discuss their experience applying Scrum to recent projects, including the role of an architect in the Scrum framework. The episode covers key challenges such as the importance of ensuring clarity in the backlog, prioritization of sprints, and addressing technical requirements while focusing on business and added value. 

[00:06:23] Allan, an architect and technical lead, discusses the challenge of finding their place in a team using the Scrum framework for the first time, and navigating discussions related to technical requirements and architecture while also focusing on business requirements and added value. 
[00:10:15] Focus on delivering continuous testing value during sprints, even if it means sacrificing some business value.
[00:11:56] Agile and Scrum framework used for new project, integrating systems and iterating for development. Customer familiarity with Agile important.
[00:13:12] Capture project requirements early to avoid issues in development.
[00:16:36] Business analyst helps product owner with basic questions on application building, including object lifecycle. Dynamics 365 provides out-of-the-box features, such as bulk edit mode, without development needed. It can be demonstrated in demo instead of user story.
[00:19:10] To successfully execute a Dynamics 365 project using Scrum framework, it is important to ensure technical requirements are included in the backlog and fully estimated. It is also important to train the customer on Dynamics 365 and focus on prioritization during sprints. Custom development must fit into the security models provided by Dynamics. Workshops may be needed to refine new business requirements.
[00:24:06] Team delivers daily or every two days into the UAT environment, with testing by a quality insurance person and a dual check by the project owner or business analyst before marking as done. UAT phases were conducted initially, but now testing is continuous without UAT phases.
[00:26:13] The architecture and requirements were complicated due to unclear data sources and ongoing system construction. Agile methodology requires clear definitions before development, and cultural differences affect analysis phases. Workshop and design are necessary for identifying potential risks and managing sales territory was a major concern.
[00:31:14] Ensure clear backlog, communicate dynamics to team and stakeholders, define sprint process, architect advisory role, avoid influencing sprints.
[00:32:34] Dev team used Azure DevOps for backlog management, linking work items to pull requests and builds for easy tracking and communication with end users. They also suggest creating automatic task generation for consistent task patterns.
Support the show (https://buymeacoffee.com/amazingapps)

CONNECT
? Amazing Apps (https://amazingapps.show) website
? Customery on LinkedIn (https://linkedin.com/company/customery)
? Neil Benson on LinkedIn (https://linkedin.com/in/neilbenson)

MY ONLINE COURSES
? Agile Foundations for Microsoft Business Apps (https://customery.com/foundations)
? Scrum for Microsoft Business Apps (https://customery.com/scrum)
? Estimating Business Apps (https://customery.com/estimating)

Keep experimenting ?
-Neil

source