piannaf’s avatarpiannaf’s Twitter Archive—№ 3,779

        1. This so resonated with me, I feel the need to thread my highlights kevlinhenney.medium.com/agility-speed-96057078fe40#cefb
      1. …in reply to @piannaf
        "Teams that aspire to be more agile have created currencies of story points and have ritualized development velocity. They have mistaken a weak proxy measure as a meaningful system of estimation, an indication of progress and a mark of quality. This is not agility."
    1. …in reply to @piannaf
      "we should be cautious of any language or technique that optimises around project management measures."
  1. …in reply to @piannaf
    "Software development is better thought of in terms of product development than project management, therefore time to market is typically less important than time in market."
    1. …in reply to @piannaf
      "Unaware of its origin story and intent, many now favour the word sprint over iteration because of the implication of raw speed.... Rather than being shielded from pressures and interruptions, teams routinely experience them with increased frequency and intensity."
      1. …in reply to @piannaf
        "The intent of story points is to focus on relative sizing independently of other expectations of time. The problem is that, in being numeric, story points become a currency susceptible to arithmetic, especially once they’ve been aggregated."
        1. …in reply to @piannaf
          "If keeping developers busy was the main goal of software development, all would be good… but the goal of software development lies in the development software, not the consumption of development hours."
          1. …in reply to @piannaf
            "The busyness of the development team is not that interesting or useful, but it is easy to measure and report... The degree to which the team is building the right thing in the right way at a good pace, however, is harder to assess... but it is meaningful and useful"
            1. …in reply to @piannaf
              To track velocity, focus on functionality completed (not functionality worked on), focus on functionality delivered (not functionality requested or promised), focus on functionality used (not estimates of business value), track defects (and time spent on defects), ... and so on."
              1. …in reply to @piannaf
                "Although we may find ourselves nodding along to or advocating the mantra of “deliver better software, faster”, we should pause a moment to realise that what we probably mean is “deliver better software, sooner”. The difference is both subtle and huge."
                1. …in reply to @piannaf
                  "if most teams chasing agility stopped chasing story points and forcing delivery, and focused instead on identifying and removing obstacles from the path of development, that would be a significant improvement on their status quo...
                  1. …in reply to @piannaf
                    .... This would definitely be leaner, but it would not necessarily be more agile. It would streamline the flow of development, but it would not necessarily improve the ability to respond to change."
                    1. …in reply to @piannaf
                      "Agility is not speed; it’s something far more useful and far more interesting."