Agile, like many new ideas, has a tendency to overreach. The exasperated users are the same ones who dread system updates. They see any technological change or inconvenience as the result of a vast technocratic conspiracy. These people are the ones who want it "to just work" and have little patience for the tedious process of taking matters to that point. These complaints stem from taking this group outside its narrow comfort zone.
On the other hand, there are end users, usually termed "power users", who love their engagement with technology and its processes. It is these people who should be part of the ongoing development process. The larger mass of users should be consulted and upgraded, but infrequently. Of course, this requires you not break backward compatibility with each new release. You know who you are.
In theory, since a movie is just a series of still frames, the same techniques could be used to modify individual frames as are used to "photoshop" a still image, (albeit, tediously). You might find the tools and tutorials at this site of some help in analyzing individual frames: http://fotoforensics.com/
You might also find some of the information at the associated Hacker Factor blog of use: http://www.hackerfactor.com/blog/index.php?/categories/17-FotoForensics
"The C Programming Language -- A language which combines the flexibility of assembly language with the power of assembly language."