Skip to main content
Environment: local

Due to the Russian invasion of Ukraine, we have paused all purchases and training in and from Russia.  Read Statement

Something clever

Last post 02:56 pm October 28, 2022 by Eric Naiburg
2 replies
07:29 pm December 21, 2018

Ummm, I dunno


07:31 pm December 21, 2018

It worked!


02:56 pm October 28, 2022

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?

 


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. If you have left the first and last name fields blank on your member profile, your email address will be displayed instead. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.