Showing posts with label #DevOps. Show all posts
Showing posts with label #DevOps. Show all posts

Thursday, 25 October 2018

DevOps and AI means that Lean Data has another Principle

In an earlier post I expounded on the principles of Lean Data:

  • Organisations know what data they hold and manage;
  • Data is classified according to subject area and criticality;
  • Only the minimum data necessary to Add Value to the business is held;
  • Data replication is kept to the minimum level necessary to optimise business performance;
  • Data Value is determined by its utility in Serving the Customer, Supporting Essential Capability, Protecting the Organisation, Providing Insight for Business Decision Making.
I also covered Data Portfolio Management. However, what I missed was the emerging issues around database management systems and Machine Learning. It appears that as people start to scale their Lean efforts (Strategic Alignment, Design Thinking, Agile & DevOps) they are beginning to realise that this includes data too.

What becomes increasingly important is having a handle on configuration management over data base design (i.e. schemas) and data sets themselves, ensuring that it is co-ordinated with code configuration management and integration across multiple deployments. This should have been implicit, but apparently it was not.

Therefore I suggest adding the principle that:

  • Data configuration management of schemas, test data conditions and machine learning training data is co-ordinated with applications and code configuration management.

Friday, 14 September 2018

DevOps 2018 Report

Puppet has published its 2018 State of DevOps Report. This year they have examined the premises on adoption and confirmed that most successful adoptions follow a project by project approach, with a single project pioneering the way and gradual cross poliantion of practice whilst it is matured.

The project focuses on 2 aspects of adoption:


  • CAMS - Culture - Automation - Mearsurement & Sharing


  • a 6 layer maturity model from 0 to 5, which broadly follows a simplify and Standardise Approach, Followed by Process Practices, then Automation and finally Self Service capabilities.

One of the themes of the report is the gap between teams practicing DevOps and Senior Management. It still appears that DevOps adopters continue to struggle with cultural aspects associated with empowerment and reporting.

Anyway, for anyone interested in the Lean Aspects of Digital Business Models, this is essential reading.

Thursday, 28 December 2017

Agile Is Not New, But It is Useful

Agile advocates are often quite quite siloed in their thinking, many having had little other experience of delivering projects than bespoke software development projects. Many of them are not even aware of the historical trends before the publication of the Agile Manifesto or that they are in fact just participating in an evolutionary trend, rather than a revolutionary approach. Agile owes much to Rapid Application Development or RAD (its immediate predecessor). Often, I have heard them musing about applying Agile to other technologies and industries and wandering whether it is possible. At the same time they miss the fact that DevOps, which extends Agile, is based on manufacturing theory (Total Quality Management, Just-In-Time and Flexible Automation).

Actually, project managers who subscribe to the AgilePM approach, will often use the organisational aspects of agile to run their projects and the approaches used in RAD were not new either. Prototyping was a feature enabled in manufacturing by the use of CADCAM to rapidly design and produce prototypes and Engineers have always been taught that Design is an iterative process. The concepts of Design Thinking originate from academic papers produced in the 1960s, and address many of the technique aspects of Agile including multi functional product teams and evolutionary prototyping and development of innovative products.

But if you want to see Agile organisational constructs such as sprints in action, go to a shipyard. almost all modern shipyards practice modular shipbuilding approaches. They split the overall design into modeles which are constructed and outfitted. These are combined to form blocks, which are then further outfitted. The blocks are then moved to the construction berth, combined and integrated. Work is usually organised around 1 to 2 week production units (although sometimes 4 week ones are used). Testing is continuous and progressive as systems and compartments are completed. Test conditions are part of design. (Does this sound Familiar?). 

Although this practice evolved in the late 60s in Japan and gradually spread, it was in fact learnt from high rise building construction, with each floor of office or hotel blocks treated as a sprint.

Likewise, filming has a similar approach. Up front sketches are used to design each scene. Some work is done with cameras, lighting and film to workout the best combinations to achieve the cinematic affects required (a little similar to preliminary UI design). Scenes become the sprints and are filmed iterativelly to produce what can be afforded and so on. UAT is done with test audiences.

So Agile is not new, it's just slightly tailored to software development, and just like some of the other approaches used elsewhere, it's based on producing a right quality product with the minimum of fuss.

Tuesday, 12 December 2017

The Way of DAU - The best a business can be

Just to let you know, The Way of DAU is now available from Amazon as a paperback. (click on Amazon to see) and the e-version should be available soon. 

This is a deliberately simple book on the quite complex subject of how to adopt a sustainable digital business model. It was inspired by my personal frustration with incomplete models and advice available for Digital Business.

Digital operations have now replaced traditional Business As Usual business models. The Way of DAU promotes 10 basic principles, an iterative Framework (the DAF or Digital Adoption Framework), and positive cultural values to achieve the behaviours needed in successful digital businesses.



The book is based on a mixture of personal experience (in an organisation struggling to reinvent itself) as well as collected best practices. The current edition represents an MVP version. I hope to collect constructive feedback via a LinkedIn Group to drive future releases of the book. (see: The Way of DAU Group ).




Monday, 17 July 2017

Digital Adoption Framework

A lot get's talked about Digital, but there are few comprehensive approaches to adoption available for reference. 

This is why I was interested when I came across Vadrim's DAF diagram, reproduced below. Enjoy!