After years of going around in circles, I\u2019m going to get it done.<\/p>\n

A set of quality metrics that help improve productivity, and I need our community to pitch in..<\/p>\n

I\u2019ve gone through relevant content I could find, and to be honest there is just so much on this topic, both good and bad content.<\/p>\n

The mistake I have done and see other do is, we measure things we \u2018think\u2019 will generate value, like automation coverage, but never the actual outcome we want \u2013 time to market and product quality.<\/p>\n

Also there are some process factors which usually get skipped, which are also responsible for hitting these goals<\/p>\n

In lieu of these, want to classify the metrics in three categories with some \u201cSAMPLE\u201d metrics, not an exhaustive list, just to explain the heading better.:<\/p>\n

\n
• Practices maturity\n
  \n
  • g. Scrum ceremonies and best practices in them<\/li>\n
  • Three amigo sessions<\/li>\n
  • Defining the complete user journey for each epic & feature<\/li>\n<\/ul>\n<\/li>\n
  • Continuous testing\n
    \n
    • Automation pyramid<\/li>\n<\/ul>\n<\/li>\n
    • Business value\n
      \n
      • Time taken from pull request to ready for demo<\/li>\n
      • Trend of issues coming from support which have to be fixed<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n

        Under these three headings will be a list for each.<\/p>\n

        Thoughts?<\/p>\n<\/div>

        <\/div><\/div><\/div><\/div><\/div>\n","protected":false},"excerpt":{"rendered":"","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[52],"tags":[],"yoast_head":"\n