Posted on

Enterprise Readiness For The Digital Age: Digital Fluency And Digital Resiliency

Businesses no longer view digital transformation solely as a source of innovation. It has become a requirement for business continuity, enabling teams to work anywhere and organizations to rapidly adjust in the face of a COVID-19 crisis. 

While remote working is here to stay, the future is a hybrid working model. This new system of working is a game-changer, and the faster businesses acclimatize, the quicker their productivity will rise. As enterprises move from the Respond stage to the Renew stage, their primary focus should be on building digital resilience through digital fluency. In the long run, companies can mitigate risks, swiftly adapt to change, and come out of future crises stronger. 

Posted on

A Rapid Overview of ISA-88 and How It Aligns With ISA-95 and IIoT Platforms

ISA-88 is a long-standing standard for managing batch processes, while ISA-95 is focused on defining the progressive complexity of information that is expected to be available at each layer.

Often, interconnect between the two standard definitions and further the evolving IIOT platform definitions cause some degree of confusion as manufacturing firms grapple with defining and shaping their IT strategies and new tech/platform/apps adoption frameworks.

Posted on

10 Common Scrum Mistakes and How to Avoid Them

When most people think of Agile, they think of “Scrum”.  Scrum is the most widely used, and arguably, the most abused Agile framework.  Scrum is simple in concept but can be difficult to do really well.  Here are 10 common Scrum mistakes and how to avoid them:

1. Expecting Transformation to Agile and Scrum to Be Easy

All too often, someone will pick up a book on Agile or Scrum, start chopping up requirements into user stories, begin daily stand-up meetings, develop software in 2-3 week sprints, and then call themselves Agile.  Easy, right?  They will likely see some improvement in their ability to respond to change, and may even provide working software faster – for a while.  It won’t be too long, though, until the promises of Agile become less evident, teams struggle to keep up the pace, software doesn’t always match user expectations, and then Agile is deemed a failure.  Agile transformation takes time and almost always starts out messy.  Real transformation exposes existing corporate and culture problems that must be dealt with – problems such as poor communication, lack of accountability, distrust, etc.  Effective Agile transformation is often a total culture change.  Give it time, and be ready to go through the pain and resistance to cultural changes.