This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
hello all! this is natasha gupta, speaker for the synopsys session on 'find fast, fix fast.' here to answer any questions you may have during the presentation in the slack channel!
4Reminder: The breakout sessions are starting in 5 minutes. Get in front of your browser and start navigating your way to whichever session you’re attending. https://devopsenterprise.slack.com/files/UATE4LJ94/F04DG604H1C/image.png
Welcome @natashag from Synopsys' team for our first sponsor session's Q&A. Thank you #C01TK0N13J5!
most welcome! please check out our blog at https://www.synopsys.com/blogs/software-security/ for more information and resources as well!
Hi all, coming up next is LinearB co-founder Dan Lines, presenting "Completing the promise of CI/CD with CM" Dan will be diving in Continuous Merge - what it is, why it matters and user evidence of it's effects. Continuous Merge blog: https://linearb.io/blog/continuous-merge/ Continuous Merge tool (gitStream): https://linearb.io/dev/gitstream/
A warm welcome to Dan Lines from LinearB for our next session's Q&A. We appreciate #C03DGPV75M2!
And to @necco from LinearB who is joining us today!
Hello everyone, I work with Dan and have been helping to drive the Continuous Merge movement. If you have any questions about Engineering Metrics or Continuous Merge, let's get a discussion going : ) Who here is tracking Cycle Time ✋
If you're using Cycle Time, I can definitely recommend checking out the Engineering Metrics Benchmarks: https://linearb.io/engineering-benchmarks/ We analyzed 1mil+ PRs to get these numbers.
The PR review process is almost always a Cycle Time killer. Why? Because we are treating every PR the same...
You know what people love? Estimated Review Times Knowing how long a review will take helps save time
This looks like a Slack bot, is it working with other instant messaging app? (e.g. MsTeams)
Does it work with Teams on the Gov Cloud?
gitStream can recommend PR Sizes, and WorkerB (slack bot) can remind team of the goals they set
For auto-approval, are these organizations not limited by things like model audit rule?
Not everyone is, or follows it for the matter. To be fair, in this case, gitStream is the reviewer.
Yeah makes sense! Like auto merges by renovate that the pipeline checks the success and then merges. Thanks this is really cool!
I have run into this issue as well but some of it might be the audit/compliance people I’m working with don’t fully understand what is happening
One of the coolest things about gitStream is that you can create your own repo rules using a .cm file vs. a readme file
Continuous Merge blog: https://linearb.io/blog/continuous-merge/ Continuous Merge tool (gitStream): https://linearb.io/dev/gitstream/
fwiw, SO temporarily banned ChatGPT created answers due to often being wrong. https://www.theverge.com/2022/12/5/23493932/chatgpt-ai-generated-answers-temporarily-banned-stack-overflow-llms-dangers
If you are looking to start an Engineering Metrics Program, check out http://Linearb.io and itself gitStream is completely free!
Reminder: The breakout sessions are starting again in 5 minutes. Get in front of your browser and start navigating your way to whichever session you’re attending. https://devopsenterprise.slack.com/files/UATE4LJ94/F04DG604H1C/image.png
Welcome @pmccarron from LaunchDarkly for our next session's Q&A! Thank you to our incredible Premier Sponsor #C01653T4GJC! 
Hi all! Thanks in advance if you choose to watch my talk on Full Stack Feature Flags. I'll be hanging out here so feel free to drop any questions in here or in #C01653T4GJC.
Welcome @dominica for our next session's Q&A. Thank you #xpo-planview-tasktop!
Thank you @mollyc
It's not an easy win if you're not set up & organized for change
The similarities between the 5 stages of grief and business transformation!! 🤯
Psychological Safety coming back again - I'm seeing a trend across a lot of the talks 😄
People (Culture) > Process > Tools. Psych Safety plays a bit part of that, for sure.
@marc.poulin For sure - if psychological Safety isn't table stakes, then problem.
When I was at Chrysler, during COVID I did an experiment. I stopped showing up to meetings. Nothing happened
Too many meetings IS too much WIP!
Have you noticed an increase in the amount of complaints about too many meetings since WFH? Anecdotally, I feel like I saw this a lot at my previous company which had very Agile methodology.
Agree! If you at the office, you can take a walk out for coffee or lunch - or just walk down the hall to meet - you're not expected to be in front of you screen all day.
I feel like asymchronous communication has a lot of the answer to this, but getting adhesion is challenging.
We had a survey where people talked about what wasn't working, and "too many meetings" was a top answer. However, many people also mentioned "meetings" in their answer to what WAS working. Lots of useless meetings, but when you get a meeting right, it's powerful
Good goal! Work to live, not live to work. #OptimizeForLife
Lowering WIP thru smaller batch size an automation is so powerful.
Tony went to his daughter's soccer game for the first time!
I see what you did there @dominica. 😉 "A best.... no, a good practice..."
hahaha - nice catch!
Tony started with a personal hypothesis. The data reinforced his instinct
Oooof... that cognitive overload hits home. The WIP coming from teams is real.
The WIP limit IS an enabling constraint.
Pull system - The departure rate is your capacity.
"Revenue protection" — I've always loved that phrase. Hi @dominica !!
I have a question about this slide. Our products go through a publishing process, so the waiting for release state is something that we do not have direct control on. Would you recommend that that be excluded from the calculation in that case?
@dominica something I still struggle with related to these flow metrics is how to coach people against the sunk cost fallacy. If the Product Manager or team determines that an idea should not be done (either it's still in the backlog or is in progress and they realize it's the wrong thing to build). Any suggestions on how to help people overcome this?
@shane.brauner Flow Load does not include the backlog in this example. It normally doesn't.
But it could if the backlog is a waiting spot from upstream workflow.
I personally see the internal backlog as Options that we could bet on, so the lead time for me doesn't start until we've agreed that we'll make that bet. For things coming from customer requests it's a bit different since you could start the clock from when they ask about it, or from when you've confirmed for them that you'll do it. Could work around that with a Backlog pool and an Options pool... but that feels a bit like hiding the times. What do you recommend?
@shane.brauner Wherever you set the clock to start is when Flow Load and Flow Time begin. Flow Time ends where ever you set the clock to stop - usually when it hits a done state.
ok, thanks. That jives with my prior understanding. I’m thinking we just track different stats for different types/levels of work. Differentiating a new initiative that would have to go through approvals / funding exercises vs. fulfilling a customer request vs. engineering initiated debt work would all have different start times.
It could halt. Or it's actively in progress and the PM/team realizes the feature won't actually help solve the user's problem / job to be done.
we promote cancelling such work, in which case it falls out of the metrics
one large telecommunications company found that 70% of stale work was cut by people no longer at the company
(Laughing, but not because it's actually funny, if you get my drift...)
Side note - I like how @dominica has all open-ended / powerful questions on this slide. No leading questions.
Like being held hostage by dead people. Or something like that. What a story!!!
"You best start believing in ghost stories. You're in one!"
Peter Senge has some great stuff about shared visions and current reality
Experiments require Daily Practice ---> Ideal #3 from The Unicorn Project
I've enjoyed this talk immensely @dominica Thank you!
Many Thanks! @acrocker3
Thank you @dominica for such a great presentation. Love the idea of using math to model what we do. Helps to explain causation over correlation. :-)
The e-book Making Work Visible is available for free (while supplies last), sponsored by LaunchDarkly. Grab your copy from their booth in Gather or in Solutions Hub: https://members.itrevolution.com/live/expo
Love the making work visible book, I'm only half way through it and it has already changed how I view time management
1Great job thank you @dominica!
👋 Hi everyone! My name is David and I am a Senior Data Scientist at Stack Overflow. I look forward to sharing how we think about measuring knowledge reuse. Please let me know if you have any questions.
Welcome @dgibson for our next session's Q&A Thank you #C03E0JH0LP9!
This track had multiple healthy reminders of casualties of WIP and ways to take some challenges back to leadership!
I love Stack Overflow!!! And @tal , of course!!! Hi, @dgibson
Sooner, Safer, Happier is also a very worthy read for this. I've read 28 books so far this year, and it's my favorite (along with several other IT Rev books)
I use Stack Overflow to solve big technology challenges — and to learn how to write correct YAML files. 😂
I've worked for organizations where this is the primary way to share :woman-facepalming: There are clearly better options!!
I feel seen. 😂 Luckily search on Slack is pretty good, but I've spent so much time scrolling on Slack trying to find things.
It only works if the message is out in the open. I've been on a campaign to discourage private questions and encourage public asking. Search is one reason.
Great idea! ^^^^ In fact, one of the founders of Slack competitor (that was acquired by Rally — Flowdock) described how that was his mantra: get knowledge out of email threads, and get as much interactions out in to the open.
The perpetual balance between optimizing for the individual versus optimizing for the team.
We had more or less addressed the "answering questions workload" by having support rotation so people could at least plan the answering questions time in their workday ahead of time.
I like the analogy of "automating the work of answering repeated questions"
(The full case study is in DevOps Handbook — I loved that idea so much.)
You can snag a DevOps handbook Companion over at the https://members.itrevolution.com/live/expo! 😉
Awesome — 62% of answers are viewed again by the same person. "I don't do git rebase often, so I need to learn how to do it again"
That and how almost half of dev find themselves answering questions that they’ve answered before are my favorite data points to share!
@dgibson that was awesome and you articulated how many developers feel about Q&A and knowledge transfer, thank you!
Thank you! Developers are already very comfortable with QA formats but no one wants to answer the same question over and over again
The long-form vs. questions piece is a huge takeaway for me. Thanks @dgibson!
Long-form is a large time investment to create and also consume. QA is easier to create, consume and keep up-to-date
I think there's also a psychological barrier: people sometimes see long form doc as something formal that they have to get approval to submit, or that they have to do Right. And I suspect lots of people tell themselves "oh. I'm not good at writing documentation," but I suspect there are fewer people by far who tell themselves "I'm not good at answering questions."
Reminder: The plenary sessions are starting again in 5 minutes. Start making your way back to your browser and join us in #discussion-plenary to interact live with the speakers and other attendees. https://devopsenterprise.slack.com/files/UATE4LJ94/F04DG604H1C/image.png
Reminder: Please submit your feedback for the talks you attended. It’s so valuable for us and the speakers. And after all, feedback is a gift and sharing is caring! Enter your feedback for those talks here: https://doesus2022.sched.com/ https://devopsenterprise.slack.com/files/UATE4LJ94/F04DG7DQMSS/image.png
