Timeline for Incorrect scrum meeting format not allowing for enough participation from developers
Current License: CC BY-SA 4.0
11 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Oct 16, 2018 at 6:00 | history | tweeted | twitter.com/StackWorkplace/status/1052076796500500480 | ||
Oct 5, 2018 at 17:50 | answer | added | Jamie Clinton | timeline score: 1 | |
Oct 5, 2018 at 17:19 | comment | added | paparazzo | Not a good situation but as a contractor I think you should stay out of it. | |
Oct 5, 2018 at 17:16 | history | edited | TCFP | CC BY-SA 4.0 |
One small detail added
|
Oct 5, 2018 at 16:32 | answer | added | Omar Martinez | timeline score: 5 | |
Oct 5, 2018 at 16:22 | answer | added | Daniel | timeline score: 2 | |
Oct 5, 2018 at 16:20 | review | Close votes | |||
Oct 11, 2018 at 11:03 | |||||
Oct 5, 2018 at 16:01 | comment | added | rath | Also, assigning tasks in an ad-hoc manner is a lot worse in my opinion, and transitioning to a ticket mentality would be my priority. Something like if it's not on $task-tracker, it doesn't exist would be nice | |
Oct 5, 2018 at 16:00 | comment | added | rath | Don't have the time for a full answer, so, a comment: Do you do sprint retrospectives? This seems to be the natural place to bring this up, but it would have to be done incrementally. | |
Oct 5, 2018 at 15:55 | review | First posts | |||
Oct 5, 2018 at 20:28 | |||||
Oct 5, 2018 at 15:54 | history | asked | TCFP | CC BY-SA 4.0 |