I have had the opportunity to present this topic any many conferences this year and feel it is a critical topic for teams trying to make progress in their DevOps journey. Please feel free to continue the discussion with me on twitter @tomcudd.
This talk continues to be one of my favorites to give and I just keep getting the chance to present it. I will continue to submit it because it’s just a fun one. The Slides have been uploaded to SlideShare and my notes are mostly included here.
Continue reading “Are You Really Using Kanban or Just Making a List of Issues?”
Thanks for everyone attending the Nebraska.Code() Conference. After the jump, check out a previous version of my slides and some notes on the topic I collected. I’ll likely be updating the slides a bit more soon, and will post when that happens on twitter.
“It is better to ask for forgiveness than permission.” A statement like that is pervasive in an organization that follows a decentralized command and control structure. As organizations become more complex, it is nearly impossible for any single person to fully capture detailed information in making decisions. Yet, many companies still try to run significant decision making authority through single threaded resources.
The technology industry has embraced the DevOps definition around the idea that it is used to break down silos and barriers to teams working together. As a portmanteau, the word DevOps clearly states in its own name the purpose of the philosophy. However, just smashing together a development and operations team does not just automatically eliminate silos within an organization.
DevOps has many different meanings depending on the perspective and experience of anyone you might ask. The tech industry generally aligns on DevOps being a set of practices and culture that an organization adheres to in order to deliver operational excellence. DevOps should not be a team, a set of tools, or something you can bring in a consultant to apply to your organization. Excellent leaders in the DevOps space realize that self-reflection and attempts to correct any issues are the most effective ways to improve.
Thanks to Amegala for wrapping another great day of breakout sessions. I’ve embedded my slides on caching for anyone who needed to follow up on my talk. Feel free to reach out to me on twitter with any questions.
Thanks for all those who attended my breakout session “Apply Software Development Practice to Application Configuration”. And many thanks again to Amegala. The details and examples in this talk can be found on my original post here: https://tomcudd.com/software-development-practice-application-configuration/
If you have questions or want to continue the conversation, please follow me on Twitter.
Thanks again to the whole Amegala crew for putting together a great day of workshops and breakout sessions. I wanted to make sure to get my notes and the slides up tonight in case anyone is wanting to read up a bit more on Kanban this week. Also included are the links to the workshop exercises and a couple other ones I have looked at in the past.
Open office plans are yet again in the news as Apple’s new headquarters building plans initially included open office spaces for the engineers along with many stories of the frustrated employees being asked to work there. As someone who’s been working in a creative environment that embraces the collaborative space, there are times I find value in it. But I also work on the technical side of an agency which requires heads down time to get things done. I just remarked to someone today that a big pair of headphones is the modern day equivalent of a closed door to an office since nobody has doors anymore. I’ve never been one to listen to music to try and drown out the noise, but learning I need to find a way to focus an hour or so once a day. So I started looking at some options that might go well with some white noise or music.
Continue reading “Headphones for the Open Office”