Issue link: https://read.uberflip.com/i/1198887
4.0 Comparison of team organization frameworks Hopefully, it is clear how both Kanban and Scrum would substantially change the way an engineering firm organizes itself in the delivery of work. Both processes put a stronger onus on the Project Manager to be organized in the preparation of tasks and responsive to the needs of the team. In many ways, these processes turn Project Managers into servant leaders who strive to clear the way for design work to get done with minimum disruption and the highest level of efficiency. The table considers the approaches in terms of their ability to address productivity issues in engineering teams: Productivity Challenge Business as Usual Kanban Scrum Creates a structure for planning work in advance Minimizes context switching by giving engineers clear focus & priorities Easy for everyone to see why a task is blocked and who is responsible for unblocking Easy to track who is/has reviewed tasks Easy to know exactly what someone is working on at any given moment Reduces idleness by showing what to do next when blocked or finished work Reduces working to deadlines by recognizing those who get tasks done efficiently Supports realistic estimating of effort and tracking of time to do tasks Creates a sense of progress and work being completed Sometimes not Typically not Sometimes true Typically true Clearly business as usual in different engineering firms will have different outcomes. However, the resolution of the above issues is more likely to be down to a good culture or strong leadership rather than an effective framework being in place. Applying lessons from software design to building services engineering 11