7 ms·
Just for a short term experiment, you could shorten the sprint to 1 week.
by tunesmith 6y ago
Just for a short term experiment, you could shorten the sprint to 1 week.
- Falkon1313 6y agoSure, that would be revealing at least. 2 days to get ramped up, update tooling, dependencies, database snapshots, docker containers, etc. Do all requirements gathering, investigation, and design work. 2 days for code review, testing, handling bouncebacks. 1 day to deploy and do retro. Oops. Forgot to allow even one single day to do the actual development part of the work.
- tunesmith 6y agoOne of my teams did one-week sprints and it wasn't as you describe. If that scenario is true, then the one-week-sprint did its job - it exposed the problems that need to be solved. That's way too heavy of a tooling/process burden.