The problem with doing things in a quick and dirty way is that the dirty remains long after the quick is gone. Today's software developers are constantly making tradeoffs of time and quality in order to deliver working software on time. As we code, we suspect there is a better, cleaner way to solve the problem at hand. Since we have forecasts, goals and commitments to achieve we can't invest an inordinate amount of time locating the optimal answer. Solutions that are "fit for purpose" are good enough. In this session, you'll learn where waste and technical debt come from and, more importantly, some techniques for reducing and possibly removing them all together.
You will learn:
- How to create and use a definition of done
- How Agile software requirements reduce waste and focus the team on developing fit for purpose solutions
- How pairing, code reviews, and other practices can reduce debt and increase code quality