Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • This also bears the risk of piecemeal work, kludge and quick and dirty solutions. Often, management is not familiar with software issues and will decide to only schedule what some customer actually asks for. Core issues will not get scheduled, but one dirty workaround after another for them. Like: "we don't have time to get the integration tests for that module running, we have a dozen bug reports in the pipe for it!" It forbids some dev best practices, like the campsite rule (leave the garbage until you can't walk over it any more). Commented Mar 25, 2016 at 14:42
  • @ErikHart That's entirely true, and that's the core philosophy of agile development which you need to grok. You're not working for your own satisfaction, you're working for the customer's satisfaction. Testing is not an optional extra though, so if the workarounds are making testing take longer then your estimates need to clearly show that. At some point the extra testing to check your workarounds all work will outweigh the effort to just fix it. Commented Mar 31, 2016 at 10:36