Something clever
Ummm, I dunno
It worked!
For some time now we have been unable to measure our veolcity for each sprint (every 2 weeks), as it can potentially take 2 months for a story/bugfix to make it's way from feature development to production. Our DOD is in production.
Our process is:
Feature development
Feature test
Integration test
UAT test
Release to prod
These steps don't include issues where are bug is found and it needs to be fixed in the environment that it's in. Also, the UAT test also includes regression testing (all testing is done by a person in each environment). So a simple HTML change make take 5 minutes to develop a fix, but wont make it to production for a month or two.
Considering our sprints are 2 weeks long and it takes about a week to run regression tests. How can we possibly get changes into production every 2 weeks?