Skip to main content

Author: AI Insider

3 big takeaways from Romanian AI Days 2023 that stayed with us

Factory of the future, robot empowerment, and healthcare transformation

3 big takeaways from Romanian AI Days 2023 that stayed with us

6 minute read
by AI Insider team

Last week, on September 20-21, AI Insider attended Romanian AI Days. The 2023 edition was the third year we partnered with Romanian AI Days to support the AI community in Romania, connecting experts, industry practitioners, academics, freelancers, and students who discussed the most recent advancements in the AI field.

Here are three takeaways, from Marius Podea, Founder of AI Insider, who joined the event:

Takeaway 1

Prof. Dr. Alin Albu-Schäffer’s presentation emphasized the integration of adaptive manufacturing in factories and highlighted the role that robots can play in enhancing the lives of people of higher age and people with disabilities, especially in an era of limited human resources, a challenge that will become increasingly pressing in the coming decades.


Takeaway 2

Dr. Ing. Martin J. Schuster discussed the roles of robots in space and deep-sea exploration as well as humanitarian missions, emphasizing the challenges of autonomous operations in environments with extended communication downtimes and the importance of efficient AI systems that conserve robot battery life.


Takeaway 3

Lucian Itu’s presentation showcased the integration of AI into healthcare, particularly in medical image analysis, which assists diagnosis by offering descriptive findings and enables safer testing of various heart treatments using digital heart models to eliminate risks before the application on patients.

“Impressive presentations at AI-focused events such as Romanian AI Days are inspiring as they demonstrate the dynamic evolution of technology. This annual gathering of the AI community consistently unveils insights and innovations that ignite our anticipation for the future.”
Marius Podea

Did you miss out on the action? Here are three big takeaways that AI Insider came away with.

Takeaway 1

Adaptive manufacturing and the factory of the future

Prof. Dr. Alin Albu-Schäffer’s presentation on the future of factories inspired many attendees. His vision of adaptive manufacturing resonated particularly with our team, as we’ve been implementing similar concepts in developing a cutting-edge Manufacturing Execution System (MES). Adaptive manufacturing, placing flexibility at the heart of production, holds the promise for improving efficiency, reducing waste, and enhancing product quality. As AI advances, its role in reshaping manufacturing processes is becoming increasingly essential.

Furthermore, Prof. Dr. Albu-Schäffer’s insights into how robots can enhance the quality of life for people with higher age and people with disabilities in an era of scarce human resources left a lasting impression. The shortage of caregivers is a real challenge that AI-powered robotics can help address. It’s a reality already unfolding and will impact society in the coming decades.

Prof. Dr. Alin Albu-Schäffer presenting Factory of the future at Romanian AI Days 2023

Prof. Dr. Alin Albu-Schäffer presenting Factory of the future at Romanian AI Days 2023

Prof. Dr. Alin Albu-Schäffer - Explainable AI (XAI) for robots interacting with the physical world

Prof. Dr. Alin Albu-Schäffer – Explainable AI (XAI) for robots interacting with the physical world

Prof. Dr. Alin Albu-Schäffer - Mobile personal assistant

Prof. Dr. Alin Albu-Schäffer – Mobile personal assistant
Takeaway 2

Robots as explorers: space, deep water, and humanitarian aid

Dr. Ing. Martin J. Schuster took the stage to discuss the contribution of robots in various frontiers – from space exploration to deep-water missions and humanitarian support. His presentation offered a glimpse into the current state of robotic systems and the unique challenges they face when operating independently in remote and hostile environments.

AI plays a central role in these scenarios, but as Dr. Schuster pointed out, it must be optimized to balance intelligent decision-making and energy efficiency. The need to conserve battery power is critical, especially when communication with the base may be disrupted for extended periods, even 24 hours.

Dr. Ing. Martin J. Schuster presenting Robotic teams for autonomous exploration at Romanian AI Days 2023

Dr. Ing. Martin J. Schuster presenting Robotic teams for autonomous exploration at Romanian AI Days 2023

Dr. Ing. Martin J. Schuster - Autonomous exploration with heterogeneous teams

Dr. Ing. Martin J. Schuster – Autonomous exploration with heterogeneous teams

Dr. Ing. Martin J. Schuster - ROBEX (Robotic Exploration of Extreme Environments)

Dr. Ing. Martin J. Schuster – ROBEX (Robotic Exploration of Extreme Environments)

Dr. Ing. Martin J. Schuster - RAFCON (RMC advanced flow control)

Dr. Ing. Martin J. Schuster – RAFCON (RMC advanced flow control)

Dr. Ing. Martin J. Schuster - Next steps

Dr. Ing. Martin J. Schuster – Next steps
Takeaway 3

AI in healthcare: transforming diagnosis and treatment

Lucian Itu’s presentation highlighted how AI is transforming the healthcare sector, particularly in medical image analysis. With AI’s assistance, medical professionals can facilitate the interpretation of complex images and generate descriptive findings. This saves time and leads to more accurate diagnoses and treatment plans.

A standout moment in the presentation was the discussion of how AI is used to simulate and analyze different heart treatments on digital models of the heart. This innovative approach allows healthcare providers to eliminate potential risks before applying treatments to patients. It’s a powerful example of how AI can enhance patient care and safety.

Lucian Itu presenting AI for healthcare - From patient twinning to precision therapy at Romanian AI Days 2023

Lucian Itu presenting AI for healthcare – From patient twinning to precision therapy at Romanian AI Days 2023

Lucian Itu - Coronary analysis based on coronary CT angiography

Lucian Itu – Coronary analysis based on coronary CT angiography

Lucian Itu - Coronary analysis based on coronary CT angiography - Comprehensive assessment

Lucian Itu – Coronary analysis based on coronary CT angiography – Comprehensive assessment

Lucian Itu - AI-powered comprehensive analysis of cardiac MRI studies

Lucian Itu – AI-powered comprehensive analysis of cardiac MRI studies

Lucian Itu - Prognostic value of incidental cardiovascular findings in routine chest CT

Lucian Itu – Prognostic value of incidental cardiovascular findings in routine chest CT

A bonus takeaway

The event also featured startups pitches, each with AI at the core of their innovative ideas. These pitches provided a glimpse into the diverse and promising applications of AI that the future holds.


Looking ahead

As we reflect on the insights and innovations presented at Romanian AI Days, it’s clear that AI’s impact on our world is profound and continually evolving. With each passing year, we witness the strides made in AI technology, all of which hold the potential to enhance our lives, transform industries, and address some of the most pressing challenges in society. We eagerly anticipate what the future holds as the AI community continues to push the boundaries of what’s possible – and leading the digital future.

  • Are you implementing or seeing some of these AI trends?
  • Did you attend Romanian AI Days?
  • Are we missing any highlights?

Tell us more about your experience with Artificial Intelligence.


We hope this article has helped you get insights into some of the most recent advancements in the AI field. If you’re looking to dive deeper into the matter, look no further. You’re welcome to join the conversation.

Continue reading

Senior SAP ABAP Developer

Senior SAP ABAP Developer

Romania / Remote
Full-time, flexible
Senior level

Apply now

Make an impact with us

At AI Insider, you will be part of an exciting and international work environment and contribute with your senior experience to our impact as a team in enabling clients to achieve their objectives. In one of our projects, we are developing a new generation MES (Manufacturing Execution System) and we’re looking to expand our team with a new colleague experienced in SAP ABAP Development.

Why this role is important for our work

  • International team, people with various backgrounds and levels of expertise, direct interaction and communication with the end client
  • The project is part of our client’s digital transformation initiative and supports them in leading their digital future

When here, your responsibilities will include

  • ABAP Development in S4 HANA
  • Creating technical concepts for new functionality
  • Peer testing, ensuring a quality gate for the other colleagues
  • Assessing R3 business logic and moving it into S4

What is takes

  • Good understanding with PP/MM module and data structures
  • Good knowledge in developing OData services
  • Good knowledge of SAP Gateway OData error troubleshooting
  • Knowledge with BAPI, RFC, IDOC
  • Fluent in English; German a plus

What we offer

AI Insider’s culture is value-driven, entrepreneurial, professional, and partnership-oriented. We’re motivated and engaged, and we love the work we do and the impact we have.

AI Insider is a place where you can solve diverse and complex tech challenges for and with our clients and together with people who believe in purpose, show empathy, pursue growth, and put trust at the base of everything we do.

We provide and support a senior and international work environment based on direct interaction with our clients.

Sure we work hard, but we also allow ourselves to pause and keep balance in our lives.

We value flexibility. We trust that flexibility through autonomy enables you to learn and develop continuously, experience wellbeing, enjoy a respectful way of working, explore and do the best work you can do to ensure that both team and clients achieve their objectives.

With this in mind, you can choose the benefits that bring the most value to you.

Freelancers, contractors, and full-time employees

Freelancers, contractors, and full-time employees are all part of our team. Our collaboration models are flexible.

About us

Full IT service provider by nature. Partner by approach. AI Insider is a full IT service provider that started in Cluj-Napoca in 2019. Through every partnership and project, we make businesses’ transition to their digital future real, more approachable, and sustainable. We do this with an AI-first philosophy, the best technology at hand, and empathy.

We believe that most companies think about their digital future or are already in transition to it – and that together we can partner with them and help them. From end-to-end application services to automation and Artificial Intelligence, your work will ease the tech challenges of the companies in transition to the AI age, so their leaders focus on key aspects of their business.

With us, your work will smooth the path for our clients to move forward and lead their digital future.


Application guideline

Please choose the most convenient option for you to apply:
Send us your CV/résumé at careers@aiinsider.de

Or use the form below

Continue reading

Telemetry: a big opportunity to approach scaling in the cloud – Part 2

What’s under the hood?

Telemetry: a big opportunity to approach scaling in the cloud – Part 2

10 minute read

Image by Emma Gossett – Unsplash

by AI Insider team

What’s under the hood? How to instrument your deployed application using Azure Application Insights? What assets does OpenTelemetry bring? How to extract the component for scaling using telemetry?


You’re back. Great! This article is part two of a two-part series on using telemetry to approach scaling in the cloud. So if you forgot about Part 1 or didn’t have the chance to read it, we invite you to do a quick recap and read our first article in the series, Telemetry: a big opportunity to approach scaling in the cloud – Part 1.

Azure Application Insights (AI)

If your application is hosted in Azure, we have good news. You can instrument your already deployed application with no code modifications at all using Application Insights.

Fig. 7. Default page in Azure Application Insights

Fig. 7. Default page in Azure Application Insights
It attaches its own profiler to the required services, and then spots the calls to known APIs like database/HTTP/gRPC querying or, for example, HTTP handling. The profiling itself is as fast as the local one. If another service is involved in the request, the call to that service is automatically enriched with the context information. Then, the called spans are attached to the calling one.

Fig. 8. Span with many attached child spans

Fig. 8. Span with many attached child spans
It also aggregates data and can display various charts:

Fig. 9. One of the dashboards of the Application Insights service in Azure

Fig. 9. One of the dashboards of the Application Insights service in Azure
In Fig. 9., the slow request is under arrow 1. Under arrow 1, arrow 2 shows a peak on the Dependency Call Duration chart. Knowing that the dependency is a database, we can say the problem is in slow response from that database. Of course, we can click things and dig deeper to find the exact query that is slow.

Fig. 10. AI can show separate spans relation between them and details

Fig. 10. AI can show separate spans relation between them and details
With AI, we can define alerts to warn developers when something goes wrong (memory consumption is too high or an exception happened, etc.). Azure even has a feature called Auto Detection that, once activated, starts learning regular metrics of your application. Once learned, it can raise an alert in case it detects an abnormal behavior.
AI properly understands any already scaled services as different instances of the same service. The component map is very useful in general.

Fig. 11. Application Map in Azure Application Insights

Fig. 11. Application Map in Azure Application Insights
AI has many more interesting features, e.g., tracing failures/exceptions, Geo-distribution of the users, and custom charts. Data can be queried with a special T-SQL-like language.
Applications outside of Azure can send traces with just a little of coding and are available for all the major frameworks: Java, .NET, NodeJS, etc.

One more popular tool to compare is Datadog.

OpenTelemetry

While the number of tracing tools continues growing, the request to standardize the data format and API of the tracing is coming. OpenTelemetry is being developed for that reason as it is a set of open standards, SDKs, and tools. Check the huge volume of supported products in the registry.

OpenTelemetry components can be containerized and reside in the Kubernetes cluster for testing and debugging purposes. For example, injection of Zipkin (a collection and visualization tool) is only two lines at the configuration file:

Fig 14. Zipkin data visualization

Fig. 12. Zipkin added to Docker-compose configuration
The general concept of OpenTelemetry components is very similar to what we have in other SDKs, but at the moment of writing this article, automatic instrumentation for .NET was in alpha version. However, manual instrumentation here is very simple:

Fig. 13. Application manual instrumentation with OpenTelemetry

Fig. 13. Application manual instrumentation with OpenTelemetry
We are providing the address of the data collector, common properties (service name and the version), and APIs that we want to observe: HttpClient, ASP.NET Core request processing, and SQL querying. An idea is to set up the console as the telemetry output (this way, we can satisfy the 9th factor of 12 factors concept).

Data can be exported to a tool of our choice. Here is how Zipkin looks like:

Fig 14. Zipkin data visualization

Fig 14. Zipkin data visualization

OpenTelemetry also recommends another visualization tool called Jagger. Please access more information on modularity here.

Fig. 15. Components concept of OpenTelemetry

Fig. 13. Application manual instrumentation with OpenTelemetry
As now we know what slows down our users, what is next?

Extracting the component for scaling

Next, we take the code of that slow process and move it into a separate newly created service. It is necessary to add some code for serialization, validation, and application domain maintenance. The request processing may be possibly slowed down, but we can now scale it! To control that, we want to introduce the Load Balancer, which will start adding instances to the requests number growth at a time.

Having that, we allow more users to make more requests to be served within the same period. The only output metric that grows with the number of users is the hosting cost.

Imagine the scenario of a video conversion service: users upload videos, the server converts videos to another format (that is already measured by us and happens to be slow), and, finally, users download the converted video back. Here we extract the conversion code into a separate service. Once a video has been uploaded, our Load Balancer spins up a new instance of conversion service, which handles the video without disturbing other instances of the conversion service. It does not matter how many videos have been uploaded; each will be available for downloading at a nearly constant time. Furthermore, having 0 users at a given moment means we also develop 0 running instances that, in the end, generate zero cost.
Besides the scaling, we are automatically optimizing the recovery after the conversion’s critical failure: we don’t have to restart the entire application anymore. Instead, we restart the conversion service only. Furthermore, we can plan to increase or shrink the pool of instances depending on the predictions we make. This way, the recovery is either immediate or invisible for the end-user. As an exercise, try to plan the separation of file storage – one user could upload and download files independently from another.

Later, once the application can scale, we should also give attention to keep testing the scaling. Azure has a feature called Load Testing for that. If we know our users’ behavior, we can define the appropriate test data to check how that behavior is preserved under the heavy load. This testing can run before pre-release deployment or even for pull request validation.

How do you approach scaling?

Now that we’ve discussed how to use telemetry to approach scaling in the cloud, where is your scaling on the map? Is it where you thought it was?
Tell us more about your experience with scaling and how you approach it, especially if you have a newcomer experience.

We hope this two-part article has helped you get insights into using telemetry in scaling in the cloud. If you’re looking to dive deeper into the matter, look no further. You’re welcome to get in touch with us and take the conversation forward together.

Continue reading

Telemetry: a big opportunity to approach scaling in the cloud – Part 1

What’s under the hood?

Telemetry: a big opportunity to approach scaling in the cloud – Part 1

10 minute read

Image by Emma Gossett – Unsplash

by AI Insider team

What’s under the hood? What flavors of scalability to consider in the cloud? How to find the right process to extract for scaling using telemetry?


This article is part one of a two-part series on using telemetry to approach scaling in the cloud.

Context

The topic of scalability has been evolving very fast in the last 10 years. Understandable if one could get lost in tons of SDKs, tools, and product announcements. In this two-part article, we invite you to learn more on how to approach scalability and, at the end, we give you the direction on how to move forward. We consider a need in scaling and how to use telemetry to analyze it.

While the topic of microservices is tightly bound to the scalability, our consideration should work for SOA-like systems (Fig. 1) as well as monolith and various combinations.

Fig. 1. SOA - Service Oriented Architecture adapted from Wikipedia

Fig. 1. SOA – Service Oriented Architecture adapted from Wikipedia

For simplicity, we assume that our application is already in the cloud, like in Azure. Some examples are .NET-based, but the idea still applies to other frameworks.

When speaking about scalability, we usually consider two different flavors of it:

  • Vertical scaling is when we increase the capacity of the “hardware” resources (e.g., more CPU time, faster memory bitrate). Plus, as we are discussing the performance, we briefly cover the optimization topic too.

  • Horizontal scaling (which also includes Geo-redundancy) is when the number of instances of a particular service increases.

From the two of them, horizontal scaling is more difficult. The reason? In most cases, we cannot scale the entire application because of the need for some synchronizations and cost savings. Instead, we want to extract some particular process into a separate service and scale it independently. This approach also speeds up the service recovery after a failure, which means less chance of an outage for our users. But how do we find the process that is working too slowly?

Finding the right process to extract for scaling

We usually come into question of scaling due to poor performance of particular processes in the system. This may happen with the increase of the complexity of those processes or the increase of the number of users requesting them at a time. Both result in more requests coming into critical-like sections (which is, roughly, a blocking resource with possible access by only one tenant at a time). In this case, the requests are put into the wait queue more often, thus adding overall average response time – in other words a bottleneck.

Fig. 2. Only the first request can access a Blocking Resource. Other requests are in the wait queue, while Following Processes have the capacity to serve more requests.

Fig. 2. Only the first request can access a Blocking Resource. Other requests are in the wait queue, while Following Processes have the capacity to serve more requests.
There are simple cases, like when such a resource is just a thread which can be addressed with the increase in the number of CPU cores. But there are more complex cases, like blocking access to a database, which requires global architectural changes. For example, instead of having only one database, we could create one for each tenant and make the code access data asynchronously.

Fig. 3. Blocking Resource is scaled and each request can access its own copy

Fig. 3. Blocking Resource is scaled and each request can access its own copy

When tenants are spread geographically, we want to define one or several services for each database (to have them geographically closer to the user – please see Database sharding).

In these cases, the bottlenecks and the queues can come into play with various combinations and are possibly not simple to trace. Let’s see how telemetry can help with that.

The main idea is to measure the process start and end times, eventually calculating the duration. We have dedicated tools for that, and we call the output of such measurements a span (or sometimes a trace).
If we had an HTTP/Web application, spans could be observed even in the browser (developer tools in the menu).

Fig. 4. All major browsers have tracing functionality. Firefox developer tools are shown.

Fig. 4. All major browsers have tracing functionality. Firefox developer tools are shown.

There, we can find the timing that we are not satisfied with, and then for more details we can attach the profiler, which measures all the functions in our application.

Fig. 5. JetBrains dotTrace Profiler (source: JetBrains)

Fig. 5. JetBrains dotTrace Profiler (source: JetBrains Profiler)

Profiler visualizes the slowest spans for us and also spans which they consist of. We can see exactly how much time was spent on each function.

Here, we can also examine the optimizations of the code itself. Something can easily get fixed by resolving programming mistakes. Something can be removed by introducing caching or indexes, or we can try to convert the function to asynchronous code or, oppositely, to synchronous one where necessary.

At this point, it’s also possible to spot the complexity of our algorithms that is too high. Special sampling mode shows us both the time taken and the number of calls.

Fig. 6. Sampling mode in JetBrains dotTrace

Fig. 6. Sampling mode in JetBrains dotTrace
Most of the profilers also have a feature called Timeline and it is ideal to see how threads are waiting for other threads to do a job.

Additionally, not as much spoken, we can also profile the memory consumption. Memory profiling not only gives the understanding of how to increase the speed, but also it is an argument to scale itself. For .NET, please check dotMemory by JetBrains or similar tools.

These profiler features open the bigger picture on performance. However, it can be very different from the production stages of the application. Users may be invoking different processes more or less frequently than tested. Luckily, we have a number of tools to see traces in the production, and some even allow us to observe the system in real time.

What tools? Let’s start with Azure. Actually, let this knowledge sink in for a bit and then come back for Part 2 of this article.


We hope part one of this two-part article has helped you get the first insights into using telemetry in scaling in the cloud. If you’re looking to dive deeper into the matter, look no further. You’re welcome to get in touch with us and take the conversation forward together.

Continue reading

Senior .NET Developer

Senior .NET Developer

Romania / Remote
Full-time, flexible
Senior level

Apply now

Make an impact with us

At AI Insider, you will be part of an exciting and international work environment and contribute with your senior software engineering experience to our impact as a team in enabling clients to achieve their objectives. An open-minded development team, challenging responsibilities and projects, and professional development opportunities in the global Industry 4.0 are waiting for you.

Why this role is important for our work

  • International team, 120+ people with various backgrounds and levels of expertise, direct interaction and communication with the end client
  • Agile Scrum, embracing the SAFe framework as a way of working
  • The project is ongoing and expanding. The focus is on the software solutions that ensure quality and efficiency are embedded in the manufacturing processes and further enable the control and optimization of the manufacturing processes across multiple plants. The project is part of our client’s digital transformation initiative and supports them in leading their digital future.

When here, you will

  • Design, implement, debug, and deliver high-quality microservices on the Microsoft .NET Stack for multiple factories worldwide
  • Work with technologies in a modern development environment, e.g., Docker, Kubernetes, .NET Core, C# 7.0, Couchbase, Angular 7, CI/CD
  • Develop features to enhance the user experience for digital shop floor solutions
  • Participate in designing the system architecture and application solutions with a high degree of complexity in a critical production environment
  • Provide technical direction and mentor associate and mid-level software developers, conduct peer reviews, pair programming, and join hackathons
  • Work in an Agile Scrum team together with other teams on exciting solutions for global MES / Industry 4.0 solutions

What is takes

  • Degree in Computer Science, Software Engineering, or a related field
  • 5+ years of software engineering experience and working knowledge of WPF, .NET Core, C#, and REST API
  • Experience working in an Agile Scrum team in a fast-paced, collaborative environment and the ability to work on multiple projects simultaneously
  • Fluent in English with strong verbal and written communication competencies

What we offer

AI Insider’s culture is value-driven, entrepreneurial, professional, and partnership-oriented. We’re motivated and engaged, and we love the work we do and the impact we have.

AI Insider is a place where you can solve diverse and complex tech challenges for and with our clients and together with people who believe in purpose, show empathy, pursue growth, and put trust at the base of everything we do.

We provide and support a senior and international work environment based on direct interaction with our clients.

Sure we work hard, but we also allow ourselves to pause and keep balance in our lives.

We value flexibility. We trust that flexibility through autonomy enables you to learn and develop continuously, experience wellbeing, enjoy a respectful way of working, explore and do the best work you can do to ensure that both team and clients achieve their objectives.

With this in mind, you can choose the benefits that bring the most value to you.

Freelancers, contractors, and full-time employees

Freelancers, contractors, and full-time employees are all part of our team. Our collaboration models are flexible.

About us

Full IT service provider by nature. Partner by approach. AI Insider is a full IT service provider that started in Cluj-Napoca in 2019. Through every partnership and project, we make businesses’ transition to their digital future real, more approachable, and sustainable. We do this with an AI-first philosophy, the best technology at hand, and empathy.

We believe that most companies think about their digital future or are already in transition to it – and that together we can partner with them and help them. From end-to-end application services to automation and Artificial Intelligence, your work will ease the tech challenges of the companies in transition to the AI age, so their leaders focus on key aspects of their business.

With us, your work will smooth the path for our clients to move forward and lead their digital future.


Application guideline

Please choose the most convenient option for you to apply:
Send us your CV/résumé at careers@aiinsider.de

Or use the form below

Continue reading

The Scrum Master – a key role for project success

Prepare your organization for an agile future

The Scrum Master
– a key role for project success

10 minute read
Image by Lala Azizli – Unsplash
by Karla Merza,
Certified Scrum Master (PSM I)

What is a Scrum Master and how does the Scrum Master support the organization for an agile future and help the team stay on track?


The following article is a post by our colleague, Karla Merza. Karla is a Certified Scrum Master (PSM I), working in the IT field for over seven years. She is a promoter of the continuous learning process, and she is driven by supporting others in their agile journeys.
AI Insider’s note: This article is the last part of the 3-part series on agile project management. You may also want to read our previous articles in the series, How are you enabling agility in your organization? and Azure Boards vs. Jira. How to choose the agile project management tool to suit your practice.

The role of a Scrum Master in a team or organization is often misunderstood. This article’s scope is to raise awareness about what are and what are not the responsibilities of a Scrum Master and why having a Scrum Master might benefit your company. But before diving into all that, let’s understand the context.

Background

Scrum is a framework created by Ken Schwaber and Jeff Sutherland that helps organizations and teams handle complex problems through adaptive solutions, achieve goals, and create value. The theory, the values, roles, events, and artifacts are described at length in “The Scrum Guide”, a good starting point for anyone who wants to be more agile. This guide is not a rule book to be followed step by step, but a set of guidelines that can help companies or teams to use or create processes and techniques that bring value to their situation, regardless of what that value means to them. A video explaining how Scrum works, in a nutshell, is available here.

Some advantages of adopting Scrum are:

  • A working version of the product is available any time
  • Higher revenue (quick opportunity for feedback from customers due to the often releases)
  • Lower costs
  • Effective use of time and money
  • Possible changes can be incorporated easily
  • Better visibility of product direction
  • Large projects are divided into smaller, more manageable iterations
For example, in one of our projects, at AI Insider, the Scrum Team worked on a product on both the software and hardware parts. After each 2-week sprint, we were able to provide the client a working version of the application ready to be tested in the real environment. This way, we received quick feedback that enabled us to incorporate any change fast and easily.

What is a Scrum Master?

The Scrum Master is part of the Scrum Team together with the Product Owner and the Development team. All roles are considered equally important; there are no hierarchies. The Scrum Team is a cross-functional and self-managing team whose focus is to achieve the organizations’ or teams’ goals. The team is responsible for all product-related activities, from stakeholder collaboration, verification, maintenance, operation, experimentation, and research and development, to anything else that might be required to deliver an iteration of value each sprint.
The purpose of the Scrum Master is to mainly foster an environment that enables the use of the Scrum framework as efficiently as possible. The Product Owner creates and maintains the product backlog with everything known to be needed for the product. The Scrum Team delivers an increment of value at the end of each sprint. The Scrum Team and the stakeholders inspect the team dynamics, their ways of working, processes, tools and make changes, if needed, to improve the rest of their collaboration.
The Scrum Master is a coach, a teacher, a mentor, and a facilitator – a servant leader for both the organization and the team. It is accountable for promoting Scrum and helping everyone understand the theory, the values, roles and responsibilities, events and artifacts, and how they all tie together. By creating constant opportunities for inspection and adaptation, the Scrum Master is an enabler of the effective implementation of Scrum. He or she is a change agent who fosters a mindset based on collaboration and a healthy work environment. Also, the Scrum Master has a vital role in providing structure and visibility for processes and ways of working.

How does a Scrum Master support the organization?

The Scrum Master trains and leads the organization in being agile and adopting the Scrum framework. Some examples are, but not limited to:
  • Analyzing the current ways of working
  • Planning and organizing the implementation of Scrum, depending on the particular situation of the organization, including recommending a detailed transition plan to the new way of working
  • Identifying bottlenecks
  • Improving communication
  • Recommending, helping configure and/or train people to use a suitable project management tool (e.g., Azure Boards, Jira)

For instance, in one of our projects, the Scrum Master enabled the adoption and configuration of the Azure Boards according to the specific project structure. Usually, this approach is a proactive way of starting the project by putting the practical knowledge to the use of the project.

How does a Scrum Master assist the Scrum Team?

Although part of the Scrum Team, due to the servant leader quality, the Scrum Master assists the team in several ways. The Scrum Master:
  • Helps the Product Owner understand the need for a clear roadmap, product direction, and product backlog visible to everyone in the team and organization
  • Teaches the Product Owner effective techniques for defining Product Goals and backlog management
  • Coaches the team members in autonomy, collaboration, and multidisciplinarity
  • Facilitates conflict resolution
  • Drives the creation of a Definition of Ready and Definition of Done and holds the team accountable for following them
  • Detects possible risks early on and encourage the removal of impediments
  • Facilitates meetings as needed or requested
  • Makes sure the agreed processes are followed by everyone, and the Scrum events take place, are productive, and kept within the timebox
In all the meetings we facilitate, we keep in mind and follow some of the best practices. We make sure only the relevant people attend the meeting, and we send the meeting agenda beforehand, so the team uses their time as efficiently as possible. We make clear the purpose of the gathering, we ensure every team member has the opportunity to speak up, and that we achieve our scope by the end of our meeting.

What skills does a Scrum Master need?

The Scrum Master must be an active listener, an observer, have patience, good communication skills, leadership skills, organizational skills, be assertive, motivate and influence people, and build psychological safety. The Scrum Master has to be aware of the team dynamics, know when and how to give feedback or intervene, protect the team from outside disruptive behaviors, and encourage a self-managing and trust-based team culture.
Scrum Masters must have soft skills. Although technical skills are not a requirement, they are an advantage. Scrum Masters with technical backgrounds have more credibility, they relate to their colleagues easier, and, most of the time, have a better overview and understanding of the entire project. This way, their suggestions for improvement are more likely to be accepted and implemented by the team.
Of course, technical skills can be learned and soft skills cultivated, but not everyone can be a Scrum Master. To a large extent, being a Scrum Master depends on the maturity of the person and their willingness to embark on a continuous learning journey.

What are the challenges a Scrum Master faces?

Scrum framework has been used in organizations for many years now, but there are still some misconceptions and problems a Scrum Master comes across.
Here are some aspects that hinder the Scrum Master’s work and make the organization’s environment less efficient in delivering results:
  • The organization doesn’t understand what agility is.
  • The team adopts Scrum without knowing or understanding its principles.
  • The team doesn’t have any formal training in Scrum.
  • The team or the organization are resistant to change.
  • The members of the team are constantly changing.
  • The Scrum Master is an assistant for the team (e.g., Azure Boards/Jira administrator, the person who sets up the meetings in everyone’s calendars, takes notes at meetings).
  • The Scrum Master is confused with a Project Manager.
  • The team assumes the Scrum Master has to give them work, tell them how to do their job, or that they are the Scrum Masters’ direct reports.
  • The Scrum Master must plan and set goals for the team (e.g., sprint goal, choose sprint backlog, set deadlines, manage tasks, micro-manage the team).
  • The Scrum Master is responsible for removing all the impediments or solving all the problems the team has.
  • The Scrum Master is the middleman through which the team communicates with other departments or teams.
  • The Scrum Master must have another role in the team (e.g., developer or product owner).
  • The team or the organization had a Scrum Master as a project manager with the command-and-control type of leadership.
  • The Scrum Master is changed often.
  • The Scrum Master must deliver fast results, regardless of factors such as how long the team members have worked together, their understanding and/or experience with Scrum.
Looking from this angle, the successful implementation of any agile methodology, especially the Scrum framework, takes time and requires a dedicated Scrum Master that has an overview of the situations, especially the problematic ones, without being emotionally involved. It is a continuous improvement process, and taking shortcuts for fast results is not recommended.

Challenges I encountered working as a
Scrum Master and how I addressed them

  • Speaking up

    When the team adopts Scrum without knowing or understanding its principles

    The team members were talking over each other in our meetings. The solution that proved effective was a plush toy. The colleague who held the plush toy could speak up in the meeting while others waited for their turn. It was a way to align the team to the Scrum values and principles. This solution saved the team time, reduced frustration, and created a more productive work environment.
  • Keeping teams focused

    When the team or the organization had a Scrum Master as a project manager with the command-and-control type of leadership

    Some time ago, I took over two geo-distributed teams as a Scrum Master. Before I joined, the team members used to be called in never-ending meetings for reporting purposes several times a day. This approach disrupted the development time and frustrated the team members. Once I took over, I redesigned the mandatory Scrum meetings, sending the purpose and the agenda beforehand and ensuring the scope was held. Consequently, the teams felt their time was well-invested, so, overall, their focus, engagement and productivity increased.
  • Understanding the roles

    When the organization doesn’t understand what agility is or the team adopts Scrum without knowing or understanding its principles

    In several Scrum Teams, the Product Owners didn’t fully understand their roles. Due to a few discussions and workshops we had together, plus the resources suggested for them to understand a Product Owner’s responsibilities, they successfully created and shared a product roadmap with the Scrum team and the organization. Based on that, the product backlog started to be written according to the needs of the development team. This way, less time was spent in the refinement sessions, fewer bugs were found in the implementation, and the customer satisfaction increased.

Stand out

The role, responsibilities, and skills of a Scrum Master are diverse. There is one consideration that rises above these when thinking about having a Scrum Master in your organization. On top of training and leading the organization in being agile, adopting the Scrum framework, and delivering value to your customers regularly, the team members can focus on what they do best. And when the team does that, they can achieve high performance and project success towards consistently meeting the requirements of the business.
Do you have a Scrum Master role in your organization? If you do, what changes did the Scrum Master bring to your team or organization until now? If you don’t have a specialized Scrum Master in your organization or team, what problems do you think the Scrum Master can solve? And if you are a Scrum Master, how did your journey start? What did you learn from your experience, and what are the next steps for you?

If you’re keen to learn more about preparing your organization for an agile future, AI Insider can help you fully assess your current status and set up the way of working that best suits your particular needs. In every agile software development project, we act as a full IT service partner covering the delivery management, so you can focus on your business priorities. Get in touch with us, and we take the conversation forward together.

Continue reading

How to choose the agile project management tool to suit your practice

Azure Boards vs. Jira

How to choose the agile project management tool to suit your practice

10 minute read
Image by Leon Oalh2MojUuk – Unsplash
by Karla Merza,
Certified Scrum Master (PSM I)

Is there an agile project management tool more suitable than another? How to get the most value from such a tool? What are the assets and the constraints to consider? Here is an analysis of Azure Boards and Jira.


The following article is a post by our colleague, Karla Merza. Karla is a Certified Scrum Master (PSM I), working in the IT field for over seven years. She is a promoter of the continuous learning process, and she is driven by supporting others in their agile journeys.
AI Insider’s note: This article is part 2 of a 3-part series on agile project management. You may also want to read our first article in the series, How are you enabling agility in your organization?

Do you know why your organization or team needs an agile project management tool and what you need to consider to ensure you get the value you expect for your money from it?
I will be explaining what a project management tool is, some questions to raise in your journey to find the best that fits your needs, a head-to-head comparison of the two most popular choices used in the teams I worked with, and when I recommend you select each of them, so read on.

What is a project management tool?

A project management tool is a software that helps teams plan, organize, manage, and optimize resources across a project or organization. Adopting such a tool is important from three angles. First, it increases visibility and provides a clear overview of the work that has been done or needs to be completed. Second, it keeps the team organized and accountable in doing their work and following the agreed processes. Third, it minimizes miscommunication problems and the occurrences of bottlenecks.

What are your needs?

In case you were tasked with proposing a new project management tool, or you took the initiative yourself after seeing your current one doesn’t address the needs of the organization, you embarked on a challenging quest.
Although all tools have similar features, this is a decision that is not to be made every day, so it is crucial to ask yourself a few questions before investing in one:
  • Are you part of a new organization looking to work in a more structured way, or do you need a solution to solve problems you identified in the current way of working of your well-established organization?
  • What are the problems you are trying to solve?
  • How would this tool help?
  • Are there any features this tool must have?
  • Do you plan to integrate the current tools you’re using with this project management tool?
  • Do you need to share information/reports with other departments or stakeholders?
  • Is there a methodology the organization is already working with, and is this tool suitable for it?

Who will use it?

Regardless of the organization or type of project you plan to use the project management tool for, it’s essential to know how many people or teams will use it every day.
Some of the things to consider are:
  • What are the departments that will use the tool?
  • Are the teams technical?
  • Are they working on multiple projects at the same time?
  • What did team members use in the past, and what did they like about those tools? Does this tool meet their needs?
  • Would they benefit from integration with other tools, such as Git?
  • What are the current trends and recommendations on industry websites? What are other companies with similar profiles using?
Implementing a project management tool for the first time or switching to another one it’s a long-term commitment and investment. Analyzing and setting up processes need the leadership team’s support and a plan on how the transition will be made. It is not mandatory, but it is highly recommended to have a person who has experience with the tool you’re choosing and knows how to set it up quickly and easily. Then, think about who will train the team(s) in using it. Depending on how open your organization is to change, this process may take time. It is also advisable to constantly ask for feedback from users and adapt if needed.

Azure Boards vs. Jira

There are a few options available on the market for project management tools, such as Hive, Trello, Asana, ProjectManager.com, ClickUp, Taiga.io, Jira, and Azure Boards. Choosing one that fits your needs and your budget can feel overwhelming.
Let’s look at two of the most popular choices for agile delivery management, Azure Boards and Jira. Below there is a direct comparison of the most relevant topics. Any other information you are interested in and are not covered by this article can be found on Azure Boards and Jira official websites.
Azure BoardsJira
Developed byMicrosoftAtlassian
PlatformsCloud, SaaS
On premises: part of Azure DevOps Server
Cloud, SaaS
Data Center (on premises): new license can't be bought anymore; support will end on the 2nd of February 2024.
AccessibilityWeb-based Integrated with TeamsWeb-based Desktop application Mobile application
Integrated with Teams, Slack, and many other tools
Plans and pricingCloud:
- Basic plan: First 5 users free, then $6/user/month
- Basic plan + Test plans:
$52/user/month
Server:
- A 3-year commitment is needed; clients can also move to the cloud whenever they choose to for free.
- A 3-year commitment is not mandatory if the payment is made
through Azure platform monthly, Visual Studio ($45/user/month for Professional or
$250/user/month for Enterprise) and one of the plans for the Cloud are purchased.
Details about the plans and pricing: here.
Cloud:
- Free for up to 10 users
- Standard plan: $7/user/month
- Premium plan: $14/user/month
- Enterprise plan: personalized offer based on discussion with their sales team.
Details about the plans and pricing: here.
SupportBasic support included for all Azure customers: 24/7 self- help resources, ability to submit as many support tickets as needed, Azure Advisor (a personalized guide for best practices), and Azure health status and notifications.
Support plan can be upgraded for an additional fee per month.
Support via email, help desk, forums, FAQs, knowledge base, phone, 24/7 live rep and chat.
TrainingIncluded for the Professional direct support plan, which costs $1.000 per month.Free tutorials and courses; paid courses, on demand for individuals or teams (virtual or onsite).
Prices range depending on the option chosen from $100 to $10.000.
Project templatesBy default, the organization contains 4 types of project templates, called processes: Basic, Agile, SCRUM and CMMI (Capability Maturity Model Integration).
Details: here.
Custom processes can be created by the admin of the organization.
For Software Development, there are 3 types of custom templates: Kanban, SCRUM, and Bug tracking.
Other project templates are available for Service Management, Project Management, Marketing,
Human Resources, Personal, Operations, Legal or Sales departments.
Details: here.
Custom templates can be created by the admin of the organization.
Item types supportedConfigurable for each project. The layout is also configurable: epic, feature, impediment, bug, product backlog item, task, test case, test
plan and test suite.
Configurable for each project. The layout is also configurable: epic, story, bug, idea, task, subtask.
RoadmapNot available.Jira has a roadmap feature integrated that shows a breakdown of all the epics and their user stories and the dependencies between them. It lets you see progress in a timeline view (weeks, months, or quarterly) and export it in a PDF version. An advanced roadmap feature is available for Premium and Enterprise plans, which allow planning and tracking work across multiple teams and projects based on capacity, manage dependencies and competing priorities and explore alternative scenarios.
SprintsStarted by default.Have to be started by the user. The configuration allows multiple sprints to run in parallel.
CapacityCapacity can be set for each team member in a sprint for any plan.Available only for plans that support the advanced roadmap feature (Premium and Enterprise plans).
WorkflowEditable in both text and diagram mode.Editable in both text and diagram mode.
AutomationProcesses can be automated with Microsoft Flow.Directly from Jira. Processes can be automated (e.g., when a pull request is merged, the ticket can be automatically assigned to a QA).
DocumentationIntegrated Wiki. Text can be customized as needed.Additional product must be installed: Confluence. It comes with its own plan and pricing model.
Source controlOnly Git and TFVC are supported.Plugin must be installed for the tool used (e.g., BitBucket/Git/GitHub).
ReportingReports can be generated on the Dashboard, in customizable widgets.Separate section for reports included in each plan.
Status updatesStatus updates and progress tracking is in real time and visible to the entire team.Status updates and progress tracking is in real time and visible to the entire team.
FeedbackCommunication can be done on each particular task, visible to each team member, including giving feedback, sharing a status update or asking questions.Communication can be done on each particular task, visible to each team member, including giving feedback, sharing a status update or asking questions.
SecurityDifferent users with different permission levels can be configured by an admin user.Different users with different permission levels can be configured by an admin user.

So, what and how to choose?

Azure Boards

Ai Insider Agile Project Management Tools: Azure Boards screenshot

Azure Boards by Microsoft
It might be more suitable to go for Azure Boards if or when you:
  • Have in your team non-technical people who will use it. The ramp-up period for these people might take less time than you wish to spend on this with other tools.
  • Prefer to have all the information on your server. This comes with the benefits of having full control, easy and quick access to the infrastructure, including its resources and security settings, and customization at your own pace and finances. Of course, the initial investment or the operating costs may be high and in-house maintenance is required. Azure also allows you to move to the cloud whenever you wish, without additional costs.
  • Already use other Microsoft services on a daily basis, including Office 365.
  • Want an integrated out of the box Continuous Integration system.
  • Would like to have a way to better manage the sprint allocations per team member and to identify bottlenecks easier without paying extra for another plan (the capacity per sprint feature is included in the basic plan).
Jira

Ai Insider Agile Project Management Tools: Jira board screenshot

Jira by Atlassian
It might be more suitable to go for Jira if or when your organization or teams:
  • Already use other tools and would like to integrate them with Jira. Atlassian has a wide variety of plugins and add-ons, both open source and paid.
  • Need to have a powerful reports system and roadmap available at all times.
  • Have to run multiple sprints in parallel for the same product backlog.
  • Consists of mostly technical people that can use and control this very customizable tool. Non-technical people may need more time to get used to the functionalities, and sometimes the organization is not able to allocate that time for it.

Remember that, in the end, both tools can help you manage your project(s) successfully. So, when you choose the agile project management tool to suit your practice, my experience shows that it all comes down to:
  • Your preference regarding the UI/UX
  • Your company’s or team’s type and size
  • The tools you already have in place
  • The available budget
  • The time you want to invest in adopting the tool and training people
  • How the tool can solve the problems you identified in your organization or team (the must-have features)

AI Insider can help you choose the suitable agile project management tool for your particular needs and budget. In every agile software development project, we can cover the delivery management as well, and set up the way of working that best suits you, so you can focus on your business priorities. If you’re looking to dive deeper into the agile matter, get in touch with us and take the conversation forward.

Continue reading

What we learned at the Manage Agile Conference

How are you enabling agility in your organization?

What we learned at the Manage Agile Conference

11 minute read
Image by Headway – Unsplash
by AI Insider team

Back in late November, AI Insider gave a presentation at Manage Agile 2020, one of the largest annual conferences for the agile scene in German-speaking countries. The event focused on agile leadership and agile project management approaches.

One important thread that stood out among the conference’s themes was Competitive advantage through agility. Our participation in the event included a presentation on the theme “Why you should enable agility within your organization, be it in IT or not”, held by Marius Podea, sharing knowledge and practice with the Agile Leadership community. That’s not unusual at AI Insider, but what made the presentation remarkable is that the topic didn’t focus on the software development industry – it looked beyond it.
“When it comes to competitive advantage, agility has never mattered more. But for most leaders, the challenge to make it a source of competitive advantage has been both a barrier and an opportunity. Markets demand that organizations adopt and change continuously. But while agility may be demanded from the outside, it is driven from the inside.”, says Marius Podea.
Over the last years, being and working agile have enabled successful software development projects. It improved product quality, delivery, and speed to market. At the same time, the motivation and productivity of the IT teams and customer satisfaction increased.
More recently, agile practices have been expanding to various industries, functional areas, and senior leaders. But how do leaders understand the agile mindset and its methods, nurture it for their teams, and benefit from it? As leaders from different industries, how are you enabling agility in your organization?
Here are 3 insights based on what we shared at the conference:

1. It’s time to make more sense of agile practices in industries other than IT.
Agility leads to better performance and provides organizations with robust advantages over the competition.

What if agile companies grow revenue 37% faster and generate 30% higher profits than non-agile companies? What if high-agility companies deliver 29% more of their projects on time, 28% more of their projects in the agreed budget, 24% more of their projects achieving what they were supposed to do, and 31% more of their projects exceeding ROI?
From more projects delivered on time to more projects exceeding ROI, from more motivated teams to improved customer satisfaction, from growing the revenue faster to generating higher profits, non-IT companies prove how being and working agile matter.

According to the extensive study, “Pulse of the Profession: Organizational Agility” that PMI developed in 2012, on more than 1,000 project, program, and portfolio managers, the expansion of agile to various industries has already confirmed at least four advantages for organizations. “The average percentage of projects completed on time, on budget, achieving business objectives, and forecasted ROI is significantly greater in organizations reporting high agility than those reporting low agility.” (PMI, 2012)

The project success metrics by level of agility (Source: PMI, 2012)
Also, the PMI study revealed that organizational agility translates into a faster response to market changes, improved efficiency, employee and customer satisfaction, risk mitigation, cost savings, and more profitable business results.

The benefits of increased agility within the organizations (Source: PMI, 2012)
“The PMI study shows us that the possibilities and opportunities that agile raises with its expansion in other industries are substantial. These are compelling outcomes that high-agility companies achieve a consistent competitive advantage compared with low-agility companies.”, states Marius Podea.

2. Teams in industries different from IT can transition naturally to agility with no experience or awareness of it.
What if their practices emerge deliberately to agile? How will it reflect on their competitiveness?

Driven by “can agile project management be adopted by industries other than software development?”, a group of researchers (Conforto E. et al. (2014), findings published by PMI) analyzed 19 medium and large-sized companies from eight well-established industries such as Automotive, Energy, Consumer Goods, Electronics, Telecommunications, and Engineering, which used a traditional management approach.
The researchers surveyed the product development and R&D managers, analysts, and executives, who had experience in new product development and did not formally use agile, to identify if they managed projects using agile. The researchers based their analysis on two key elements: practices and enablers, the predictors for the agile approach.
Formally, in the development of innovative projects, teams use traditional project management methods. Practically, their way of working is consistent with the agile approach.
On the practices side, the study revealed that:
63%
of the surveyed companies developed project planning at a macro level and by iteration (compared to 37% that approached the project planning in a traditional, detailed manner)
63%
of the surveyed companies updated the project plan monthly and weekly (compared to 37% that updated project planning in a traditional way, at the end of each phase)
53%
of the surveyed companies described the project scope with a minimal textual description, revised on the go (compared to 47% that used detailed project scope)
47%
of the surveyed companies shared the responsibility to create the project plan (compared to 5% where the PMO created it, and closed to the companies where the PM created it)

The practices and the methods used in other companies than IT (Source: Conforto E. et al., 2014)
Out of six practices evaluated, four referred to an intermediate or an agile way of working. “Even if, formally, the leadership did not put in place an agile methodology, nor was aware of it, the teams transitioned naturally to agility.”, adds Marius Podea. “As the findings show, we can understand these results as a sign that some companies are moving towards agile management or a blend of agile and traditional management practices.”
Performing innovative projects with less formalized processes and empowering the teams with a degree of autonomy to make decisions are just two pieces of evidence of favorable conditions for the agile approach.
Furthermore, on the enablers side, the study found that:
79%
of the surveyed companies had project team members with 2-3 years of experience (compared to 21% that had teams with less than 2 years of experience)
68%
of the surveyed companies had PMs with 2+ years of project management experience (compared to 32% that had PMs with less than 2 years of experience)
84%
of the surveyed companies had their team size under 12 people (compared to 16% that had the team size over 12 people)
90%
of the surveyed companies had their teams co-located
95%
of the surveyed companies involved the customer in their project planning (compared to 5% that did not involve the customer)
84%
of the surveyed companies showed an organizational structure type useful for agile
63%
of the surveyed companies used a partially standardize product development process (compared to 37% that used a process that was fully standardized)
79%
of the surveyed companies had multidisciplinary teams (compared to 21% that had not multifunctional teams)

The enablers of the agile way of working in other companies than IT (Source: Conforto E. et al., 2014)
Out of ten enablers evaluated, eight referred to an intermediate or an agile way of working. “Once again, this time from the enablers viewpoint, the analyzed companies, regardless of their industry, seem to transition to agility.”, says Marius Podea. “When team members have 2-3 years of experience, they can self-organize as a team and choose the best working solution, hence reducing the number of product iterations and waste. Customer involvement enables the team to build the product with the customer’s vision and their users’ needs in mind, thus bringing the most valuable products and features to market faster while increasing customer satisfaction. A project-oriented organizational design empowers the PM and the team to self-organize and make decisions. A cross-functional team gives the team access to the needed resources to figure out the right solutions while avoiding bottlenecks. These are competitive advantages for agile companies.”, adds Marius Podea.
Usually, teams adapt their way of working to their contexts and challenges. It is how the companies from the research applied – without being aware of it – the agile practices in their well-established industries, where the waterfall was the standard approach. While some challenges still exist, companies from industries other than IT can adopt agile and create attractive possibilities. What if their practices emerge deliberately to agile? How will it reflect on their competitiveness?

3. Adopting agile goes beyond the teams’ way of working. It is a process of transforming leadership.

“I want this to be changed now; we are agile, right?” “I want to change this, but keep the deadline; we are agile, right?”
The advantages of agility and the real transition of teams to the agile way of working are encouraging. And they would be even more valuable if every potential challenge transforms into support.
When some leaders share what they know about agile, they speak about speed, sprint, backlog, releases, velocity, and so on, and believe these automatically translate into organizational agility. But because awareness and experience lack, it becomes challenging for them to understand the real approach. And by lacking the knowledge, it’s easy for them to confuse providing information with imposing decisions.
That is the case of leaders that communicate continuous changes in functionalities while keeping the urgent deadlines. While some aspects are valuable for the team’s effectiveness and the project success, adding new layers of changes by imposing decisions, even with the best intention behind them, misses the agile practices, and fails to benefit from what agile delivers. One example is imposing the implementation of new, superficial, incomplete, partially developed/tested, or last-moment functionalities, which are not embedded into the product but delivered just for the satisfaction of one customer.
The more decisions are imposed, the more likely the product to become functionally unstable. Usually, this is the moment when the team starts cutting corners.

The cargo cult agile and the top down approach in decision-making affect the teams’ effectiveness and the project success
“Cutting corners as a response to the top-down approach in decision-making doesn’t work in the long run. The quality of the product starts decreasing, teams lose their motivation, customer satisfaction decreases, and there is a lack in delivery.” says Marius Podea. “It reveals a cargo cult agile, where the right things are said or done, but the core values are not understood.” adds Marius. “Teams should be empowered to work how they best see fit. Agreeing on a timeline is essential. Then, the teams work on and decide the best way to implement the project and to integrate the changes. Build projects around motivated individuals. With the right environment and support, trust them, they will get the job done.”

Empowering the teams supports the teams’ effectiveness and the project success
“Adopting agile goes beyond the teams’ way of working. Agile is more than concepts and ceremonies. It is about culture, a part of the organization’s being. That is why it comes with a blend of organizational and leadership transformation.”, closed Marius Podea.

Enabling agility in the organization: Wrapping it up and looking towards the future

Agile has transformed the software development industry. Now it transforms other industries.
Organizations benefit from agility in terms of better performance and competitive advantages – from successful project delivery to overall organizational efficiency, profitable business results, and response to market changes.
Then, regardless of their experience or awareness of agile, their teams can transition to agility and, therefore, organizations gain advantages over their competition. In this transition, they count on a blend of practices and enablers.
Lastly, agile makes its way to the senior leadership, and it’s transforming it as well.
So, at this point, we have factual evidence that agile can work outside the IT industry. Still, a challenge stays with us – the behavior of the people who need agile understanding. And balancing factual evidence with empathy, we all can help to head it in the right direction.
Those leaders and teams who learn to enable organizational agility in their industries and business activities will move their business forward.
There are a few practices that teams and leaders can do together to support continuous improvement:
  • Raise your level of agile understanding and learn how agile works.
  • Learn where the agile approach fits the needs and where other approaches fit better.
  • Similar to new technology adoption, start small. Start with a pilot, learn, adapt, then expand it gradually.
  • Enable your teams to approach their practices flexibly while keeping in mind customer collaboration, team motivation, a working solution, and responding to change (based on agile values).
  • Embrace agile practices within the leadership teams. It creates the context to understand and learn about agile while building the bridge between you and the teams you are empowering.
Tell us more about your experience with enabling agility in your organization.
How do you make more sense of agile practices in your industry to lead to better performance? Is your team transitioning naturally to agility, or is your practice emerging deliberately to agile? How do agile teams collaborate with leadership in your organization?
If you consider starting to enable agility in your organization, how could you enable it? If you have already started, what do you recommend to your peers?
We hope this article has helped you get the knowledge and insights into connecting organizational agility with a competitive advantage. If you’re looking to dive deeper into the matter, look no further. You’re welcome to get in touch with us and take the conversation forward.

Continue reading

Reaching the top of the mountain

Creating the path forward when there is no map.
AI Insider in the making

Reaching the
top of the mountain

7 minute read
Video by Taryn Elliott – Pexels
Today we conclude our #AIInsiderInTheMaking series, a 3-chapter story of AI Insider, the full IT service provider making businesses’ transition to their digital future real, more approachable, and sustainable.
You learned why we are in business, what we stand for, how we are going to break through the world, what we do.
As stories are more than a flash, and so is ours, we shared one chapter at a time so you could read each part in one sitting.
In the previous Chapters, Why climbing the next mountain, technology showed to be more like the gear to rely on when climbing the mountain – the partner, not (yet) the way that instantly projects the business into the digital future. Then, in The way up the mountain, trust and empathy showed how they made it easier for partners to achieve their objectives.
Today, in our last chapter, you’ll learn that partnerships cultivate and validate shared purpose first, then shared success, and achieving both means taking the responsibility to prepare and adapt continuously.
This — is Chapter III:
by Marius Podea
AI Insider Founder

Since I’ve been in the IT service industry, I’ve experienced transformation and changes that required all of us to adapt continuously. What I think made the difference in this flow was the enthusiasm. It transported people through the most ambitious changes.

Partnerships cultivate and validate a shared purpose first, then a shared success.
Before all else, for AI Insider, the enthusiasm comes from our connection to what we are doing – making businesses’ transition to their digital future real, more approachable, and sustainable. Knowing that what we’re doing makes sense to businesses, creates meaning for their people, covers their needs and objectives – this fuels our growth and adaptability when being both inside and outside our comfort zone. Then, enthusiasm comes from our connection with our clients – feeling connected with them in a way that frees our energy and lets us apply our expertise. Every partnership cultivates and validates our shared purpose first, then our shared success.
Preparedness and adaptability are a responsibility in reaching the top of the mountain.
You may believe, like me, that enthusiasm needs to be sustainable. So, we nuanced it by assuming long-term contributions. And because we think long-term, we know we have responsibilities. It’s our responsibility towards us – to gain a deep understanding of the market and grow our expertise, make responsible decisions, prepare and learn how to succeed and how to bounce back from failures, and, most importantly, to adapt along the way. At the same time, it’s our responsibility towards our clients – understand their perspectives, needs, and business environment with empathy, build trust-based relationships, approach, prepare, and adapt technology as their partner to complement them in realizing their vision and purpose.

Being prepared and adaptable is our responsibility. That is reflected in our mission statement: “Guide and help business leaders effortlessly manage their challenges with the best technology at hand.” It is how we behave – we understand the context and make suggestions while assuring the clients we are providing them the help they need to make their vision and purpose happen. They can focus on their day-to-day business while we take care of the IT challenge.
It is what we did – I’m reiterating my previous example on automation – when working with one of our clients to prepare their recruitment practices with RPA as an alternative to their manual work. In the first weeks, we performed a thorough analysis, making sure the solution brought the highest ROI for our partner. We covered the entire lifecycle while our partner focused on scaling their services and accompanying their customers on talent acquisition strategies. Now, we’re setting our next milestone to cover 2nd and 3rd level support.
The previous experience works if you continuously prepare and adapt to the climb’s conditions, as when entering uncharted paths, experience makes way for adaptability.
Everything begins with the way you perceive the top of the mountain. The journey has not ended once you reach the summit. It is the place where you catch your breath, celebrate the milestone, and look at how you got there. But it’s more than that. It’s the place to set your eyes on the new horizons. With the new horizons, new challenges and opportunities arise beneath your feet. While you briefly enjoy your achievement, you cannot stay put on this summit, as your business must reach new heights. At AI Insider, this is the responsibility for both internal growth and the clients we guided on the way up.
The way you choose your next summit to climb is double pinned: your previous experience cannot work this time if you don’t continuously prepare and adapt to the climb’s conditions.
With the status quo in mind and the direction set, we begin our next part of the journey looking at both familiar and new landscapes. But slippery paths, deep valleys, and foggy views can derail even the most well-prepared climber. As we feel a responsibility for our clients, our fellow travelers, forging through harsh conditions, we must adapt our path, techniques, and tools to get them up.
Similar to mountain climbing, in business, you make your journey while always looking for the milestones to reach. Both activities have their risks, involve navigating in always-changing conditions, and don’t end after reaching the summit of the mountain and planting your flag. When entering uncharted paths, experience makes way for adaptability.
I’m reintroducing my previous remark from the first two chapters. A technological solution is not necessarily successful because it embodies a new technology but because it integrates without risking any part of the existing business and because the people who benefit from it are comfortable working with it. It is what makes the technology valuable – not only what you implement but also the way you implement it. Reaching the summit itself might not be the definition of success, while the way you get there makes you successful.
With each milestone reached, we feel more responsible for the success of the journey and the experience of our clients, fellow travelers. As we reach higher, the conditions get harsher, but the satisfaction of a well-climbed mountain gets bigger.

That’s my conclusion for you: each climb is different, and so is each IT challenge that the business leaders have – more picturesque or mundane, more or less technical, more challenging or more comfortable, and so each IT and business challenge is in the real world – simpler or more complex about the business’s digital future, closer to or farther from adopting and scaling new technologies, focused on addressing the short-term or long-term business horizon. But there’s always a way to prepare and adapt to each climb while keeping the top of the mountain in your perspective.
After all, reaching the top of the mountain is not the purpose. It is the climb. Firstly, embrace your challenges. We’re about sustainability, about creating solutions, providing IT services, and building partnerships that last, and we’re looking at technology as a partner for businesses; we begin with the business, then pursue the technology. Then, enjoy the air with your fellow travelers. We’re advocates for partnerships built on trust and empathy. Lastly, behold the view together with them. We aspire to reach a shared purpose and a shared success, and preparedness and adaptability are our responsibility in achieving both.
In this climb, as the path forward we created, having no map, we let AI Insider be our partner, and we hope it will be yours as well.

We hope you enjoyed Chapter III, Reaching the top of the mountain, and our full story. You can anytime learn more about the previous chapters, Chapter I: Why climbing the next mountain, and Chapter II: The way up the mountain.
If you know that your network is as curious as you are, don’t leave it behind. Tell your network about AI Insider.
We’re the full IT service provider making businesses’ transition to their digital future real, more approachable, and sustainable. As you’ve already learned about us, we do this with an AI-first philosophy, the best technology at hand, and empathy.
In the meantime, we invite you to follow AI Insider on LinkedIn. You’ll get updates about work, projects, future stories.

Follow AI Insider on LinkedIn

Continue reading

The way up the mountain

Creating the path forward when there is no map.
AI Insider in the making

The way up
the mountain

6 minute read
Video by Haakon Birkeli – Pexels
These weeks, we share with you the #AIInsiderInTheMaking series, a 3-chapter story of AI Insider, the full IT service provider making businesses’ transition to their digital future real, more approachable, and sustainable.
You will discover why we are in business, what we stand for, how we are going to break through the world, what we do.
As stories are more than a flash, and so is ours, we share one chapter at a time so you can read each part in one sitting.
In the previous Chapter, Why climbing the next mountain, technology showed to be more like the gear to rely on when climbing the mountain – the partner, not (yet) the way that instantly projects the business into the digital future.
Today, you’ll learn that any IT initiative can impact the business, and acting with trust and empathy makes people better at figuring out and creating and providing the right solutions in the right way. Doing business this way makes it easier for partners to achieve their objectives.
This — is Chapter II:
by Marius Podea
AI Insider Founder

I’ve always been an advocate for partnerships built on trust, and I invest the resources I have in creating and nurturing them. I’ve seen how slowly things move when the level of trust is low, and, over the years, I’ve learned how to rely on communication and transparency to create a trusting relationship. When people see the work going on behind the scenes, every step of the collaboration, they trust us more and value our solutions and services more. We tell and show people who we are and what we do.

When people see the work going on behind the scenes and every step of the collaboration, they have more trust and value the solutions and services more.
For AI Insider, trust is the basis for everything we do and also the essence that a long-term partnership has. Building trust, however, often requires thinking about business from new perspectives. We approach partnerships by relying on technical expertise and interactions. We include here our ability to create and provide solutions and IT services that bring value and harness technological advances by relying on technology as a partner. We also add our ability to understand the business environment and sensing and responding to changes.
Let’s take the example of Robotic Process Automation. Technology-wise, we start with the processes that are well-suited for automation. We apply use cases to show the potential of the technology to answer to the pursued value, document the roadmap and the processes, design the architecture, and so on to cover the full cycle of the solution. People-wise, we ensure that stakeholders understand how they will benefit from automation. We focus on proactive consultancy and take care of the people who will be working with the newly-created solution. We communicate and engage with them at every stage, part of our support to business leaders in change management.
That makes me come back to my previous observation from my first chapter. A technological solution is not necessarily successful because it embodies a new technology but because it integrates without risking any part of the existing business and because the people who benefit from it are comfortable working with it. It is what makes the technology valuable – not only what you implement but also the way you implement it. The impact is as relevant as the purpose when building a trust-based partnership.
Balance results with empathy. Wait. Why empathy?
You can’t build trust unless you genuinely understand your clients. You have to see the world with their lenses as well, then balance results with empathy. Maybe it’s unusual to rely on empathy in business, but that’s how we ensure the impact we make is felt and measured. I think of AI Insider as a full IT service provider by nature and as a partner by approach that makes businesses’ transition to their digital future real, more approachable, and sustainable with the best technology at hand and empathy.
Why empathy? Even if the world is abundant in technologies, we interact with people. They all have their challenges, problems, ongoing changes to handle. It’s simplifying and optimizing internal business operations, improving customer-facing processes, freeing up their colleagues to be more productive, improving the speed of launch for new initiatives, meeting their business KPIs with less overhead, and so on. To create and provide solutions and IT services for them, we have to understand their vision, their business environment, industry, and the contextual flexibility to integrate and adopt a specific technology. In the middle of any change, people need empathy.
Maybe it is why we’re so comfortable spending time listening to our clients. We understand the context of their work and the promise to their customers, define their status quo, identify challenges together, and, with these insights in hand, we create and provide the solutions and services to solve the challenges and problems with measurable impact.
This year, for example, we did this with one of our clients, helping them improve the quality of the web solutions delivered to their customers, restore their team’s working path, and scale the volume of the projects. With the custom-built project management framework we provided, they improved customer satisfaction, the EBIT, as well as their team’s satisfaction.
This way of doing things – acting with trust and empathy – means a promise to our partners: if you work with us, we make every interaction you have with us an individual one. If you need to focus on the key aspects of your business or your day-to-day business, we take care of the technology. We’re also setting up the agile context that keeps you in control of the initiative in every moment of the collaboration. We tell and show you who we are and what we do.
Eventually, what we have learned at AI Insider is that any IT initiative can impact the clients’ business, and trust and empathy are the details that make us better at figuring out and creating the right solutions in the right way. We do business this way because it is easier for our partners to achieve their objectives. It’s the path forward we created and our way up the mountain.

We hope you enjoyed Chapter II, The way up the mountain. If you know that your network is as curious as you are, don’t leave it behind. Tell your network about AI Insider.
In the final part of our story, Chapter III, partnerships cultivate and validate shared purpose first, then shared success. What does it take to achieve both?
In the meantime, we invite you to follow AI Insider on LinkedIn. You’ll get updates about work, projects, future stories.

Follow AI Insider on LinkedIn

Continue reading