Agile software development is based on the principles of Lean Management, i.e. we work customer-oriented , continuously deliver real value following the Pull Principle, and we always strive to improve our processes. This delivers important features to our projects that most traditional projects are missing. Our projects are …
1At fixed intervals of a few weeks you get ready usable functionality delivered in the highest quality. You do not need to wait until the end of the project for your product, only to find out that it’s not quite what you wanted.
2You can check the quality at any time directly on your growing product and you don’t have to be satisfied with half-finished prototypes or work packages. You always know what we’re working on, how long it will take and what comes next. So you have project progress and costs in your sight at any time.
3Our high transparency allows you to control the project in a flexible and secure way. You can incorporate new or change existing requirements at any time during the project. You also decide when the product is sufficient for you and if you want to terminate the project after the running iteration.
4We not only implement, but also think ahead and develop your product step by step from practice together with you. You don’t have to specify your product in documents as a complex, theoretical construct, only to find out later that the practice has different requirements. We help you to find the smallest solution that covers all your needs. So you get exactly the solution you need – no more, no less.
1Compared to other eastern european countries like Poland or the Czech Republic Bulgaria still has fairly low hourly rates, and this with a reasonable spatial and temporal distance. The time difference is only +1 hours and our development center in Sofia is only about a 2 hour flight away.
2There are hardly any significant differences in the mentality of the bulgarian developers to their german colleagues. Our developers work independently and responsibly, speak very good English and sometimes even German. The bulgarian universities provide education at a high level. Its graduates are technologically up-to-date.
3Since Bulgaria is a EU member, transactions enjoy basic legal security. However, your contractual partner in our projects is always our german headquarters. This allows us to guarantee you a trouble-free project execution. So you don’t have to worry about EU or even bulgarian law.
You don’t have to write detailed specifications anymore, be a process or technology expert, lead the team or run the software. You can dedicate yourself entirely to your product and its features. We take over the complete …
1We capture and refine your requirements with you. You do not need to create thick specifications anymore or bother with cumbersome requirements management tools.
2We care about the complete staffing of the project with the appropriate employees, we completely provide the technical infrastructure, establish the development process and ensure its compliance.
3We deploy, monitor and maintain your application on the test, staging and production environments – at your place or ours. We host your product also cloud-based, in our cloud or our hosting partners’.
4We coach our development team in professional, technical and interpersonal concerns and provide friction-free communication with your involved employees – even across the language barrier.
Our high product and process quality in our projects is primarily the consequence of our lived agile values:
1Positive regard is the foundation for trustful and open collaboration. We treat everyone with respect – whether customer, employee, co-worker or supervisor. If you feel yourself respected, you don’t have to be afraid to tell the truth or to hear the truth.
2Only when you know the truth, you can make the right decisions. We therefore communicate information in an open way – positive and negative, praise and criticism. Thus, we are able to discover misleading developments very early and to react on them appropriately.
3Everybody loves to bring good news. But it’s the bad news that will save projects. In order to deliver but also to accept and learn from them, it requires courage – courage for the truth and courage for change. We cultivate both in our relationships with our customers and employees.
4We are authentic in what we say and do. If we commit ourselves, you can be sure that we will be 100% behind it. We rather reject a project, if we have doubts about its feasibility, than we rush you and us into an adventure.
Due to the synergy of our values, innovative methods, open source technologies and efficient tools your overall costs are reduced even more significantly. Here you’ll find out why.
Clear, direct and continuous communication is an essential prerequisite for successful agile work. The best way is, of course, when customer representatives and the development team are in the same place and speak the same language. Neither is possible in nearshore projects. This places high demands on the communicative skills of all persons involved in the project.
We therefore use Moderators in our projects who actively support all project participants in communication. In addition to the professional and technical know-how of an experienced project manager and IT consultant, moderators have at least two other important skills:
1Friction losses and inefficiencies in projects usually arise on an interpersonal level and unconsciously for the project members. With the help of group dynamic know-how, our moderators are able to quickly identify blind spots in communication, misunderstandings and other conflict potential, to make them accessible to the participants and to work efficiently with them.
2Our moderators are at home in German and Bulgarian culture and speak fluent Bulgarian as well as English and German. This enables them to interact with both cultural sides of the project with appropriate sensitivity.
1In agile projects, planning is frequent and collaborative. In order not to waste any time with our virtual teams, we use easy-to-use web tools in which each participant can observe what the others are doing in real time in their browser. If someone is unable to attend, they are automatically notified of important changes by e-mail or instant messaging.
2In our virtual meetings each participant should get as much as possible from the other. That’s why we use powerful web conferencing software with HD resolution and desktop sharing. If a participant doesn’t have access to the Internet, he or she can dial in by phone for free.
For larger teams, we provide a live HD stream from the developer’s room – even bidirectionally if desired. So you are live and close to the action.
3Each project has its own virtual project room. It is easily accessible via web browser and contains all information about the project, e.g. contact data of the project members, current news or access to tools and operating environments.
Furthermore, all project artifacts, such as source code and other documents, are available to all project participants via a modern distributed version control system.
4All our project team members can be reached via VoIP, chat or telephone. Each project room provides its own chats and news feeds. So you can contact the developers directly at any time if you have any questions and you will be informed about the latest developments immediately via App, RSS or Instant Messaging. Access to project-relevant computers is via remote desktop. We mainly use AnyDesk, currently the fastest tool on the market.
If you are at war with these new technologies, you can also use our project moderator as a communication hub.
Our employees are highly responsible and self-determined. For us, it is therefore very important that applicants find themselves in our corporate philosophy and working method and that we can also employ them according to your wishes.
1Our selection process starts with interviews. With their help, we clarify whether the applicant basically has the desired qualities, i.e. what experience he or she has in which software technologies and how his or her personality harmonizes with our agile values and our way of dealing with each other.
2In Reviews of the applicant’s current project work, we then gain an impression of the technical demands he has on his work and how he implements them. Among other things, we investigate the question of whether the applicant creates memorials of his competence or writes beautiful, pragmatic and comprehensible code.
3Finally, the applicant works on a trial basis in one of our internal projects. This shows us whether we and the applicant also fit together in practice. During the trial period, the applicant will be introduced to our tools and methods as well as other technologies. Afterwards he will take over the first tasks in one of our customer projects.
Most of our applications have a collaborative character and are implemented by us as web applications. All web frameworks we use are based on the principle “Convention over Configuration”, implement the MVC pattern and are widely used. This guarantees high productivity in the creation and maintenance of applications, keeps the onboarding times for new developers short and the supplier lock-in low for our customers.
To ensure that the applications we develop fit perfectly with our customers’ IT strategy, we mainly use three variants of web frameworks:
1Rails is currently the secure web framework with which the highest productivity can be achieved. We use Rails primarily for stand-alone applications with little dependency on third-party systems or a higher-level IT strategy. This environment can often be found in smaller companies and start-ups as well as autonomous branches or departments.
2If a company relies on Enterprise Java as a strategy for its applications, diverse legacy systems such as ERP, CRM, DMS, etc. have to be connected or the performance requirements are extremely high, Grails is used. In addition to high productivity, it enables seamless integration into the Spring- and JEE world with all its advantages.
3If a company relies on Microsoft, we develop our applications in ASP.NET MVC. Since version 3 this Framеwork offers sufficiently high productivity advantages with simultaneous seamless integration with existing Microsoft technologies.
Of course, these are not the only technologies in which we have competence and experience. We also develop applications with classical frameworks like JEE, .NET, Cocoa and languages like PHP, C++ or Objective-C.
A fair contract design allows us to concentrate fully on the development of your product and does not waste time negotiating contract details or what a change or defect is. We don’t want you to be bound to us by a contract, but by the high quality of our work.
1The quality of our implementation is not determined by a rigid specification, but by your current requirements. If you do not like the implementation of a product function at the end of an iteration, you do not have to pay for it. We will then fine-tune it until you are satisfied. However, the continious involvement of customer representatives during implementation ensures that this case does not usually occur.
2You can finish the project after each iteration, i.e. every 1 to 4 weeks. If, for example, you are of the opinion that the functionality implemented so far is sufficient for your purposes, you can end the project at the end of the current iteration. In practice, it can happen that customers have changed a large part of their original requirements and achieved their project goals below the originally planned budget.
3We offer you different ways to pay for our services. We have made the best experiences with Pay per Hour, because in this way the highest transparency in the project is achieved. In combination with regular inspections and flexible exit options, a win-win situation is guaranteed.
However, you can also pay by volume if you do not feel comfortable with purely expense-based payment. We call this Pay per Point: The scope is estimated in points per requirement. However, we do not offer a classic fixed price, since in our experience there is always a loser here.
4An important factor in the satisfaction of customers, suppliers and their employees is, in addition to quality, pricing. Nobody wants to pay too much or earn too little. As a nearshore service provider, we are able to offer significantly lower prices than local software companies. We are and do not want to be the cheapest, because we know that quality also has its price in Bulgaria. We pay this price in the form of fair wages and additional services for our employees.
5According to agile understanding, the detailed specification of requirements before a project and the subsequent explicit management of change requests is a waste. In agile projects, requirements are therefore only documented to the extent that a rough estimate and planning is possible. The details are then clarified immediately before and during their implementation. Short delivery cycles and the continuous involvement of the customer provide the necessary transparency to quickly adjust estimates and planning. Experience shows that this empirical, flexible approach leads to considerably higher customer satisfaction at lower project costs.
1The person responsible for the product knows the business processes to be implemented in the product and those surrounding the product with sufficient precision to derive the product functions with their business value from them and to plan their implementation in the project. He alone is responsible for the return on investment by designing the product over time, i.e. he determines WHAT and WHEN. In agile projects it is also referred to as the “single drinkable neck” and is a mixture of product manager and project manager.
2Depending on the project size, one or more end users should support the project. In addition to the person responsible for the product, they are the direct contact persons for the detailed design and acceptance of product functions. Only by involving end users can it be ensured that the product is not developed without the support of the people who will later work with it. The scope for design is clearly limited by the scope of the functions defined and planned by the person responsible for the product. This prevents the infamous wish concert.
3In order to establish a continuous delivery flow in the project, continuous participation of the customer representatives is also necessary. In addition to regular meetings for requirements clarification, project planning and quality assurance, project managers and end users are available at fixed times of the day to answer developers’ questions.
4The first agile project initially unsettles most customers because it lacks the central pillar on which the perception of security in classic projects is based: The requirement specification and the detailed project plan based on it. However, it only takes a few iterations before they realize that the security provided by the degree of completion of work packages is only a sham. It quickly becomes apparent that real security in the project can only be created by delivering real value, i.e. usable product functions.
Trust in the agile approach is most quickly gained when you apply it. However, it takes courage to leave even seemingly safe ground and break new ground. The great success of agile processes may make this step a little easier. We cordially invite you to join us.