If it works its obsolete

It depends on the nature of the evolution. If it is constantly trying to implement new stuff then this suggests that you are not able to implement proper change control/testing procedures.

It also suggests that you are dependent on individuals with key knowledge of the system.

I say this because if you work in teams then you simply can't do without good documentation. The team cannot function without knowledge share. Knowledge share includes documentation

Trying to implement good practice retrospectively is hell.

Ideally, you need to get agreement to slow down the evolution and have set release timetables, but you need management to buy into this.

Sell it as

• Long term reduced cost
• Improved quality
• Long term Increase productivity

To use a military analogy, after every advance you need to consolidate your position and make sure that the supply lines do not become over extended and therefore vulnerable.

Think of the supply lines as being the path to bring a new team member up to speed on the system