That means that for right now, our short-term roadmap is oriented towards taking the steps we need to take to be in a good place to push those changes. Right now, Trello’s team is focused on working on a few large-scale priorities for the app itself-these are big changes that take a lot of time to put together. This Trello blog article gives even more detail about we act on your requests: Submitting a new feature idea We want to be careful to add the right features to Trello so that it remains a product that you love. Members of the various teams within Trello meet regularly to discuss the overall direction of Trello and what features will help move us in the right direction. We have an internal Trello Development board that we use to discuss features among the team and decide who will work on them. Review customer communication via Twitter, Facebook, our public development boards, and incoming email that raise common themes and excellent ideas to the team. This allows us to identify common themes and areas that need improvement. Sometimes this means not working on one thing so we can work on something else that's more important. What you want may already be solved! How we decide on new features Try a Google search for Trello your-feature, e.g. The idea you have may not exist in Trello, but there might be a workaround out there already. Our manual and programmatic adaptations, across a broad range of uses, provide the best kind of feedback to guide the future development of Trello.Do you have an idea for a cool new feature of Trello that you think could be the Next Big Thing™? This guide is here to help you understand how we keep track of feature requests as well as how to submit new ones. By enabling all users to simulate the feature manually and by enabling API-wielding users to simulate it programmatically, Trello meets our needs well enough.Īt the same time, crucially, Trello lays a foundation for improvement. Also, your notion of that will differ from mine. While I imagine that I'd want Trello to offer parent-child linkage, I'm still not sure precisely how I'd want it to work. That's another way in which Trello shines as a user innovation toolkit. What's more, I've done enough hacking with the Trello API to know that if I really need to automate that splitting and linking, I can. We're not dealing with that many cards, and it isn't too hard to manually split them apart and link them together. You might conclude, at this point, that we've outgrown the tool and should switch to one that automates parent-child linkage. We want those children to link back to their parent, and we want the parent to link to its children. That idea card may spawn three or four new cards as we move into the refinement phase. A card in the idea-capture phase will include discussion of the idea and will link to specs and related documentation. That's becoming a common operation for us. Cards in Trello, for example, can't spawn children that remain linked to their parents. We've used Trello to hammer out a team consensus about what ours should be, and it has been invaluable for that purpose.Īs we refine that workflow, Trello's generality becomes less helpful and we begin to feel the need for features that Trello lacks. But the ways in which our team enacts those universal processes are highly specific to our product and to our mix of personalities.Įvery team workflow is unique. The processes that we represent on our board are universal: idea capture, idea refinement, prototyping, development, deployment, support, bug triage. For example, we no longer have a list called Backlog. The names of the lists on our board aren't conventional. One of them, it turns out, is to evolve a workflow that makes sense to everybody on the team.Īfter several rounds of negotiation we've come up with an approach that makes sense to us. Teams need to figure out how to make best use of that toolkit. It's an all-purpose toolkit that provides a few basic building blocks: boards, lists, cards. Kanban? Scrum? Scrumban? I'm not entirely sure what those terms mean, but thankfully Trello doesn't care. But it doesn't prescribe any particular methodology. Trello supports the popular idea that software development tasks are represented on cards that move across columns on a board, evolving from ideas to specs to working code. A project management application developed by Stack Overflow co-founder Joel Spolsky, Trello serves as a user innovation toolkit.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |