Updates

Dec 7: ๐Ÿ“ƒ P85 Calculation and more configs ๐Ÿ“ƒ

Julian Colina
December 7, 2021
  • toc-h2
  • toc-h3
  • toc-h4
    โ€
  • toc-active

๐Ÿงฎ 85th Percentile on Cycle Time ๐Ÿงฎ

https://cdn.zappy.app/162a582b97a7dece5dc296122c716d3b.png

At Haystack, we want to give more actionable insights and decrease the amount of noise there is in the data. We have analyzed millions of pull requests and found that 85th percentile has higher signal and allows the team into better conversations.

We recommend using the 85th percentile when calculating Cycle Time allowing you to understand and take action on your software delivery pipeline.

You can configure it from Speed page (img) and learn more about P85 calculations from here.

โš ๏ธ Risk Limits โš ๏ธ

https://cdn.zappy.app/1862ee1a3bc11b5a78c0382b7507ed3f.png

Each organization has different needs. Some might use 2 approvals for pull requests, whereas others might want to improve their cycle time to less than 2 days.

You can now configure risk limits to fit your teams current needs. The changes will effect risks page, email and slack notifications.

๐Ÿ‘€ Preview Exclude Rules ย ๐Ÿ‘€

https://cdn.zappy.app/cf419b18bf5bbaa1b33dcb6d96b5a5c4.png

Each repository can have different patterns that are affecting the data. Some repositories might have certain bots commiting, whereas other repositories might have a process to merge the release branch back to trunk.

With new the Filters page you can check each pattern, validate if it is the correct pattern you'd like to exclude and make your data represent what your team actually works on!

โญ๏ธ Change Lead Time (Alpha) โญ๏ธ

https://cdn.zappy.app/c379c5d08d3a7abea76399c701917fe3.png

The change lead time is how long it takes a team to go from code committed to code successfully running in production. Elite teams can complete this process in less than one day, for low performers this process can take anywhere between one and six months.

Haystack now supports Change Lead Time allowing you to see your teams bottlenecks more holistically.

Note: Change Lead Time is currently in alpha stage for only selected users. Email support@usehaystack.io request access.

โœˆ๏ธ Single Sign-On (SSO) โœˆ๏ธ

Haystack now supports SSO with the providers above. To get access, email us at support@usehaystack.io

๐Ÿ’ก Improvements ๐Ÿ’ก

  • Bots comments are excluded from First Response Time and Rework Time calculations
  • Role field added to User accounts page
  • Export functionality added to pull request tables
  • GitHub link added to pull request tables
  • Throughput by member chart added
  • Benchmarks link added
  • Popup added when leaving configurations page when unsaved changes are present
  • Repositories page shows pull request count

๐Ÿ•ท Bug Fixes ๐Ÿ•ท

  • Filters issue fixed across the page changes
  • Team page with the auto-sync issue fixed
  • Multiple tags with the same commit issue fixed
  • Default sorting issues fixed for drill-down tables
  • Multiple tagged commit issues fixed

๐Ÿ—‘ Removed ๐Ÿ—‘

  • Concurrent work trend removed

โฐ ย In case you missed it ย โฐ

  • ๐Ÿ“’ EngProd Guide ๐Ÿ“’
  • ๐Ÿซ‚ Detailed Settings for Team Members ๐Ÿซ‚
  • โš ๏ธ New Risk: Commit Without Pull Request โš ๏ธ
  • ๐Ÿ“ˆ Risk Trends ๐Ÿ“ˆ

Keep up to date with feature releases here!

โ€

About the author

Julian Colina
CEO & Cofounder of Haystack.

Our latest news

Discover our latest articles, feature releases, and more!

Ready to get started?

Start Free Trial