![]() ![]() It is possible to add it to another board if you want, but you have to copy it and it is not updated when the original is. Every new card created is bound to a specific board. Trello has a really simple and clear logic. The most important difference between Trello and Targetprocess 3 is how they deal with cards. They support 5 people for free! Just perfect for our little team! The product is more complicated though so you have to give it some time in the beginning. have the same user stories but view them in a scrum, a kanban or scrumban board just as easily. When the time came it popped into my mind. There was in fact a tool in my presentation list which showed a lot of promise but was at Beta at the time. You can find some Trello addons of course (see above) but you cannot rely that they will do everything, plus they do not work in your mobile edition and not everyone uses the same web browser.Īs a result we decided to change our development process tracking tool and use Trello for our internal project management needs only. Plus we wanted to have different layouts apart from Trello’s standard and we also needed some extra features like sorting or tracking time. The problem was even worse in the mobile version. At some point we had so many cards in Trello boards that we had to scroll all the time. Still, as the development of our product gradually progressed, we realised we needed something more. It has a nice mobile app, A LOT of ADDONS (check Chrome Web store for example Scrum for Trello, Boards for Trello, Points for Trello , Kanban WIP for Trello and many more!) and many fans/followers. Development, Customer Requests, Things to Do etc. Trello is a really simple, intuitive, fast and free tool! You can create boards for every process you can imagine. Trello was one of them and when the moment came (while working on Blendo with my team) we needed a tool for our software development process, we initially went with that ( here is how we used it). At the presentation I introduced (or rather scratched the surface of) a number of tools for agile development. You can typically get there either by using a whiteboard and some post-it’s or by picking a tool that can solve the problem for you.ĥ months ago I made a presentation for our monthly Agile Meetup regarding such organisational tools. One of a team’s initial tasks is the selection of an appropriate work process, a way for its members to collaborate efficiently. This post (which will be completed in two parts) is meant to share our experience on the subject and describe both the tools we end up using and the process we follow. If so, you probably searched for tools that could make it work better for everyone. ![]() Have you ever been on a team? Have you tried to collaborate efficiently? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |