This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-06-23
Channels
- # ask-the-speaker-track-1 (171)
- # ask-the-speaker-track-2 (401)
- # ask-the-speaker-track-3 (250)
- # ask-the-speaker-track-4 (194)
- # bof-arch-engineering-ops (3)
- # bof-covid-19-lessons (9)
- # bof-cust-biz-tech-divide (8)
- # bof-leadership-culture-learning (19)
- # bof-next-gen-ops (46)
- # bof-overcoming-old-wow (8)
- # bof-project-to-product (10)
- # bof-sec-audit-compliance-grc (9)
- # bof-transformation-journeys (52)
- # bof-working-with-data (33)
- # discussion-main (885)
- # games (335)
- # happy-hour (129)
- # help (411)
- # hiring (43)
- # lean-coffee (17)
- # networking (8)
- # project-to-product (1)
- # snack-club (44)
- # sponsors (77)
- # summit-info (437)
- # xpo-datadog (2)
- # xpo-digitalai-accelerates-software-delivery (28)
- # xpo-github-for-enterprises (25)
- # xpo-gitlab-the-one-devops-platform (25)
- # xpo-itrevolution (3)
- # xpo-launchdarkly (3)
- # xpo-pagerduty-always-on (1)
- # xpo-planview-tasktop (6)
- # xpo-slack-does-devops (13)
- # xpo-snyk (5)
- # xpo-sonatype (12)
- # z-do-not-post-here-old-ask-the-speaker (176)
@fernando.cornago how do you cope with this level of transparency within your organisation?
@fernando.cornago how do you cope with this level of transparency within your organisation?
@fernando.cornago442 ย how do you cope with this level of transparency within your organisation?
fyi, more comments on keynotes are in #ask-the-speaker-keynote
Welcome speakers @nic.whittaker and @michellecmoss after the break!
Are you guys live?
Are you guys live?
itโs weird how it doesnโt make a difference though. I recorded mine on Saturday (it will be played out tomorrow morning) and I feel exactly the same as if I was talking live! Only I know all the things which donโt go quite how I wanted already!!! :rolling_on_the_floor_laughing:
Oh ok thatโs what l thought - as TEH @patrick.debois256 said youโll be totes fine, questions were gentle so far
I love this community - I donโt think Iโve spoken at another conference where we can be so open about how we feel.
and yeah @nic.whittaker you already know you smashed it ๐ weโll confirm that for you in about 40 minutes ๐
l dunno - lโm loving virtual vs in person keynotes - right before my turn lโd be obsessing about the fear of climbing stage steps in heels - lโm sure you can relate ๐
Yes, I am focusing in on our infrastructure, but it is hard to ignore the application design. I am no stranger to agile transformation, i lead a grass roots transformation in a US government contract setting
Ironically, if i were to do it again, i'd focus on the core infra teams first then deal with the app teams
IMO, the mindset leap is smaller/more natural for Devs compared to the infra teams
That is very reassuring, i have been thinking I was taking the wrong approach this time, but I agree getting the core down right is the first key
I am trying to build a linkage of the core teams that enable security, audit, network ops, and enterprise architecture. I am getting the management team on board with this concept
โDevops is about collaborative behaviour across the whole orgโ ๐
โPeople who waterfall in their headโ is what l call them
โPeople who waterfall in their headโ is what l call them
i've seen it done different ways. for us, it was about co-locating teams to address ways of working and friction between teams, as well as to double-down on limited coaching resource.
but i've seen it used to force all new teams for the first x weeks of delivery through a cookie cutter
This is amazing @nic.whittaker and @michellecmoss! @andrew.salt If you stay on track 1 right after this, @nisha.parkash and I talk specifically how COMCAST/SKY got started with Dojos.
@michellecmoss What was the objective of your Dojo? Was it dev focussed, ops focussed, culture focussed... a mixture?
@michellecmoss What was the objective of your Dojo? Was it dev focussed, ops focussed, culture focussed... a mixture?
We started with like-minded project teams as the connection but then found there was scope for shared outcomes and collaborative ways of working. Once they started talking they found more commonality that we had realised.
@michellecmoss...I'm working with Ops heavy orgs, with some dev - so I'm interested to see if the Dojo approach can work for Ops orgs
@michellecmoss...I'm working with Ops heavy orgs, with some dev - so I'm interested to see if the Dojo approach can work for Ops orgs
I have started to do a similar approach with some OPs teams to get them connecting better
You said something about getting leaderships to resolve conflict in front of an audience... could you elaborate on that please? How many people / who / what sort of issue made it to that forum?
You said something about getting leaderships to resolve conflict in front of an audience... could you elaborate on that please? How many people / who / what sort of issue made it to that forum?
In the Big Room event, we had way more than double the demand for capped Capital and Resource challenge. Everything was more important than everybody else's thing. The C suite had to argue it out and rationalise the final decisions in the room.
Did they follow through on those @nic.whittaker?
On the decisions? Yes - the funding for the quarter was signed off at 5pm on day#2 of the session. Done.
I think that the speed in which people picked up on the objectives was the most impressive thing
Magical mega team who felt Psychologically Safe moment
I can imagine they'd be under pressure to collaborate constructively with 200 people watching... more of a 'yes and' style than behind closed doors perhaps
actually the first 30 mins of the C suite argument happened in a closed room. but then they got turfed out.
@nic.whittaker @michellecmoss How many PIs have you gone through now and how much have you adapted the process? How have you adapted the PIs for the current work situation?
@nic.whittaker @michellecmoss How many PIs have you gone through now and how much have you adapted the process? How have you adapted the PIs for the current work situation?
totally adapted - but mainly because of Covid - see last few minutes of this talk
"individually we may go faster but together we will go further"... wise words
"individually we may go faster but together we will go further"... wise words
And good luck to your company and yourself to get out of this crisis more strongly! ๐ช:skin-tone-3: โ๏ธ
Such a quick cross-over ๐ -- @nisha.parkash and I are here to answer questions for The Comcast/SKY Dojo!
@michael_winslow good callout to the whitepapers - this one (and many others) on the website and all worth reading
@nisha.parkashย &ย @michael_winslow, did your DOJO's include Product Management skills? @Fannie Mae we are leveraging DOJOs to help our Business Analyst to Product Owner journey along with helping the tech teams with techniques like TDD, Pair/Mobbing, Pipeline automation, Cucumber, etc.
@nisha.parkashย &ย @michael_winslow, did your DOJO's include Product Management skills? @Fannie Mae we are leveraging DOJOs to help our Business Analyst to Product Owner journey along with helping the tech teams with techniques like TDD, Pair/Mobbing, Pipeline automation, Cucumber, etc.
Hi Jose, thank you for your question, we didn't focus on having Product Management but we made sure we had Product Management presence
@nisha.parkash, @michael_winslow did you tried other tools than miro eg. Mural? Does someone know a good comparison between such tools?
@nisha.parkash, @michael_winslow did you tried other tools than miro eg. Mural? Does someone know a good comparison between such tools?
Hi Rene. This group did not work with other tools. A couple of us had previously worked on projects with @dominica where she was using Mural. She did all the heavy lifting to try several tools! Shout out to Dominica!
Really enjoying this talk @nisha.parkash @michael_winslow itโs giving me all sorts of ideas
Really enjoying this talk @nisha.parkash @michael_winslow itโs giving me all sorts of ideas
Thanks Liz! We are hoping that a lot of folks are in a similar situation as us which is ... we did not yet have widespread buy-in from Senior Leadership.
We are actually getting a lot of additional support simply by putting this talk together and presenting it to leadership!
You showed some great ideas around cross-team, international collaboration and learning, I really appreciated it
Great breakdown of DOJO benefits as well. And a session with @michael_winslow background makes me want to rewatch Coming to America later today. Win/win
Great breakdown of DOJO benefits as well. And a session with @michael_winslow background makes me want to rewatch Coming to America later today. Win/win
@nisha.parkash and @michael_winslow appreciate your talk. I'm an Agile/DevOps coach and would love to connect, share, learn more about DevOps Dojos.
@nisha.parkash and @michael_winslow appreciate your talk. I'm an Agile/DevOps coach and would love to connect, share, learn more about DevOps Dojos.
Thanks Michael and Nisha - Linked in connections sent. Watch out for https://www.linkedin.com/in/johannt/
Thanks Michelle! We appreciate the mention of Dojo in your talk as a perfect handoff to ours!!! ๐
Why do you emphasize the many.many relationship as a difference to DevOps? Don't we also have many:many relationships in DevOps when we look a large, complex, global product develpment?
Why do you emphasize the many.many relationship as a difference to DevOps? Don't we also have many:many relationships in DevOps when we look a large, complex, global product develpment?
In my experience the m:m relationship in data analytics is prevalent in every organization of any size. The mix of low-code BI tools and lots of back end databases and a culture of separation make this tough in the data world
really keen to hear success stories on DataOps - please share - I'm currently working on a CI/CD pipeline for Snowflake+Azure+PowerBI
really keen to hear success stories on DataOps - please share - I'm currently working on a CI/CD pipeline for Snowflake+Azure+PowerBI
Fantastic. We collected a bunch of stories: -ย ย ย ย ย ย ย ย ย Videos:ย https://bit.ly/2FmFNRZ -ย ย ย ย ย ย ย ย ย Blog: https://medium.com/data-ops -ย ย ย ย ย ย ย ย ย SlideShare: https://bit.ly/2FHN3Hu
Great insights into this increasingly important topic, probably greatly undervalued
@michael.palzer @stephan.stapel supply chain inspires my thinking as well. This is just software supply chain. Minimize touch to reduce cost and damage. JIT to minimize storage cost and aged inventory.
Seeing all this DevOps talks on question pops in my mind: How do you orginize @stephan.stapel do you have an actual Ops team? Or single teams that are cross-disciplinary?
Seeing all this DevOps talks on question pops in my mind: How do you orginize @stephan.stapel do you have an actual Ops team? Or single teams that are cross-disciplinary?
Yes, they are still around. They care about the legacy applications until those are reengineered or replaced. Transferring people into new roles is really tough. Some bits about that in a minute.
do you think that getting rid of those traditional teams is important to go towards company-wide devops?
No, probably not getting rid. You will always have fields where it doesn't make sense to do DevOps, e.g. for hosting standard applications like timekeeping, document management, jira, wiki etc.
Concerning transforming: we rather see flucuation than transformation. Lots of Ops people aka classic admins want exactly that job. So they'd rather leave than change.
@stephan.stapel Iโm a big believer of blending roles however one of the challenges iโm facing frequently. How to blend roles if certain activities are being taken care of outside of your organisation and in respect out of your circle of influence? (eg. external development vendor)
@stephan.stapel Iโm a big believer of blending roles however one of the challenges iโm facing frequently. How to blend roles if certain activities are being taken care of outside of your organisation and in respect out of your circle of influence? (eg. external development vendor)
good point. That's one of the reasons which we are insourcing as much as we can. Blending roles need real interest in company, culture etc. Interest is difficult if you're just temp. Does that answer your question?!
when you say insourcing, you mean building software by in-house developers iso buying off the shelf applications?
Insourcing goes further than dev only. Also PMs, POs and all other roles that were partially external before.
Also, we have a lot of bespoke applications, there is no standard software in parcel business ๐
@stephan.stapel @michael.palzer great talk! thanks! who was the initiator of the transformation in the company? someone at top management level or it happened from the bottom? did you see any conflicts between bureaucratic processes management (I don't necessarily mean that bureaucratic is bad for a huge company) and the innovation? how did you solve this?
@stephan.stapel @michael.palzer great talk! thanks! who was the initiator of the transformation in the company? someone at top management level or it happened from the bottom? did you see any conflicts between bureaucratic processes management (I don't necessarily mean that bureaucratic is bad for a huge company) and the innovation? how did you solve this?
We started in the middle. And found challenges on every level. Imho, it's not the top management that is per se bad and the 'bottom' that is per se good. Everyone needs to learn and change.
And bureaucratic process management: yes. Of course. We are a big company, so there is a lot of "interest" in bureaucracy. Fortunately, we found company in our company that helped us getting rid of odd things like 'annual investment requests'.
gotcha, thanks! did you start with some internal "startup-alike" project or with the transformation of existing products?
we used existing products. But there was a great wave for us to catch. With change of the CIO, a big IT renovation project was initiated. It helped a lot to be able to change the application landscape and hire additional (fresh, good) people
Personally I don't like internal startups. That might turn out to be an internal Disneyland, loosing contact to reality (for the startup and also for the rest of the company)
Aother point concerning internal startup: if you hate your org so much that you create a small new one, we not change the oiginal org?
this might really depend, consider some highly regulated business, like healthcare, 99% of seemingly unnecessary practices there I believe is to prevent really rare cases that happens 1 of 10,000 times, but still can really hurt, so while they might be willing to move, this could bring some intertion
it's like microsoft excel still having 1900 a leap year (while it's not) for a backward compatibility with lotus 1-2-3 from 80s
good point. I remember conversations with healthcare colleagues that weren't able to step from cvs to subversion because of regulations. Glad to work in a deregulated business. I guess the path is far harder.
"Manage your management". As @nasello.scott says, "hacking the biggest undocumented API"
"Manage your management". As @nasello.scott says, "hacking the biggest undocumented API"
We have in our presentations too. I quote him constantly. You get the best quotes from DevHops sessions. ๐