Seven Sins of a Software Project
0 likes1,088 views
The document discusses the seven sins of software projects which can lead to project chaos and failure. These sins include untraceable changes, non-stop development without milestones, lack of documentation, no test coverage, no static analysis, ad hoc releases, and use of anti-patterns in code. Following disciplines like DevOps, writing code according to rules, and avoiding these sins can help improve software quality and project success rates.
1 of 12
Download to read offline
Seven Sins of a Software Project
- 1. /20@yegor256 1 Seven Sins of a Software Project Yegor Bugayenko www.yegor256.com
- 2. /20@yegor256 2 “Software development projects are in chaos, and we can no longer imitate the three monkeys—hear no failures, see no failures, speak no failures.” 94% —Chaos Report (2015) by Standish Group 7%
- 3. /20@yegor256 3 writing re-writing code ahead discipline DevOps management rules
- 5. /20@yegor256 5 untraceable changes tickets branches decisions 20%
- 7. /20@yegor256 7 no documentation code use cases UML updates
- 8. /20@yegor256 8 no test coverage mandatory 7%
- 9. /20@yegor256 9 no static analysis mandatory 5%
- 10. /20@yegor256 10 ad hoc releases 2%release.sh