It’s true, we in Comminus surely does not base our recruiting process on 40 yard dash or vertical leap (as I’d probably wouldn’t be writing this if that was the case) but being a quick thinker and being passionate about the technology is what we will seek in out tryouts.

Technology evolves whether we talk about IT, sport or any other area of our life. For years you are hearing everyone talks and promote how they use various types of agile processes. No matter which agile framework you want to use, every one of them demands interdisciplinary approach. So what this has to do with sport? Well modern basketball also expects of biggest guy on court to be able to shoot from the range when is left wide open.

Our approach in Comminus is that each member of the team gets to say his vision on how each functionality should be done. Discussion is part of the process we do within our development team but also with our clients. What our clients can learn is that we don’t aim just to help make product they want but to give them solution they need and solution that gives them edge over their competition. To work like this is exciting and challenging at the same time. That’s why learning about new technologies and their implementation is not just encouraged but required.

 “It's the little details that are vital. Little things make big things happen.”

In our mission to make the most out of the little details that will do a difference we are following new breakthroughs in technology. If you are avid follower of our blog you may already read about this in Mario’s post.  As in another of our blog post Matea mentioned one of the tools we are using is Team Foundation Server. I will paraphrase Microsoft and their TFS landing page catch phrase, we use TFS for Share code. Track work. TEST WORK. Ship software.
 

You may wonder why I had the need to add testing to catch phrase written by persons who thought this through and are, I’m sure, top professionals when we talk about writing slogans. Well, if something I’ve learned in all this years in industry, testing is often considered as necessary evil. Doing proper testing is number one thing in the list that you will be tempted to cut-off or skip when things get rough, when time is running out or you want to keep budget on tight leash. Even though it will sound very tempting, and at some point you may think that is the most reasonable thing to do it.
 

Testing is one of does little things where we will challenge you hard. There are tons of articles all over the world written about testing and about various types and technics. What we aim for is that we keep testing the product in mind from beginning of the process. With first definition of products key feature or down to defining user story that we will implement one of the major questions is “How are we going to confirm that this is working as defined?”.
 

While it may seems that most important part of testing is the ability to verify our work I would be bold enough to say this is just a neat byproduct. While we are questioning ourselves how to test the feature of the end product, we are thinking about how will the end product be used. This discussion when done with product owner helps both sides to identify things like:

When your product is in end phase of development or already in production with running support issues and improvements we will encourage even more that our code / your solution must be covered and any change must follow with update of various types of tests. From unit tests, coded UI tests to more challenging functional tests. Proper testing together with continuous integration and minimum of 4-5 separate environments enables us all to make sure that the product delivers the best possible experience to the end users. Because in in the end, for the end I’ll quote famous NBA campaign: