Search Results
Search type | Search syntax |
---|---|
Tags | [tag] |
Exact | "words here" |
Author |
user:1234 user:me (yours) |
Score |
score:3 (3+) score:0 (none) |
Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
Views | views:250 |
Code | code:"if (foo != bar)" |
Sections |
title:apples body:"apples oranges" |
URL | url:"*.example.com" |
Saves | in:saves |
Status |
closed:yes duplicate:no migrated:no wiki:no |
Types |
is:question is:answer |
Exclude |
-[tag] -apples |
For more details on advanced search visit our help page |
Use this tag for questions related to a "Sprint", which is a time box used for iterative/incremental development in Scrum. The term is also used by various other agile frameworks that have borrowed the term from Scrum, and is currently considered on-topic for non-Scrum frameworks that use the term for planning or time boxing even if the specific implementation details vary.
3
votes
6
answers
298
views
Long running product development project
We do split them into small tasks and progress developing them in each sprint, but it ready for first demo only after 2-4 sprints and ready for QA/production after 5-8 sprints. … On the other hand in same release we have small features or enhancement which are much smaller and can be production ready in single sprint or two... …