As the network grows, we constantly need to check in on processes to see what’s working and what needs updating. The Do Stuff DoStuff (DSD) queue in Asana is one of those places that needed to be fixed -- so that’s what we did.
Starting today, we’re using a brand new DSD queue in Asana that will change how requests are organized and assigned. (If you don't have access to that link, shoot us an email and we'll get you squared away.)
The goal of the new system is twofold. First, we wanted to make it more clear to you what items we’re working on, and where they stand in order of priority. New requests will be processed weekly so you’ll get quicker feedback on tasks that you input. Second, we wanted to help our Product and Delivery teams sort out requests that aren’t urgent, or are better saved for a future episode. Organizing requests by area of focus will allow them to determine how best to allocate their resources.
Better communication and less pileup? Sounds pretty good right?
Important Stuff
Here’s some of the important stuff to note about the New DSD queue above:
- Add New Items: Here’s where all new items should be added. Found a bug or thought of something that could benefit you or your users? Create a new task and describe the issue -- no need to assign it or put it under a header, we'll do that for you.
- Headers: Once a week the DoStuff team will assign all new items to the proper header. By organizing the DSD queue into Metro sites, Admin, Fests, ECPs, and Backend, we’re hoping everyone will get a better sense of where new changes are coming and what areas need some work. Remember, you don’t ever need to assign tasks to a header. The DoStuff team will make these decisions once per week.
- Red = Request: All tasks assigned to REQ indicate a request that has not yet been confirmed as something we will definitely implement. See something in red that you feel strongly about? Let us know in the comments so we can take your ideas into consideration.
- Green = Gone to Dev: All tasks assigned to DEV indicate that we have a ticket in for our Developers to implement the change. These items are slated to be completed during the current Episode, but you can follow the task or comment on it to track its status.
- Blue = Bug: All tasks assigned to BUG indicate a bug that has been discovered. We prioritize bugs to be fixed more immediately because they disrupt the way the site should be working for you and your users.
- Hearts: You can still use Asana's "heart" feature to let us know the tasks you think are priority. Even if you don’t comment, a heart shows us that this request deserves our attention.
The Reference DSD Queue: An Archive For Old Requests
Some of you may be wondering at this point, what about the requests that don’t get sent to Dev? We’ve heard feedback in the past that we need better transparency about what happens to DSD items that aren’t implemented, so we’re adding a new Reference DSD queue in Asana.
This Reference DSD queue will serve as an archive for all the items that we decide not to dedicate current Dev resources to. In the past, some tickets would be closed out without a clear explanation from us. Now these “passed” requests (closed tickets) will be sent to the Reference DSD queue with a short comment after being processed from the New DSD queue.
The great thing about the Reference DSD queue is that anyone will be able to look up what items were passed on and why. This could happen for a number of reasons. Sometimes, we think it’s a great suggestion but it’s better saved for a future episode. Other times, we may feel that a request doesn’t fit with our current goals but want to archive the idea for later use, like when looking for inspiration for new product ideas during Episode planning.
We’re looking forward to your feedback, so go check out the New DSD queue now and try it out for yourself!
No comments:
Post a Comment
Thoughts to share? DO!