Timeline for Lean or agile SaaS: deployment / release features during or after sprint
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 15, 2015 at 22:03 | comment | added | Will | I appreciate the particular point that "complete but undeployed work has no or negative value." I was thinking of it as no value, but I can see it could have negative value for several reasons: it is potentially piling up essentially technical debt of deployment tasks to be paid later, it carries the risk of having pending changes that may not be well understood (and/or bundling of more risk into a subsequent release), and it complicates communication of what's live with internal customers like product management and support. | |
| Oct 9, 2015 at 19:52 | vote | accept | Will | ||
| Oct 8, 2015 at 14:11 | review | First posts | |||
| Oct 8, 2015 at 19:34 | |||||
| Oct 8, 2015 at 14:08 | history | answered | Robin | CC BY-SA 3.0 |