So I handle this in one of two ways depending on the needs of my company. So first, you use pivotal tracker so you can do it the "pivotal way". (* Disclaimer:

So I handle this in one of two ways depending on the needs of my company. So first, you use pivotal tracker so you can do it the "pivotal way". (* Disclaimer: I am not a pivot but I worked with them for about 2 years as a client in their office.) Basically it's the extreme programming methodology. Have a prioritized backlog. Make sure items aren't too big (pivots shoot for 2-4 items complete per pair per day). Do not plan out a week at a time. Just make sure everything in the backlog is sized and appropriately understood by anyone on the team at all times. When a team member needs something to do, take the top item. It works surprisingly well. If you have a new bug and it takes priority over everything else, it's the top item on the list and the next available person takes it. The most important thing is always the next thing. After a while, you get used to people understanding how the backlog works in the business and if they want new big features, they stop adding requests to the top of the backlog. Second, the "Basecamp way". Much longer time frames (I use 6 weeks). Buckets of work that are split out. Here's a page that describes it: https://m.signalvnoise.com/how-we-structure-our-work-and-teams-at-basecamp/ https://m.signalvnoise.com/how-we-structure-our-work-and-tea... I've found great success in both. I'm currently using the Basecamp way. I'm very open to questions if you have them.