21 June 2017

What I learn from 015 : article by Richard White titled "How We Use Trello & Google Docs to Make UserVoice Better Every Day"




"How We Use Trello & Google Docs to Make UserVoice Better Every Day" by Richard White

    Jira and Confluence tools from Atlassian are one of the well-known standard tools used for product management and team collaboration. In the article "How We Use Trello & Google Docs to Make UserVoice Better Every Day" by Richard White, we can see and alternative way to do product management using Trello a great "get things done" task tool and google docs.
It is worth reading it.

What I learned from this article:


  • A person is not required to take the top card from the list but rather the top card that it feels most comfortable to handle. 
    • It is a great idea. For example for pair programming when you can switch pairs between tasks as different people like different things and want learn different things, so they can switch pair on the ticket basis.
  •  Etiquette is that you should never have your face on more than 2 cards at a time: 1 major project and 1 minor.
  • Something that I should work on in the future. Currently, I do not follow this rule as for when I finish the task but I need to wait for our CI to finish successfully, I have a habit to pick-up something new.
  • If a bug is considered as “Critical” by the customer team then it can be pick up by “developer on call”.
  • They set limits to pick 7 bugs per week. It prevents development to be disturbed because there are always bugs and the customer team always wants them all fixed. They learned that set a constant throttle of how much time they spend on bug fixing helps them to have more stable development.
  • If you don't have a dedicated support team, then having a limit for a number of bug fixes to do is crucial. I experienced a chaos when our team suddenly need to take care of support and it turns our development into a mess. We fixed it by having dedicated person who handles these issues.
  • We keep a list of areas that we think might need refactoring. Engineers take small cards when they feel like it and add them to in progress; larger cards need to be planned in the Next Up list.
  • It is a great idea to have 'spare time' to spend on improving code without hassle.
  • One of they board is called The Planning Board is where CEO, PM, and head of UX spend the majority of the time. It has the following columns: Next Up,  Spec (This means “someone needs to write a spec”.  Design (This means that the card needs a designer to take a look at it), Ready (We have a spec that’s been reviewed by the idea creator and by the design team. )
  • It sounds 3 amigos style meeting that helps sprint plan.
  • Have a single prioritised list for the product team to work from. Don’t have a separate system for bugs because from they experience having more than one list breaks down a prioritisation.


Overall, the useful article to read if you want to learn on how to organise your team when what tools can you use if you don't want to spend the fortune on Atlassian products.



FOLLOW AUTHOR:

LINKEDIN: https://www.linkedin.com/in/rrwhite/
TWITTER: https://twitter.com/rrwhite