Developers and QA
Principle to follow as a scrum master
Development Guidelines
Keep API docs updated and accurate
Track daily progress from team members
Before production: check Sentry, backend logs, and fix issues
Verify resources and version updates
Reuse existing solutions instead of building from scratch
Discuss with QA before changing existing code/features
Understand functionality and impacts with QA
Always ask why the feature is needed and if the approach is best
Before coding, align with QA on test plans, key cases, and edge scenarios
Avoid adding runtime features β move them to the next sprint
Maintain a doc for assumptions and known bugs
Start only after writing pseudo code and defining the approach
Bugs found on dev and local will be managed in DBdash. Bugs found on prod by members other than QA will be managed on frill.