- Make the Entire Team Understand the Software Lifecycle: Teams must understand the overall lifecycle of the application, so that they what they are required to do right now and in the future.
- Reduce Cycle Time: Aim to minimize the time it takes to move from ideas to usable software.
- Develop a Learning Mindset: Failures are inevitable, but it's important to learn from failures to avoid repeating them.
- Spend Time on Building New Skills: Before moving on to new projects, allow enough time to gather the important lessons, and make sure those lessons are absorbed by your team.
- Document Operations: Document all tools, processes, automated tasks and more with the same level of quality as your product code. Moreover, regularly review and update the documentation.
- Automate Testing: Automate common testing tasks and integrate the tests into your build processes to ensure consistent test coverage.
- Measure Performance: An application might work fine under test conditions, and then have problems in production due to scale or resource limitations. So make sure to always define the maximum expected capacity and usage limits.
- Automate Deployments: Automate application deployment to test, staging, and production environments to the process faster and more reliable, as well as to remove the risk of human error.
- Use Continuous Integration: Cl allows the entire team to work on a codebase, at the same time, without having conflicts.
- Use Continuous Delivery: It will help you detect code defects sooner, and ensure that properly tested updates can be released in a very short time.
- Use Continuous Deployment: It is an additional process that automatically takes any updates that have passed through the CI/CD pipeline and deploys them into production
Last active
February 11, 2022 08:00
-
-
Save paulfermoreyes/ebc211a6f3f82f70667aee016330e9bf to your computer and use it in GitHub Desktop.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment