![]() At the client’s next convenience, he or she can go down this list and provide feedback. Once I complete work on a card, I move it to Ready for Review and notify the client. For large projects with many collaborators, putting a face to each card explains who’s doing what, and keeps us from stepping on each other’s toes. This is a low-touch way of keeping the client informed of exactly what I am working on at any given time: no tedious status meetings or taps on the shoulder needed. In Progressĭuring the week, whenever I am working on implementing a particular feature, carrying out a task, or fixing a bug represented by a card, I will move that card to In Progress and put my avatar on the card. This means fewer surprises and happier clients. The This Week list is not set in stone, but it does give the client a good idea of what I can accomplish and what to expect in the coming week. I’ll make an informed guess as to the number of cards that can “fit” into This Week, based on previous estimates, the complexity of the tasks, and observations of how fast the development progressed in prior weeks. highest priority) cards from the Backlog and move them into This Week. This WeekĮvery week, first thing on Monday morning, I’ll take the topmost (i.e. This process ensures that the highest priority items will always be at the top of the Backlog list. Can we drop or postpone any existing tasks to accommodate the new ones?.Will adding these new tasks increase the scope, and thus the budget?.Regularly during the project, perhaps in a quick ad-hoc phone call, we’ll review the list and decide which of those new ideas are feasible. I encourage my clients to add new requirements, feature requests, and changes as cards to the Backlog list as soon as they arise. For a project to be successful, it is important to take these changes in stride. New requirements will be discovered or be proposed. However, as carefully as I plan a project, or as confident as my clients are in their requirements, inevitably those plans will change. This list represents everything I aim to accomplish during the project, sorted by priority. It really doesn’t get much simpler than that! My development project boards on Trello tend to look like this, albeit with many more cards.Īt the start of the project, all cards begin in the Backlog list. Prioritizing and tracking progress on these cards is as simple as dragging them from one list to the next. I set up each development project with its own Trello board and create these lists:įor large projects with lots of integrations or a complex release processes, I might also add:Įach list contains cards that represent tasks, features, bugs, or ideas. ![]() ![]() I hope this article gives you a better idea of how I use Trello perhaps you will find some ideas to apply to your own projects, too! My typical board In my experience, this setup strikes a good balance: enough structure to keep everyone informed, but not so much friction that it slows down development. They value being able to see the progress of the project at a glance, and the boards make it clear where and when their feedback is needed. I have heard nothing but positive feedback about Trello from my clients. In this article, I want to show you how I set up Trello boards for the day-to-day management of my freelance Rails development projects. Trello is a fantastic online and cross-platform tool for organizing ideas.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |