The company I currently work for using KanBan, and while we have a general sense of direction in that we have a list of things that need to get done before a re

The company I currently work for using KanBan, and while we have a general sense of direction in that we have a list of things that need to get done before a release we don't really have much of a list of things that have to be done in a certain order (other than normal dependencies). This allows us developers to look at the KanBan board, pick the next task and start working on it. If for example right now I am not too interested in solving a scalability issue because it was only seen this one time and we can throw CPU power at it for now, I can move on to working on the logging/metrics stuff that interests me instead which will help us get a better insight into the system as a whole, and maybe that scalability issue will be solved differently because of more information. Yes, we have a set direction (government contractors generally do), but I have a lot of leeway in that I can choose what I want to work on. The same can be said for every other team in the company. It has allowed us to work together very well and yet at the same time makes it possible for all of us to work on things we thoroughly enjoy, AND time to switch off from one part of the project to another and solve another problem. Keep things mixed up and interesting.