Quantcast
Viewing all articles
Browse latest Browse all 5700

Long running un-releasable work and sprints that always map to release

We are moving to scrum. Before this, we had a two-week release cycle (a new version is deployed that customers can actually use). We are now moving to two-week sprints. Sprints give certain flexibility to not release, but we are not buying that idea. After all, what is the purpose of calling something complete, and yet not release it. We had certain process efficiency built into that and we want to continue with this. This is not my question though. This is just the context.


Viewing all articles
Browse latest Browse all 5700

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>