Whether you want to transform your business to agile or build a new agile team: In addition to competence and professional qualifications, the mindset and the individual personality are especially decisive, whether agility works in your team or not. Here what you should pay attention to if you want to fill the roles in an agile framework well.
In times of the VUCA world, the motto "change or die" shapes the business world. Who does not join in with the rapid changes in the (IT) world and doesn´t adapt, is left behind. Smart learning is essential to the survival of the entire organization and a crucial key for continuous improvement. It can bring the technical know-how with innovative and interactive methods and stimulates efficient knowledge exchange within the teams.
In conversation with Elisabeth Rosak, Principal Business Value Consultant at Qualysoft Austria. The expert for Big Data Analytics and CRM has been working for well-known players in the past and was able to significantly contribute to the company's success by successfully designing and implementing customer journey strategies in their previous stations.
The fast and flexible development of IT solutions is the foundation of success in an ever-changing digital business world. Rapidly delivering new features and high-quality releases will be critical to your success. But what else do you need to know about Test Automation?
Often functional test automation (UI test automation, REST test automation) gets created in the next sprint after the feature has been completed and sometimes even released to production. The reason for this is that the many think a feature needs to be fully implemented before test automation is created. Another reason is that there is not enough time in the current sprint and creating automation is therefore pushed to the next one.
The last step is to setup a build and deployment pipeline which automatically builds the docker image and deploys it into the ECS cluster.
Now that we have configured AWS, we can start with the implementation of the application.
In this tutorial series we are going to deploy a microservice to the Amazon Web Services Cloud with one click. In order to do so, we are going to set up our AWS Account and configure CodeCommit, S3, SNS/SQS and ECR to fit our requirements. Then we are going to use the microservice provided by Spring's Spring Boot Docker example and modify Amazon's Reference Architecture for CloudFormation to deploy our service. To connect Jenkins to AWS we are going to use different plugins that act as interfaces. Finally, we are going to write a Declarative Pipeline that checks out our code from CodeCommit, builds it, tests it and deploys it to CloudFormation using the modified reference architecture.
How chatbots are used in recruiting and what trends are emerging through the advent of artificial intelligence is highlighted in our recent blog article.
After discussing the Antipatterns in the previous blog post, lets focus on getting things right in this one. There are many best practices and patterns when it comes to CI/CD - I tried to choose patterns that are either very important or often done wrong. The latter is the case for our first topic.
I'd like to start this blog with a post about CI/CD Patterns and Antipatterns. I guess all of them are in general well known but many of the Antipatterns still persist. Also, if you are looking for a quick fix, you should really check the list. If you are a newbie regarding CI/CD, then the list should at least help you to understand the fundamental concepts behind CI/CD, which will be explained in detail in future posts.