Wastes in Software Development

Waste is simply anything that does not add real value to the overall end goal is considered waste. Things that could be considered waste are 
- Unnecessary features or functionality 
- Over engineering 
- Unnecessary code 
- Weak requirements 
- Bureaucracy 
- Anything that slows down or delays the team 
- Weak testing, resulting in many production issues 
- Poor or unnecessary communication 
- Unnecessary documentation (note documentation may still be needed) 
- Anything that wastes time without any valuable benefit 
 "The Seven Wastes of Software Development": 
1. Partially Done Work 
2. Extra Features 
3. Relearning 
4. Handoffs 
5. Delays 
6. Task Switching 
7. Defects

Comments

Post a Comment

Popular posts from this blog

Scrum Answer to Top 10 Software Project Risks

Source: (The Standish Group, 2011) Lack of top management commitment Scrum demands commitment from the top management through the assignation of a full-time cross-functional self organized team. The team is protected and can take their own decisions about the project with the support of the top management. Failure to gain user commitment In Scrum, the team constantly show working software to the users, which increase the commitment and feedback. Misunderstanding the requirements Scrum knows that is not possible to fully understand all the user requirements. In each iteration, the team work in the more important and clear requirements. As the software is developed, the team get better insights about the project goals and have more clarity about the following requirements. Lack of adequate user involvement Constantly working software makes the users more involve in the process. Lack of required knowledge/skills in the project personnel In Scrum, the teams are cros...
Read more