> However, looking back, I don’t think we needed agile or sprints. The project is not big enough (in scope and size) to justify a system like that. But most of

> However, looking back, I don’t think we needed agile or sprints. The project is not big enough (in scope and size) to justify a system like that. But most of all, agile doesn’t fit in the context of this particular project, because the client changes priorities very frequently. As in, weekly, and sometimes daily. So sprint planning goes out the window every week when new requirements and priorities are discussed Sounds like you needed to be very agile! But maybe not Agile(tm). Honestly Kanban (what they were doing before) is a great fit for this sort of environment. But for a small team maybe you don’t even need that much structure.