Coté

Delivery teams are now able to build services faster and easier. In July 2016, DTA had 14 apps in production and 50 apps in development. In October 2016, the numbers increased to 47 apps in production and 225 apps in development. Australian Government Cuts Release Time with Cloud Foundry, Iterates Faster - Cloud Foundry Live

Delivery teams are now able to build services faster and easier. In July 2016, DTA had 14 apps in production and 50 apps in development. In October 2016, the numbers increased to 47 apps in production and 225 apps in development. Australian Government Cuts Release Time with Cloud Foundry, Iterates Faster - Cloud Foundry Live

Delivery teams are now able to build services faster and easier. In July 2016, DTA had 14 apps in production and 50 apps in development. In October 2016, the numbers increased to 47 apps in production and 225 apps in development. Australian Government Cuts Release Time with Cloud Foundry, Iterates Faster - Cloud Foundry Live

Nicely moderated by Bridget. Some of my notes and highlights: Amy talks about pace of change, sustaining it in the beginning, etc. The amount of time it took us to get going was a surprise - was longer. If you can start to show results early, it helps build up momentum. “Having enough wins, like that, really helped us to keep the momentum going while we were having a culture change like DevOps.

From 451’s report on Google Next: Google believes that a hybrid architecture will persist in the coming years as enterprises continue to migrate workloads to various clouds. Its hybrid cloud architecture revolves around its virtual private cloud. Google VPC is an instantiation of GCP that can dedicate compute, storage and network resources to an enterprise. It is built upon Google's proprietary private global network designed for high reliability, low latency and hardened security.

Can we take that governance and work with the platform team to codify, to automate that which they were doing on a per application basis - that's, quiet frankly slowing down the delivery of the software - can we take that governance and can we have them work with the platform team to codfiy, to actually automate on a per application basis, have them expose that as a service on the platform -Cornelia Davis on governance and cloud-native, “Who Does What?

If there’s one complaint that I hear consistently in my studies of IT in large organizations, it’s that government IT, as traditionally practiced, is fucked. Compared to the private sector, the amount of paperwork, the role of contractors, and the seeming separation between doing a good job and working software drives all sorts of angst and failure. Mark Schwartz’s book on figuring out “business value” in IT is turning out to be pretty amazing and refreshing, especially on the topic of government IT.

I started a new booklet project, the Cloud Native Cookbook. The premise is this: The premise of this book is to collect specific, tactical advice transitioning to a cloud-native organization. The reader is someone who "gets it" when it comes to agile, DevOps, cloud native, and All the Great Things. Their struggle is actually putting it all in place. Any given organization has all of it's own, unique advantages and disadvantages, so any "

My colleague Richard has a nice post suggesting the new functions enterprise architects can play in a cloud-native organization. I like this one in particular, help make the change: Champion new team organization patterns. As an architect, you can bring developers and operations teams together. Recognize that functional silos slow down delivery. A DevOps-type approach really works. Architects are perfectly positioned to pioneer new team structures that increase velocity and customer attentiveness.

In a report giving advice to mainframe folks looking to be more Agile, Gartner’s Dale Vecchio and Bill Swanton give some pretty good advice for anyone looking to change how they do software. Here’s some highlights from the report, entitled “Agile Development and Mainframe Legacy Systems - Something’s Got to Give” Chunking up changes: Application changes must be smaller. Automation across the life cycle is critical to being successful.