Technical debt
Technical debt
Technical debt is not an XP practice.
Technical debt is total sum of less than perfect design and implementation decisions in the product.
Technical debt needs to be monitored and controlled.
Sit together-XP advocates an open space big enough for the whole team
Slack- XP recommends that in any plan it is better to include some minor tasks that can be dropped if you get behind.
You can always add more stories later and deliver more than you promised.
Energized- Work only as many hours as you can be productive and only as many hours as you can sustain.
Team should strive to have minimum technical debts, and team should reduce technical debt by adapting refactoring practice of XP.
Leave a Reply
You must be logged in to post a comment.