3 ms·

> We have feature releases every 4 weeks. If your feature is merged before QA, it goes out in that release. That's what a sprint is.

• BrandonM 6y ago
  We make basically no attempts to estimate how long a feature is going to take and then update those estimates along the way. An individual feature could take a few days to implement or several months (years even). Periodic check-ins are completely independent of the 4-week release cycle. Every 4 weeks, we release whatever has been merged in the last 4 weeks. One dev might have 8 independent changes in a release or 0. We typically have a handful of significant changes that land each release and a bunch of minor improvements. Still, there's not much effort to estimate when any particular feature might land. When a large feature is getting close to completion, the dev might choose to push a little bit to hit a particular release. There's not really any external pressure to do that, though. That's still a sprint?
  • srtjstjsj 6y ago
    Yes. A key idea of Agile (maybe Scrum specifically) thinking is that you release and retrospect/rethink often, instead of long-term working on unlaunched projects from an ancient plan. I guess if you skip the rethink part than you aren't doing sprints property. An insight of Agile is that your have to pick either a feature based release schedule or a time based release schedule, not both, which is impossible and that time-based is better.