3 ms·
Nice point. But I would argue that the stressors are the same kinds of deadlines as you would see in any professional organization. From my experience working o
by cmoses 17y ago
Nice point. But I would argue that the stressors are the same kinds of deadlines as you would see in any professional organization. From my experience working on a student developer team (attempting to use agile), the reason it doesn't work in a school setting is the lack of daily updates and meetings among team members since it's hard to coordinate the schedules any decent-sized team of students and to convince them to reorganize their workload to meet the weekly or bi-monthly deadlines. The worst case scenario is a lower grade on your project, rather than the stressor of losing your bonus or worse--getting fired.
- DanielBMarkham 17y agoI think I was unclear. Student agile and big-corp agile can have a lot in common. In really large organizations, developers can be multi-allocated to several different development teams and be working on 5 or 6 projects at the same time. In addition, slipping schedules is the norm. And you can have multiple channels of managers, making accountability problematic. So the stressors don't always apply at big companies either. That's why I use the startup metaphor. In the startup world, you produce value or you die. There are techniques to use, of course. You can insist on daily stand-ups and an hour or two of co-located time per day -- to the point of refusing to be on the team if it's not done. But that gets into a whole other area of courage and agile teams which is probably another thread.