Blog /Business and Project Management

The product owner has an important role in a team, so it’s better to set with them cooperative objectives, expectations, and rules at the beginning of a project. And this is where great communication skills can help.  A happy customer can hire your team again for another project or recommend your software development agency to their friends. This is why your relationship with a product owner is very crucial for the success of your company.

Do you really believe that showcasing your company on Facebook is enough for your company to get noticed in the internet? Before you answer, check the advantages of having your own website!  “Do I really need a website for my company?” This is a question that many entrepreneurs need to answer. Perhaps hearing such a question should make us feel offended, but in the depths of our souls, we understand this dilemma. After all, it only takes a few clicks to appear on the Internet.

Nowadays, people spend more time than ever being glued to the screen, so they can see hundreds of different websites each month. Are they even engaged when most of the websites look the same? Does your website stand out from competitors and is a real attention-grabbing machine?  The average American internet user spends twenty-four hours a week browsing the web.

Drupal has a reputation for being hard-to-manage compared to other Content Management Systems. At Droptica, however, we believe that it makes up for it with its incredible versatility and flexibility. The following ten Drupal websites are the best examples of this! 1.

In Droptica, the development team works closely with the designer. Close cooperation and unrestricted contact allow building websites that not only are visually attractive and perfected in terms of UX and UI, but also perfected in terms of programming.

After implementing scrum for Droptica's Drupal developers, we observed outstanding results in terms of the quality of our projects. In our opinion, scrum not only helps with maintaining quality – it simply enforces it. How does it do it? It puts emphasis on testing as early as possible. Writing good code that can be developed becomes a necessity. It supports automatic testing and automation of the development process. It reduces unnecessary costs and increases business flexibility.

At Droptica, remote work is something ordinary. From the very first day, we had two offices in Wrocław and Gdańsk. Recently, we also opened our third office in Rzeszów. Every day, developers, testers, graphic designers and other specialists work together in each of these locations. In addition, 90% of our clients come from abroad, like in the case of most software houses. Throughout several years, we have developed methods of effective and efficient cooperation in a dispersed team.

Droptica helps clients from all over the world to complete and implement their projects. Each of these clients has already developed their way of working. Everyone is different. In this article, I have collected the most common ways and systems of cooperation between Droptica and our clients. Why do we work a little differently with every client? We are Agile. We always want to maximise the results of our work.

Drupal is fantastic for all sorts of websites and applications. Drupal excels especially at large, complex content projects. If you know what you are doing, you can often cut development time substantially compared to other tools made for the same purpose.  Drupal's versatility, however, is a 2-edged sword. With great flexibility, extensive API and an abundance of modules created by the community, it takes a long time to get up to speed.

We recently wrote about  why SCRUM improves software development quality and why remote scrum teams are often a good choice.  Today we will discuss a very important part of scrum which is often neglected, what leads to reduced preformance, delays and mistakes - Sprint Retrospective.  What is Sprint Retrospective? This is one of the meetings in the SCRUM methodology. The meeting takes place on a regular basis, at the end of each sprint.