Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I don't know why you would want to "agile-proof" your methodology when agile methods seem to be the exact solution you are looking for. Agile methods anticipate (embrace, I think, is the word Kent Beck uses) change and look for ways to minimize risk in the face of inevitable change. It sounds like your project is the poster child for why we need agile methods.</p> <p>I'd suggest reading one of many books on agile methods and learning about techniques such as TDD, frequent delivery, story-based development, etc. that could really help you to manage the unavoidable change that all projects experience. Jim Highsmith has a good book, <a href="http://rads.stackoverflow.com/amzn/click/0201760436" rel="nofollow noreferrer">Agile Software Development Ecosystems</a>, that provides an overview of several different agile methodologies and how they address particular problems in development.</p> <p><strong>EDIT</strong>: It occurs to me that perhaps what you mean is "change-proof" your development. I sorry to say that I don't think that this is really possible. There are techniques to minimize change, but you can't eliminate it. I've found that it's better to recognize that it will happen and use a methodology that expects it and can manage it better than to try and minimize it. Processes that try to minimize change are very front-loaded with planning activity and take much longer than I am willing to spend for the types of projects that I typically work on. I find that with agile methods I'm able to complete my projects in about the amount of time that I would otherwise have spent planning for a different methodology.</p> <p>As an aside I recently had a project that, because of political reasons, we had to spend a lot of time gathering requirements and doing product evaluations. It took us about a year to eventually decide what product to get. I had the installation and integration (which used my agile methods) done in about 2 months.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload