Timeline for Integrating Part Time Workers (Students/Interns) into a Kanban System
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 18, 2020 at 13:25 | comment | added | nvoigt | Well, everything else requires extra communication aka extra work. So you need to decide if your priority is reaction time or throughput. Having tickets wait for days improves the number of tickets you get done because work is done efficiently on every ticket with no overhead, while having someone else pick them up is more work per ticket, but the ticket gets closed faster. There is no silver bullet here, no right or wrong. You need to prioritize one of them and it's up to your organisation which one it should be. | |
| Mar 18, 2020 at 12:11 | comment | added | Aaron Wallace | Good point, this shouldn't effect the rest of the available WIP. I will reflect that back to the group. However, with regard to cycle time for student work vs cycle time for full time work, how would you go about addressing this? There's an automatic 2.5 days added to cycle time of a story each time a student doesn't finish his work. Do we just accept that? Or is there perhaps another strategy lying around for dealing with that? | |
| Mar 18, 2020 at 8:43 | history | answered | nvoigt | CC BY-SA 4.0 |