tiagogm

4 ms·

1. 1.▲
   by tiagogm 5y ago

   You don't need to discuss everything. The the oh-so-common 2 hour+ full team meeting scoping session, where half the team dosen't care what the other half is talking about since it's irrelevant to them - it tires everyone ou
2. 2.▲
   by tiagogm 5y ago

   In my experience AB testing has a time and place - and that is after a certain level of traffic load and product/feature maturity and only to "validate" certain hypotheses. For low volumes of traffic AB testing would takes ag
3. 3.▲
   by tiagogm 5y ago

   Plum Guide | Backend Engineers and Frontend Engineers | Fully Remote (Europe & UK Only) | Full-time Plum Guide is on a mission to solve the uncertainty of travel. We find and curate the best home on the planet, using a mix of humans an
4. 4.▲
   by tiagogm 5y ago

   True, I do find it easier and a less time consuming to break a large piece of work in around 2day chunks (for example) than using different sizes or trying to decide if something is 3 or 5. In the end, regardless of whatever scoring strateg
5. 5.▲
   by tiagogm 5y ago

   Kanban lends itself well to this. Breaking down work into similarly sized tickets/units can, over time, be used to predict delivery/capacity (which one can use Cycle time to calibrate) Even neater with enough data it becomes possi