The new promise in the IT world nowadays is Artificial Intelligence (AI). It all sounds very futuristic and maybe a little spooky, but is this really the case? AI, it has been around since I remember computers. When using AI in processes, this seems like using more specialised systems and complex integrations.

Nowadays AI is integrated into Pega, which makes it very easy to apply in the Business Process area, where I have the privilege to work in every day. Let’s see if AI is that new or just spooky.

Read more: Artificial Intelligence: new or spooky?

In my last two blogs I have explained how important automating tedious office tasks can be to improve employee satisfaction.

Many big companies already use workflow management tools or business process management suites such as PegaSystems, OpenText, Appian, Oracle BPM Suite, etc. Most of these tools are very powerful but for many small companies they are a bit overwhelming. These big platforms offer many features such as scalability, high volumes, advanced integration, customizing portals & user interface, case management, development environments, multiple build teams, etc.

Read more: The search for small and affordable workflow automation & business process management tools

When you think of a software development tool you probably think of a platform or environment to develop software to support business functionality and/or end users/customers. In most cases you would be correct. But you can use the software development platform for more than just developing software. The developed software also needs to be tested to check whether the implemented functionality matches the intended functionality or not. Usually you would use a software tool, which sole purpose is to test the developed software or manually test the developed software. But you can also use the development tool as a test tool to support/implement (part of) your tests.

Read more: The development tool as a test tool

Delivering software quickly is important to deliver functionality to end users but this can be conflicting with the quality of the software. A solution can be built in a ‘dirty way’ and be beneficial on the short term but not in the long run. In practice, I see that organizations balance more towards delivery than quality. This blog will explain in 3 reasons why software quality is behind on software delivery.

Read more: Why software quality is behind on software delivery

Taste is not debatable, which also applies to the taste in cars. But we won’t talk about cars today, we are going to talk about developing software applications. Recently, I started a new project and have to face new designs. Here I hope to see true beauty, and sometimes it works and sometimes it doesn’t. But what exactly is this beauty? Is that the simplicity of the Duck or the force of the Ferrari? And what characteristics are crucial? In this blog we discuss some considerations on the basis of three criteria. 

Read more: Ugly Duck (Citroën 2CV) or Ferrari: 3 criteria

Page 2 of 5