With InterVenture we are able to extend our in-house team optimally. Due to the agile organisation and direct communication, our team in Belgrade is completely involved in all major projects.

Jeremy Seitz


InterVenture Best Practices: Tomatoes Rot, and So Does the Code

Posted by InterVenture on July 20, 2015

Clean coding is one of the programming elephant paths of today. “Clean code always looks like it was written by someone who cares.” – says Michael Feathers. It asks for new practices and specific discipline. As a result it brings back the results.

In time, we have recognized value of clean code.


IV Best Practices: Automating the Release Process with custom MSBuild Scripts

Posted by InterVenture on June 26, 2015

In .NET world MSBuild is the build engine, the guy that transforms your code to binaries. Code is built by interpreting scripts and they hold a sequence of build steps. Usually, the only scripts that are used are project files, like csproj or vbproj files. On build server,


InterVenture Best Practices: Craftsman, Not a Smith

Posted by InterVenture on June 16, 2015

Writing code is a beautiful experience. Every programmer will surely testify it is. Writing software is a different thing, though. It is a job, and it comes with things not so attractive. First of all, it comes with customer requirements. Then it comes with schedules and deadlines. It is also known of constant change,


InterVenture Best Practises: Estimates In the Agile Development Process

Posted by InterVenture on May 27, 2015

Yes, developers are strange. Let’s just face it. Developers operate on a different wavelength than managers. Agile developers in particular tend to deliver in short cycles, listen for the client feedback and turn that into the next development cycle.

At the same time, management wants to know dates and costs.


InterVenture Best Practises: Product Owner, Not Project Manager

Posted by InterVenture on May 12, 2015

In our company, we are trying to regulate the development in slightly indirect ways. We have recognized that direct management of developers is a bad idea. Quite the contrary, we have recognized that nourishing a well-informed product owner brings benefits that cannot be achieved otherwise.

Product owner is responsible to join the three poles of the structure: clients,


InterVenture Best Practises: If It Ain’t Simple, It Ain’t Agile

Posted by InterVenture on April 28, 2015

Writing software is amazingly simple when it comes to processes. Don’t let the complexity of the software itself sneak into the process of producing code. Understanding and modeling the domain, testing and packaging, all of those are one side of the coin. Managing the process is the other side.


Pick Your Development Tool: ConEmu – switch to consoles for more productive programming

Posted by InterVenture on January 27, 2015

Developers in my company (and most senior developers in general) are power users. Power users often need to access functionality of OS that is not available in GUI (or meant to be). On the other hand, they want to automate repetitive tasks.

This is the place where consoles step in.


Sprint Planning in Distributed Scrum Team: Lessons Learned

Posted by InterVenture on January 13, 2015

Having a team which is separated geographically carries several challenges, one of them being the question of planning sprints. Root problem here is that members holding different roles are stationed in distant offices.

One of the most important lines of division appears between business analysts and development staff.