Timeline for Does the Scrum Guide Specify How Often to Release QA/Test Builds?
Current License: CC BY-SA 4.0
12 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Apr 18, 2019 at 12:27 | answer | added | kriscorbus | timeline score: 0 | |
Apr 18, 2019 at 12:17 | review | Suggested edits | |||
Apr 19, 2019 at 7:58 | |||||
Apr 5, 2019 at 15:43 | answer | added | Thomas Owens♦ | timeline score: 0 | |
Apr 5, 2019 at 14:15 | comment | added | Bryan Oakley | You asking if the guide mentions something, after specifically saying you read it and saw it didn't mention something? What kind of answer are you expecting other than "I read it, and no, it doesn't mention it"? | |
Apr 5, 2019 at 13:01 | answer | added | Dan Ray | timeline score: 0 | |
Mar 12, 2019 at 20:17 | comment | added | Christian Findlay | There are a lot of dictates in the official guide. If dictates make for less agility, Scrum ain't very agile. | |
S Mar 12, 2019 at 18:55 | history | suggested | mrflash818 |
seems to do with agile, so added the agile tag
|
|
Mar 12, 2019 at 14:43 | review | Suggested edits | |||
S Mar 12, 2019 at 18:55 | |||||
Mar 12, 2019 at 7:29 | answer | added | TheFogger | timeline score: 0 | |
Mar 12, 2019 at 6:20 | comment | added | Doc Brown | If there would be some "dictate by an official guide", that would not be very agile. The answer to your question is IMHO the same as the top answer to "How often to release" from your link above: whenever appropriate. Note Scrum tries to be a generic framework, but build times and QA requirements still vary heavily from product to product. So there is no way around using your own brain and think what is appropriate for your software and your team. | |
Mar 12, 2019 at 5:54 | answer | added | Euphoric | timeline score: 8 | |
Mar 12, 2019 at 4:49 | history | asked | Christian Findlay | CC BY-SA 4.0 |