Timeline for Influence code quality as Scrum Product Owner
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 26, 2016 at 11:44 | vote | accept | Stephan | ||
| May 31, 2016 at 15:19 | history | tweeted | twitter.com/StackProjects/status/737664764000784384 | ||
| May 31, 2016 at 13:37 | comment | added | Thomas Owens♦ | Is the external, visibility quality decreasing? That is, are the amount of issues in delivered products (both the software and any associated documentation products) increasing? Or is the problem simply in the quality of the written code in factors such as readability, maintainability, testability, etc.? | |
| May 31, 2016 at 10:05 | answer | added | CBRF23 | timeline score: 1 | |
| May 31, 2016 at 2:40 | comment | added | Todd A. Jacobs♦ | You can collaborate with the team to define a Definition of Done that produces increments of higher quality. You may need to define user stories that focus on team infrastructure rather than product features to make capacity available for it within the sprints. | |
| May 30, 2016 at 23:07 | answer | added | Ewan | timeline score: 1 | |
| May 29, 2016 at 21:12 | answer | added | Barnaby Golden | timeline score: 8 | |
| May 29, 2016 at 20:02 | history | asked | Stephan | CC BY-SA 3.0 |