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 | |
Results tagged with release-planning
Search options answers only
not deleted
user 30
3
votes
In scrum, when do developers typically check their sprint code into production?
This is going to be highly dependent on the context.
I'll start off by saying that "checked into production" doesn't mean anything. Is that "checked into an integration branch in source control" or "c …
- 19.9k
4
votes
Accepted
Giving credit via Scrum or Kanban boards to developers participating in release-management a...
The purpose of a board is not to give credit to developers. The purpose of a board, especially a Kanban board, is to visualize the workflow.
In this particular case, I see a few possibilities. However …
- 19.9k
2
votes
How should you do long term releases with Kanban?
With Scrum you can try to plan longer releases using team velocity. If
team velocity is 100 Story Points (SP)/Sprint and the Product Backlog
has 1000 SP then you can say you can finish in 10 Sprints. …
- 19.9k