|
TDD: Use lightweight architecture and an appropriate scope of testing to avoid architecture rot, high test maintenance cost, and usability problems.
YAGNI: Use Case Slices and lightweight architecture can help avoid being blind-sided
On-Site Customer: Add a product owner to avoid burning out both the customer and the team.
User Stories: Instead of deferring detailed scenario development to your development during TDD, use Use Cases to bring the analysis out to the person who matters: the market constituency
Domain-Specific Languages: Take the value from the analysis and run with it; sometimes, building a domain engineering environment buys you only cost and headaches These remedies work well with each other.
Required experience :
Some level of immersion in an industrial software development project.
Expected Audience and Benefits :
These simple tips will help the audience think about and avoid common pitfalls. It's not rocket science, but it's solid information that can help projects avoid getting into trouble.
|
