aleixmorgadas’s avataraleixmorgadas’s Twitter Archive—№ 478

      1. If you are responsible for a teams User Story definition, one of the reasons I suggest to not have too much glaurality on tasks level, it's that it doesn't help the team to focus on delivering one thing at a time. 1/n
        Permalink On twitter.com Twitter logo aleixmorgadas’s avatar ♻️ 1 Retweets Mood 0
    1. …in reply to @aleixmorgadas
      It always depends on the situation, but my take is that you should find a balance to continuous delivery value to the user. Delivering a lot of tasks seems to boost output over outcome. 2/n
      Permalink On twitter.com Twitter logo aleixmorgadas’s avatar Mood +1 🙂
  1. …in reply to @aleixmorgadas
    If you started splitting too much, you might be hiding a problem with technical debt or team's cognitive load. Just postponing the actions required to address them until given a point, people starts moving really slow. 3/n
    On twitter.com Twitter logo aleixmorgadas’s avatar Mood -6 🙁
    1. …in reply to @aleixmorgadas
      Splitting too much to "show progress" to the people you are reporting is more like a palliative than a real solution. It might seem that works on the short term, but you're simply shotting in the foot by doing it 😅 4/4
      Permalink On twitter.com Twitter logo aleixmorgadas’s avatar ❤️ 1 Favorite Mood +5 🙂