Timeline for How should we implement items from Sprint Retrospectives?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 8, 2012 at 15:29 | comment | added | Steve V | @CodeGnome he is project manager (we have another person as product owner); he is a scrum-master. I think we have some kind of "corporate" version of SCRUM (if it makes any sense) | |
| Nov 8, 2012 at 12:14 | comment | added | Todd A. Jacobs♦ | @SteveV If your Product Owner (or worse, a non-Scrum product manager) is running your stand-ups, then you're already off in the weeds. This is not Scrum, and it's unlikely to be agile. | |
| Nov 8, 2012 at 11:29 | comment | added | Stephan | Yes, the team. I edited my response accordingly. I guess you'll have to convince him then to add it. At least, you should be able to add it to the sprint backlog for next sprint (or at least bring it up again during next sprint planning). | |
| Nov 8, 2012 at 11:26 | history | edited | Stephan | CC BY-SA 3.0 |
added 4 characters in body
|
| Nov 8, 2012 at 11:03 | comment | added | Steve V | > You can only implement it if there is real value in it for your team, otherwise they won't do it ============== they - means team? oh, they would (probably) do it - at least it looked that way when the idea has been discussed during the retro; but (I don't know why) we have no budget for these things, our product manager (he is running standups) will forget about our shiny ideas by next morning - and that's understandable since nothing has been placed on the task board; so we go back to square 1. | |
| Nov 8, 2012 at 11:00 | history | answered | Stephan | CC BY-SA 3.0 |