- How big is your team? 4 Dev, 2 BA/QA, 1 Product, 2 Administrators - What are the essential roles need to be in the team? Pretty much the listed above, but

- How big is your team? 4 Dev, 2 BA/QA, 1 Product, 2 Administrators - What are the essential roles need to be in the team? Pretty much the listed above, but with the added separation of build target for developer. - From feature inception to release, how long does a feature takes? What are the process needed along the way? Depends on the UI/UX due to the fact that we target so many platforms, if there is any platform specific UI/UX then that will add to the till release. However, most of the time this is not the case and we have quarterly releases. In order to go from inception to release we have to follow the normal BA -> SWAG -> Development -> QA -> Release - How does your team prevent regressions? Code review and automated testing - How does your team share knowledge effectively? Domain knowledge? Not so well, our BA/QA's are always available to help understand any domain knowledge that is needed to implement a feature or fix a bug. - What is the testing strategy? TDD with smoke tests via katalon - What are the methods and tools used to design the application architecture? iDesign methodology with Azure I recently just switched from the web world to the application world, and it has been a bit of a pain due to the necessary understanding of platform specifics, installers, apk, ect. But, I think moving forward application development will only get easier with things like .NET MAUI, Flutter, ect.