DXCTechTalk

as a starter, have you seen the latest point of view paper? https://www.dxc.tech...

Start with identification of user needs, map out the value chain, understand your role in it, ref Wardley Maps.

No, so, sounds like something I need to pursue

The Apps paper is here: http://www.dxc.techn...

@GlenPRobinson Makes sense otherwise all you are doing is modernizing something that you may not really need, tail wagging the dog then

@GlenPRobinson Especially when you look at Lambda and Azure Event Grid, its about response decoupled from underlying tech

for me it starts with understanding and experimentation - the value is in unlocking the information - pick a story that enables information composition to improve the business?

@GlenPRobinson All the while being careful not to 'pave the cow path'.

I keep coming back to information flows - which then become logically expressed in #Lambda and #AzureEventGrid... if you don't know what information you'd need to best complete - then we have a business understanding challenge.

@DanHushon I don't see this as being about knowing or not. It's about discovering. The world changes everyday and with it our information needs change too.

we have quick starts and assessments to help. It starts with current client mapping and business goals and of course the ability to drive change across the key priorities

I believe we have to also focus on the customer and employee journey as part of the overall digital transformation quite often that will lead us to changes across existing application portfolio

...I think helping clients understand that this isn't "more of the same", and how Agile and microservices can de-monolith their apps and improve interoperability between old and new apps...visual roadmaps and rapid prototypes seems to help.

Michael - isn't that the point... if there is an API, there's a way. the understanding of information relationships, structures, and analytics will need to be core skills for developers in modern world.

Developers must be composers not just sheet readers e.g. automatic pianos

@DanHushon partially true. Every API comes with a set of preconceived structures and omissions. An analog is the idea that first we shape our cities then our cities shape us. An PAI is a narrow channel, good for some uses especially known uses.

@DanHushon Not so good for unknowns, or unknown unknowns.

as @psd said "Agile: make it up as you go along. Waterfall: make it up before you start, live with the consequences." https://twitter.com/... - that has important consequences for managing risk

I also wrote something on this a couple of weeks ago 'Marginal cost of Making Mistakes' http://blog.thestate...

@cpswan I can accept that as a good 140 char fitting description

@cpswan Fits well with why I say procurement needs to get on the digital transformation bandwagon - https://blogs.dxc.te...

bridge the gap between planning and action. Make learning part of your action, aka development. that is agile

one of the most important lessons (normally takes a couple of years) to learn is that Agile techniques have a context. They are not appropriate everywhere.

Waterfall - all you planning is upfront, as you move through the process flexibility diminishes. In Agile you start we less up front planning, and iterate your way through development, making adjustments and delivering working software.

I think that Agile is cultural - in that the culture must accept #GoodEnough and #LearnFromFailure... then what @cpswan said

@swardley - and Agile and Waterfall are not the only methods around. Concurrent engineering or incremental development may be more appropriate to a given context.

Agree, it is a cultural shift away from get it right the first time, to minimum viable product that is enhanced through fast iterations

@NewInstEcon : oh agreed. Long ago I did some work on marginal cost of change, last post on this was circa 2013 - http://blog.gardevia... .. and yes, many methods are needed.

@swardley Indeed - having rich choice of alternative methods gives more options to optimise cost benefit outcome.

We have been sharing books with clients including the DevOps handbook, The Phoenix Project, and The Innovators dilemma and driving the conversation to "fail early, fail often"...also, letting clients listen in on Scrum calls can excite them on their side.

I've been a big supporter of #PaaS since 2005 I think it eliminates many hurdles with rapid delivery

Hey Jim... so we've long said smart software is replacing smart infrastructure, but in this case containers begin to optimize around a standard lifecycle strategy to enable improved agility.

PaaS can play many roles, but will play a key role when integrating with legacy systems. The LEF will soon be publishing some thinking on this.

It removes the need to constantly tweak the runtime platform to support the apps deployed

- very context specific. As a general rule, when industrialised components exist then you should aim to consume unless you really know what you're doing.

fewer decisions on what to use means fewer cycles agonising and more cycles doing

containers provide lifecycle managment for services at far faster instantiation/teardown rates than traditional "image" based models (!IaaS)

@swardley - Strongly agree. In my view that is the core value proposition.

@swardley I would say this is 95% of what's behind falling into the Trough of Disillustionment

they certainly can be. several industries leverage PaaS aligned to core systems like airline reservations where PaaS can extend core to the edge

Use of a PaaS accelerates focus on the business functionality be that Customer Experience or Business Process transformation.

There's practically very use for Public Cloud at this point without PaaS. The enterprise can automate VM provisioning. PaaS has always been the end game.

Dogfood is a powerful way to become customer zero. We do that in DXC. We are also containerizing apps to enterprise grade. includes stateful and transactional systems as well

We're transforming many DXC Insurance portfolio products via this #innersource platform. Participation and use welcome https://github.dxc.c...

We absolutely are! And have been sharing that story, even before being at DXC.

I think @danhushon can give us some great enterprise level examples here too.

lots of great work being done inside DXC great story which we will be leveraging more and more

@ojacques2 We were participating in HPE as part of Digital Revolution. Is there similar platform in DxC?

I'd love to see what you guys think of blockchain impact to things like collaboration and the future of work

We try to get clients to understand that the more they shift toward the direction of serverless/function-aaS capabilities the greater the reduction in operational and maintenance

Ultimately this ends up being a financial versus engineering decision in many cases all we can do at DXC is be relative to both sides of the debate within our customers

I think that modern enterprise platforms like #SAP, #Dynamics provide a more modern API driven / PaaS approach and can expose business information and processes... but we have to modernize from the legacy platforms to unlock

Abstract the legacy apps (as required by each User Story) by exposing the information through interfaces/APIs

I'll add we're building out our capabilities around decomposition of these monolithic apps into microservices and unlocking the value as @danhushon states