AZ-400: Plan work flow and feedback cycles

Choose a process flow or process template to work in Azure Boards

Waterfall Development

1. Requirements analysis
2. Design
3. Coding/Implementation
4. Testing
5. Deployment
6. Maintenance

• Slow to offer feedback, as the solution may not be developed until weeks, months, or even years after the requirements analysis

Agile Development

• Compresses the steps of waterfall development into shorter bursts (typically "sprints") with a focus on smaller changes with more rapid feedback and iteration

CI/CD

• Continuous integration/continuous deployment
• Making frequent, small, reversible changes to code
• Automating build, test, and deployment steps

Source Control

• Useful for tracking changes to code
• Also referred to as version control
• Facilitates collaboration on projects, particularly large-scale projects with many developers

General Best Practices

• Commit code changes early and often to keep them small
• Automate code checks, builds, tests, and deployments as much as possible
• Continuously monitor application health and performance through various tools and metrics
• Set up monitoring alerts and automate triage when possible