Category: Software

Categories
Entrepreneurship Software

The next edition of Espeo Junior Academy is coming. Take the opportunity and become a Node.js or React Developer with us. 

The following article will explain the opportunity of attending Espeo Junior Academy. At Espeo, we focus on values of development and partnership. Academy is dedicated for Juniors who are looking for an excellent opportunity to start their career. With us, you will have a one of a kind opportunity to become a Node.js or React Developer under the guidance of top experts.

It is not the first educational project we are running. There are people in our Crew who took their first steps as programmers with our previous endeavors like this one. Nowadays, they are top experts in their technologies and they are happy to welcome a new generation of Academics. Therefore, we know it works. Read the article and find out for yourself.

You will find the answers on the following questions:

What is the Espeo Junior Academy? Why is it worth participating in?

During the Espeo Junior Academy, for 2-4 months, you will cooperate with our experienced mentors, who will support you in your career development. The program will be individually tailored to your experience and knowledge. Participation is free of charge. Additionally, you will receive a salary throughout the training period. After completing the training, we will offer you evaluation and introduce you to work in commercial projects with our clients. 

Espeo Crew

The program is dedicated to students who are looking for a place to gain practical knowledge and various experiences from experts. The Espeo brand has been known on the Nordic and European market for 14 years. During this time, we developed the latest technologies and became innovators in various areas. The Espeo team consists of people focused on development and who stay up-to-date with the changes in our dynamic industry. The value of the program is visible in the feedback from the Alumni of the previous Academy. 

Hint from Espeo Junior Academy Alumni

Meet Aleksandra Czajczyńska who graduated from the Espeo Junior Academy.

We asked Aleksandra to share insights into her experience with the Academy. This is what she said: “When I received information that I was qualified for the next recruitment stage at the Espeo Junior Academy, I was excited. That was my first experience with the Assessment Center. I got a technical assignment and Adrian Warkocz evaluated me based on the Espeo competence matrix. Then, I was assessed as Junior II, and invited to participate in the program. I’ve decided immediately to move from Wrocław to Poznań to take advantage of this opportunity. In retrospect, I know it was all worth it!“

Aleksandra Czajczyńska, Frontend Developer & Alumni of Espeo Junior Academy

She continued: “I received a lot of support from experienced developers during the whole training. Consequently, I learned that there are no stupid questions in IT. It was the first time that I had the opportunity to work with such a large team of developers. I got a chance to work on a commercial project with new technologies from the very beginning. At Espeo, I became an equal team member, and I got lots of support. And what’s more, I have developed my interpersonal skills while working with clients. Espeo Junior Academy is not a typical internship program. That is a real chance to start a career. I heartily recommend it from the perspective of a graduate of this program.”

Why is it worth building your career here?

We are a reputable Digital Consultancy. Because of this, you can be sure of the value of the acquired knowledge. Working at Espeo is a dynamic journey through the changing technological reality and projects full of challenges. Therefore, you can be sure that our team will provide you with the latest knowledge and you will take your first steps based on the current technological trends.

Find out more about the specifics of working in a software house compared to a product company here.

What differentiates us?

Our company operates based on the Finnish work culture. Flat organizational structure, transparency, and focus on the value of feedback and development. Consequently, our employees stay with us for longer and come back to us from other organizations. Espeo and the Academy are more than just a chance for professional development. Here, you will also meet great people and make valuable friends.

Our office in Poznań, Poland

What knowledge and skills should I have to participate in the program?

The goal of our Academy is to create development conditions for people who are looking for a place to develop and gain their first commercial experience. The program is adjusted with participants’ level of knowledge and experience. We focus on an individual approach based on mentoring and developing values.

We are looking for ambitious students determined to develop professionally within the technological paths we offer. You should have a technical basis to start your career as a developer.  Also, it is required to have good English skills – minimum on B2 level. Finally, you should be available full-time during the training time. 

I see the Academy as an opportunity to gain the first commercial experience for people just starting in the IT industry. Currently, there is a deficit of employees. Moreover, employers still are interested in hiring people with more experience and a high level of specialist competencies. The Academy is a way to open a new career path for young developers. As a company, we see this as a new way to expand our team – from the selection of outstanding juniors – to the formation of experienced technology consultants.

Agata Staszak, Chief of Staff
Our office in Poznań, Poland

To summarize, if you already have at least basic technical skills, you know English well and you relate to our organizational culture, it means that this project is just for you!

From whom will I learn? Meet Mentors of Espeo Junior Academy 

At Espeo, we want you to learn from the best specialists from the very beginning. Our mentors are experts in their fields and great colleagues who approach the idea of sharing their knowledge with great enthusiasm. Once you finish the recruitment process and accept our offer, you will be assigned to a mentor. It is essential because we want to give you the best learning possibilities. We hope for you to become a permanent member of the EspeoCrew after completing the course. 

During the Academy, you will be able to observe our specialists and learn from them. We are not afraid of questions, and our mentoring support model is based on a feedback culture. In the circle of our Mentors Team are Adrian Warkocz (Senior Frontend Developer), Aleksandra Kasprzak (Senior Software Developer), Łukasz Błaszyński (Senior Frontend Developer), and Wojciech (Senior Node.js Developer). They are a great group of enthusiasts who are not only world-class specialists but also great at passing knowledge to others.

Espeo Crew

Meet our Mentors!

Adrian Warkocz was one of the creators of the first Junior Academy at Espeo. He is very proud of this project and willingly volunteered to create the next edition. What’s more, Adrian himself gained his first practical experience in a similar program. Therefore, he knows how important it is for young specialists to get into the profession by practice and to have support from experienced colleagues. Adrian has incredible energy and enthusiasm to share his knowledge. Various experiences that he gained can be a great example and inspiration for younger colleagues, and Adrian is very happy to share them.

I started my career similarly! Therefore, the opportunity to be a mentor is a great joy for me. I love sharing knowledge. Also, the chance to work with people who are just starting their careers and have a different point of view is a valuable lesson for me.

Adrian Warkocz, Senior Frontend Developer

Aleksandra Kasprzak (Ola) is a versatile specialist who constantly expands her knowledge with great enthusiasm. She is an active member of educational platforms. When she started her professional career, she realized the admirable culture of the IT industry focused on personal development and sharing knowledge the most. As a great example, she indicates Stackoverflow, where others spend their free time helping industry colleagues solve the problem. Ola is known for her ability to easily share her knowledge, and willingness to support her colleagues at work.

The culture of sharing knowledge in the IT industry is visible through the enormity of open-source projects, blogs, and free libraries that make our work easier. One of the practices for sharing knowledge that I have chosen is mentoring. In my opinion, this is a very effective form of learning in which both parties can learn a lot from each other.

Aleksandra Kasprzak, Senior Software Developer
Espeo Crew

Łukasz Błaszyński is a specialist appreciated by colleagues for his wide technical knowledge and the ability to work under pressure. He is a versatile specialist who shares his expertise in an accessible way. You can see this by reading his publications on our blog. Working with Łukasz is a pleasure due to his ability to work in a team and inspire others. At Espeo, we value Łukasz for his positive attitude and for being an inspiration for others.

Being a mentor allows me to share my knowledge and experience with people at the beginning of their career path. Each of us has started once. Therefore, I know how important it is to get support from experienced people who will show the right direction of development. That’s my motivation to be a mentor.

Łukasz Błaszyński, Senior Frontend Developer

Wojtek is a man who spreads a positive aura around him, and everyone appreciates the possibility of working with him. He inspires others with great knowledge and the ability to organize work under time pressure. Wojtek is a supportive colleague and experienced mentor who can appreciate others and share valuable feedback. At Espeo, we appreciate him for his willingness to spend time helping others and his great sense of humor.

Personally? I missed mentoring when I started working as a programmer. Junior Academy is an opportunity to pass on good practices and a pragmatic approach from the very beginning of your career. Sharing knowledge is a non-zero-sum game, especially in IT – we can draw full handfuls together!

Senior Node.js Developer

The Academy’s mentors are wonderful people who have the best conditions to teach you and help you start your career. The atmosphere at Espeo is not just words. All members of EspeoCrew from our office in Poznań are waiting impatiently for new colleagues from the Junior Academy.

Why is it worth it to boost my career as a Node.js Developer at Espeo?

The Espeo Junior Academy focuses on technologies in which we specialize. Thanks to our great experts, we carry out a wide range of projects in Node.js. Therefore, we can offer our team members innovative projects that we implement. That is an excellent opportunity to gain various experiences and build your development workshop based on the best and current practices.

Node.js breaks records of popularity on the backend. It convinced both startups and big players – due to its speed, scalability, great community, and wide range of applications.

Senior Node.js Developer

Espeo Crew

Node.js Developer is a position that we are constantly looking for at Espeo. The market demand is high, but there are not so many places where you can get a workshop by learning from experienced practitioners. Participation in the Academy is an opportunity to gain practical skills and project experience. Our aim is that you join EspeoCrew permanently as a Node.js Developer.

Read more about how to become a Node.js Developer on our blog.

Why is it worth it to boost your career as React Developer at Espeo?

At Espeo, we have a frontend team, thanks to which our experts created an incredibly effective and developmental environment. These are perfect conditions for building your career as a React Developer. As part of our team, you can discuss challenges in the project and learn from more experienced developers.

We pay attention to well-designed web applications, written with Typescript, containing tests, and accessibility. As React Developers, we can work with new technologies on various projects. Many projects allow us to learn how to choose a technology stack for a specific problem. 

Aleksandra Kasprzak, Senior Software Developer

The market demand for React specialists is greater than the number of skilled people. Many want to work as a React Developer, but there is a lack of ways to gain real experience. Participation in the Academy provides the opportunity to develop and learn from the best experts on the market.

When it comes to writing Single Page applications, React is the leading framework that sets the standards for writing modern javascript applications. Choosing the react developer path guarantees very wide employment opportunities.

Łukasz Błaszyński, Senior Frontend Developer

React Developer is a position that we are constantly looking for at Espeo. Joining our team is an opportunity to learn from the best. We are looking for ambitious and development-oriented Developers to join EspeoCrew.

Don’t wait! Join our paid internship program and start career as Node.js or React Developer.

Categories
Entrepreneurship Software Technology

The future of buying software development: Aki Inkeroinen’s and Kris Honkola’s insights

Welcome to the second article from our FutureTalk series, where together with industry experts, we cover the future of various topics related to software development. In the following article, we focus on the predictions for acquiring software solutions.

Continue reading to find insights on the topic from experienced IT professionals: Aki Inkeroinen, accomplished Sales Leader and ICT Business Developer who is currently a Managing Director of Espeo Software, and Kris Honkola, Senior Digitalization Consultant with over 30 years of experience in the IT industry.

Table of content

The evolution of the purchase model of software solutions. Will software as a service platforms replace custom development? Experts weigh in

According to Aki, the process of solution selling itself has not changed much over the years. The business needs have to always be considered together with the decision makers and this is a step that cannot be omitted. That being said, certain changes can be observed when it comes to the awareness of companies in terms of different technologies and solutions. Today, business owners can easily research various approaches so they know more or less what is required in order to bring their idea to life. This greater awareness impacts how software development providers interact with clients who wish to be more involved in the process. Another change that can be noted (and that wasn’t available 10 years ago) is the availability of Software as a Service platforms that were created as a response to the growth in market demand. While SaaS solutions address a range of needs, most of them do so in a generalized way. Taking this under consideration, custom development remains the best choice for companies who want to build a digital solution that will give them the competitive edge.

The future of buying software development: Aki Inkeroinen’s and Kris Honkola’s insights

Custom development is particularly useful in industries such as healthcare, where a lot of data is processed by a number of parties. SaaS solutions are not the best option in such cases as they rarely meet all the business needs and requirements. Hence, a certain amount of custom development is always necessary. This is why sometimes building a digital solution from scratch is actually the more profitable option. That being said, SaaS platforms make a good choice for businesses where the digital product needs to have a standard functionality that can be easily provided without customization, for instance SaaS platforms for accounting, email, and other standard business processes. Custom development is often avoided by companies since it is seen as a time-consuming and costly process. However, it is not entirely true. Both Aki and Kris mentioned that over the years they worked with companies that purchased SaaS solutions which haven’t fully met the businesses’ needs. As a result, they had to be partially customized, which ended up costing more than a custom-made solution. Therefore, choosing a SaaS solution may prove to be just as time-consuming and expensive as custom software development. In the foreseeable future, more and more software as a service platforms will cover a wider range of needs, however, custom development will continue to be the choice of companies with more complex business objectives.

What are the trends in the way business owners collaborate with ICT teams?

A lot of businesses operate in a way where business owners are not included in the decision-making processes, especially when it comes to digital investments. The reason for it is the fact that often it is believed that the IT team should be the one making the final decision about the tools, as its members have the technical background and consequently, they will be the ones using them. It can be agreed that bypassing the business leaders is hence the reason why custom development may not be the preferred option while planning digital projects.

The future of buying software development: Aki Inkeroinen’s and Kris Honkola’s insights

The lack of business owners participating in planning digital investments needs is a real problem. Nevertheless, it is a universal phenomenon. According to Kris Honkola, every 10 years we can see a trend towards greater collaboration between business and IT teams only to see it disappear again. Why is it then important to balance the roles of decision makers and ICT teams? Shortly put, the overall competitive edge of the company will suffer if one party has more say in investment or development. Here are two possible scenarios of a such situation:

  • When the technical team does not incorporate the business owners’ insights, thereby increasing the chances of developing a solution that can be useless to the end-users. For example, the IT team might be experts on a certain technology so it is the one they take under consideration when implementing a new project, even though a different technology might be better.
  • When the ICT team’s value is overlooked by the business owners, the company can be deprived of crucial technical background and insights while developing a solution.

An external business consulting can be useful in this scenario – not only does it enable a collaborative discussion, but it also provides an external perspective on the problem. Many studies have been conducted on successful businesses that invest in digitalization to find out what factors make these investments successful. The common denominator in every case was the close collaboration between the IT department and business leadership. A successful investment can only be achieved if the business leadership works together with sales management, ICT, and other departments. Then, business owners have a better understanding of the technical limitations and possibilities and the technical teams know what is the overall business goal of the project they are involved in. To sum up, there is a direct correlation between the most profitable and successful companies and a close integration of the particular company departments. It is predicted that more companies will utilize this approach in order to maximize their growth.

How will the Finnish software development market develop in the coming years?

There is a growing trend toward remote work in Finland. As a result, the acceptance of hiring talent from outside Finland will grow. Moreover, an increasing number of companies will decide to outsource their software development needs. According to Aki Inkeroinen’s prediction, the trend of remote work will most likely spread to the public sector, where the developers usually had to work onsite. The model of remote work will likely also be accepted by banks and other organizations. What is more, for decades, Finland has been at the forefront of using outsourced ICT solutions. Now, thanks to an increase in cloud based software development, Finnish companies will continue to develop competitive solutions.

How will the needs of businesses change in the future when it comes to buying software solutions?

It is likely that the future needs of clients will solely address the issue of not having enough developers. Even now, companies cannot cherry pick the best developers due to the ongoing shortage of developers. We predict that more and more software houses will be approached by potential clients with this problem.

What is more, to get the best professionals to work on their projects, clients will need to be active in selling them to the developers. The reason for this is that developers want to work on interesting and challenging projects. They want to have a real impact on how they work and the tools they’re using to get the job done. Refactoring an old-fashioned system for instance is not an exciting, desirable project. In such a case, a better option would be to hire a team of experienced IT experts in order to build the system from scratch. By having to implement these interesting and complex digital solutions to stay competitive, businesses indirectly accelerate the digitalization process. We will see this trend playing a bigger and bigger role in the future.

Do you have more questions about the consulting? Let us know using the form below and one of our colleagues will contact you shortly.

Categories
Other Software Technology

How to choose the right career path in IT: the perspective of working in a software house vs product company

The following article will explain how cooperation within a software house differs from cooperation within a product company. Moreover, they will tell you how the organization profile affects the development of the technological product.

The expertise comes from exposing yourself to experiencing new things and challenging your previous thoughts. Therefore, there are questions you probably ask yourself as an IT specialist. Where to work? Which place to choose for career development? What is related to working in a software house? Is it different from working in a product company?

We discussed these issues with our specialists, who built their career portfolios in various organizations. Adrian Warkocz, Senior Frontend Developer, and Michał Sipiak, Senior QA Specialist shared their perspective. They decided to return to Espeo after several years of gathering different experiences. Adrian and Michał are professionals who have designed a practical career path for themselves. Their point of view can be valuable both for clients and specialists seeking the perfect career path. We asked them the following questions:

What’s your perspective on working in a software house? 

Adrian Warkocz: The most essential part of working in a software house is that the projects are constantly changing. We have a well-established framework that allows us to adjust psychologically to a new challenge. We can assume that here is the beginning, these are our goals, we can see where our role in the project will end. It is not always the case that we create a project from scratch but we have a certain time frame on the horizon. There is a clearly marked start and finish, which makes the pursuit of milestones easier from a psychological perspective. If I work on a project for a long time and I start to feel that I would like to try something different, I can ask for a change, move to another project, and even completely change the technology.

Michał Sipiak: From my perspective, the biggest merit is that while working in the software house, you are in the position of business advisor. We cooperate closely with clients and that allows us to establish partnership relations. Therefore, we can directly suggest the best solutions for the product and client. We need to stay up-to-date with the newest solutions and trends. We need to use modern tools and follow what’s new on the market. That’s a great value for both the client and the employee. Technology is moving forward so fast, tools and trends change from year to year, and a software house seems to be the best place to keep up with these changes and not be left behind.

Who would you recommend working in a software house to?

Michał Sipiak: There is no one-size-fits-all recipe. For me, a software house is a place for people who value independence, enjoy working with clients and want to develop their own skills. Hierarchy is usually flat and your opinion matters. I think that’s also a place where you can grow faster. This is because we are able to change projects and technologies if we want. We are experts with diverse experiences with passion for constant learning and development. I believe that a software house is a place for people with a proactive attitude.

Adrian Warkocz: I value having an influence on what I do and to be able to change. I see a software house as a place for people who mind to be up-to-date with market changes and have an impact on the final project. My point of view also changed due to different experiences and pandemic situations. Therefore, a sense of belonging has become important to me. I’ve missed it elsewhere, and it was remote work and the conditions of the pandemic that drew my attention to this topic even more. That’s why I decided to come back to Espeo.

What was the main reason to come back to Espeo?

Adrian Warkocz: Software houses are not always structured the same way. During my career, I had experiences where I was sent directly to the client and had no ties to the company and didn’t feel comfortable. The method of managing the team and running the organization is important to me. At Espeo, I enjoy the flat structure and the fact that I know the status of the projects. If I do not like something, I can talk about it without embarrassment. I am confident that I will be listened to and that some action will be taken. Espeo is a specific place where you become a member of Crew, and you can build lasting relationships. Even after some time, there are still lots of my colleagues, and I’m happy to work with them again. 

Michał Sipiak: There is something in it. I would say that Espeo loves you for who you are. It does not try to change who you are to fit the company’s personality model. Therefore, you’re independent and you can guide your development. At Espeo, you can self-evaluate based on clearly defined guidelines. We all work towards the same goal. You can talk to everyone about everything without worrying about how it will affect your future career.

Interested in joining #EspeoCrew? Check out our open job positions and apply!

What’s your perspective on working in a product company?

Adrian Warkocz: Companies are very different. Usually, they have one specific product. Working in a product company is based on large projects that can last for years. You can change a certain scope of tasks but often the space for maneuver is smaller than in a software house. While you finish revision no. 2, there is revision no. 3, and sometimes you can feel like it’s a never-ending story. From a psychological perspective, you have to approach yourself differently not to lose your motivation. In my case, I saw that’s not a good career path for me. I don’t find myself in organizations where we face similar topics daily. For a person who doesn’t like a strong stabilization, burnout can happen quickly. 

Michał Sipiak: From my point of view, in a larger product company, it is difficult to offer new solutions and tools. Usually, they are already planned, purchased, and contracted for a long time. From an employee’s perspective, it is attractive to have well-known products on your CV. Additionally, working in a product company is stable. However, I see here a risk to constantly working on the same tools. Especially, specialization in a single technology or product poses a great risk – afterwards, it might be difficult to find a place in such a dynamic market.

Adrian Warkocz: There is also another point to consider. Product companies often have a larger budget because their product is designed for long service life. As a result, the hardware or software can be of the highest quality. They have funds for what software houses may not. In addition, there is more time to work on the project since the development pace is slower.

Michał Sipiak: Tools with expensive licenses – often such automation is a vicious circle. If the program does everything for us, the human becomes part of the process. After all, the software takes care of most of the work for us. The point I am trying to make is that it is dangerous to become a clicker in our market. It’s a bit like getting a driving license and getting into a Tesla… Would you be able to drive a classic car afterwards? In both cases you drive a car but it requires different driving skills. Generally, both ways have pros and cons.

Adrian Warkocz: My experience indicates that there is also a lot of conceptual work in product companies, which involves numerous discussions about product development. Is it an advantage or a disadvantage? It is a very individual matter. Some people like to figure out the subject conceptually before starting a typical technical work. However, I prefer the other side – more practical tasks than discussions.

To whom would you recommend working in a product company?

Michał Sipiak: I can share the experience I gained as part of an internal IT team at one big company. I had no contact with the client. The internal business was an actual client for us. So, that’s a big difference from working at a software house. Most often, you are part of a team with little influence on the final product. For that reason, product companies make a good place for people who like a stable environment. In addition, from my perspective, promotion in such companies is often influenced by many structured factors, and it takes longer.

Adrian Warkocz: When I moved from Espeo to a product company a few years ago, my colleague was leaving at the same time. Accidently, we even ended up in the same company. And this is the best example of how different people find themselves in different places. He appreciates stability, working on the same product, knowing what awaits him in six months, a year, and beyond. I have opposite needs. For me, it is important to have the perspective of change. I need to know that I can move forward and face various challenges. Moreover, I need to know that I can make an impact on the product.

Michał Sipiak: To sum up, if someone is interested in stabilization, a product company is an excellent opportunity. For some people that can be the best solution.

What is the client perspective?

The type of organization influences the characteristics of experts inside the organization. As a client or project owner, it’s valuable to see the point of your developers. Right people are a success factor of every project. Therefore, that’s a reason to consider the differences and potential advantages. How it’s to develop a particular digital solution with a software house and within an internal team? That’s a question to ask yourself before starting the project.

Karolina Fras, Employer Branding Leader

Adrian Warkocz: A software house is primarily a group of people who have various experiences and are valuable advisors for the client in product development. People who work in software houses have the ability to look at the product with an “out of the box” mindset. Also, they are up-to-date with technologies and novelties. While testing a new product, it is also much easier to scale the team and reduce it while seeing that it’s not meeting the business needs. In that case, working with a software house is more cost-effective and easier from the organizational perspective.

Michał Sipiak: From my point of view, expertise and consulting knowledge are top values. As a client, you hire a software house with experienced specialists. You describe the project, and you get solutions that tell you how to achieve it in the best way, taking your needs and capabilities into account. I disagree with this simple scaling as a larger value. Scaling up and completing projects quickly are the characteristics of contract workers, and I see the differences between software house experts and contractors.

Software house vs product company: summary

The best summary of our conversation will be the question that I asked my colleagues at the end. “How do you see your professional future?” Probably many people wondered about the answer while preparing for the interview. In practice, both Adrian and Michał have not got such a question yet. Why? I think their answers speak for themselves. After a moment of reflection, they both admitted it was impossible to predict how the industry will change in 2 years. What they would now indicate as a dream project or technology may soon be overshadowed.

What is the current perspective after coming back to Espeo?

At the moment, Adrian wants to develop mobile technologies and leadership competencies. Michał, in turn, wants to create code and learn about new technologies. They both mentioned that thanks to the variety of projects, they have a chance to stay up-to-date, which is their priority. Therefore, that was the main reason for their return to work at a software house.

Through years of experience in various organizations, they have concluded that the priority is to stay current with the market trends. From their perspective, they can achieve it in a software house. Moreover, in their eyes, such working and development conditions make a software house an excellent business partner for clients. Here they can find the most experienced and versatile specialists who will take on the role of a business consultant to implement innovative and complex ideas.

Does it mean that Software House is a perfect place to work for everyone?

There is no golden meaning for everyone. Everyone should identify their priorities. Then choose the best space to realize them. In the case of Adrian and Michał, this place is a software house. For others that could be a product company, project outsourcing company, or freelancing may be a perfect choice.

Categories
Software Technology

The future of agile: a conversation with Tomasz Liberski, Service Delivery Director at Espeo Software

The future of agile development

Welcome to the first article from our FutureTalk series. FutureTalk features articles written in cooperation with top experts in the field on a wide range of topics in the area of software development.

In the following article, we focus on the topic of agile development and its future. Together with Tomasz Liberski, Service Delivery Director at Espeo Software, we go through the evolution of agile and we share valuable predictions about its future. Continue reading to learn more.

What is agile? A few words about Agile Manifesto

The Agile methodology was initially outlined for software development. It emerged from the concept of Lean and was defined by seventeen software developers in the Agile Manifesto in 2001. The Manifesto, created as a result of a discussion about the future of software development during a Snowbird summit, is based on twelve principles, which can be found here.

Benefits of an agile development

Some of the advantages of agile approach include:

  • Continuous improvement
  • Disciplined execution
  • Iterative feedback
  • Stakeholder involvement
  • Increased transparency
  • Efficient communication with proactive team engagement

An expert’s view of the fundamentals of agile

The Agile philosophy revolves around the fact that every team member works closely together and the Product Owner bridges the gap between the business world and the technical world. Clients and software houses used to communicate and work together under strict terms in the past as the processes weren’t flexible and the cooperation was constrained with contracts. This started to change after companies started following the agile philosophy. Agile requires a great deal of education on both sides as it consists of a number of decisions which decrease the amount of redundant work that has to be done. With an agile approach, the development team is an integral part of the business – they understand why they are working on something and they have a feeling of a common goal. As a consequence, the team is more engaged and has a bigger impact on the project’s shape and success.

Time and time again companies have trusted us as a software development provider. Read more about some of our projects and find out why.

Agile means that every team member needs to take part in the decision making on a daily basis as well as take the responsibility of it. Moreover, it allows for the free exchange of ideas – every member of a team can contribute ideas and impact the development of a project. Some say that developers are not keen on working in agile. There is the idea of becoming a T-shaped profile (a general experience in all areas) so that everyone can exchange ideas and share their knowledge. Many developers, however, are opposed to this approach and instead prefer to specialize in one particular field.

The evolution of agile

When Espeo was established in 2008, it was among the first software houses to emphasize agile development. At that time, the agile approach was notably preferred both by software houses and the clients – offering agile development was one of the factors taken under consideration before starting a cooperation. Today, however, the phrase “agile” has in some ways lost its value – it is often overused, so people view it with skepticism. Nevertheless, if you consider Agile manifesto as a collection of rules and beliefs rather than a methodology per se, it still forms a valuable core for managing software houses and projects.

With 14 years on the market, we have gained valuable expertise in various areas. Read more about what we excel at.

Over the course of time, we have noticed that companies have departed from the core of the agile manifesto – its principles and beliefs have eroded. Instead, organizations have adopted specific practices that are not indicative of agile but are believed as such (e.g. a daily stand ups). Conventions such as daily stand ups aren’t at the heart of agile – they have not been stated in the Agile Manifesto. They are, however, good practices and are commonly used in many companies. The downside of this is that people have come to associate agile with such practices, and the agile values have lost their importance. The foundation of agile development consists of a variety of values. Agile practices are a totally different thing – they address the same values but are different for every organization. Companies that implement agile values can freely adjust their practices according to the inspect and adapt rule and e.g. have a sit down and not a stand up.

Contact us

The future of agile: a conversation with Tomasz Liberski, Service Delivery Director at Espeo Software

It has been argued that agile values are outdated, although I believe that the original agile principles included in the manifesto are still relevant and adequate. This doesn’t mean that certain agile principles haven’t been tested over time. For instance, in the pandemic times, the rule about face-to-face communication may no longer hold much significance. Moreover, it is arguable if the communication using different online platforms is less effective than face-to-face communication. In an international setting, for instance, online communication makes it easier to communicate regularly between technical and business professionals on a daily basis. Martin Fowler has once written that most groups are more productive working in a co-located manner. I believe that a well-assembled team that works remotely can outperform a co-located team composed of inaccurately chosen members. The same applies to teams with members located in different time zones. If synchronous communication is maintained, the project has high chances of succeeding. It is the asynchronous communication that slows down the processes in complex teams.

What the future holds for agile development? Tomasz Liberski shares his predictions

There are a couple of predictions for the future when it comes to agile. Firstly, a certain power struggle can be observed. Employees demonstrate that remote work can be just as effective as working on-site. On the other hand, many companies indicate that on-site work is better. It is therefore likely that agile principles will continue to adapt to the remote reality of managing projects. Secondly, globalization will continue to have an impact on software development processes. This means that agile principles will play a big role in the management of software projects across borders and the implementation of global strategic management processes of many companies across the world. In terms of agile (putting remoteness aside), there are voices arguing that it is the right approach at early stages of product development (e.g. MVP). Nevertheless, to ensure the success of the product later in the lifecycle, a focus on high-quality processes and continuity is crucial. This is where the topic of DevOps comes in. It can be viewed both as an evolution of agile and its complement. The last prediction for the future of agile is that the term itself will undergo a certain type of rebranding. As mentioned earlier, this term has become a buzzword in a way. In order to promote its beneficial values, it might get modified to better suit the current industry climate. What is for sure is that agile is a useful and still timely philosophy, and its rules (when correctly applied) benefit the organizations.

Ready to build a successful digital product together? Leave us a message and we will get back to you shortly.