Archive for June, 2008

Best Practice #9 “Be flexible when offshoring!”

Monday, June 30th, 2008

This is my favorite offshoring Best Practice. Be Flexible! 

When will you find the need to be flexible? During all of the times that I mentioned in the previous 8 Best Offshoring Practices. You will have to be flexible with the times of day you work, with the type of work you do offshore versus on-shore, with the type of communication methodologies you will have to be flexible (plus have a few options prepared in case the first one falls through).

In the end working offshore should not mean so many differences that the practice of completing a software development project is unrecognizable. Much of the process will be familiar to you; at first it may seem just not as comfortable due to the different times of day you find yourself working, or the means you are using to communicate (web conference tool) versus face-to-face, etc. But just like anything else, the more you do it, and that means every day, the more used to it you become and the more flexible you are the more you will find the method that works right for you, for your projects and for your company.

Best Practice #8 “Limit the heroic efforts necessary when offshoring!”

Monday, June 16th, 2008

Maybe you have heard this in your company, or thought it yourself, It takes a heroic effort every time to bring the project in when we do it offshore! Now some people thrive in the high stress of having to solve a lot of problems at the last minute, or having to work 40 hours straight, but for most of us, we will not do our best work at those times.

You have to monitor an offshore project, just like you would any other project.  Continual deliverables work the best so that you can limit the number of surprises at the end. Nothing is going to require a heroic effort like throwing a project over the wall and not checking in on it for 4 months when you actually need the final project. Not just accepting the answer, everything is okay, without actually seeing some results, will also help prevent the need for heroic efforts at the end.

Put an appropriate monitoring system in place, the same as you would if the project was in house and let it work for you. It may not always eliminate the need for an extra push at the end of the project, but it should give you more confidence in the results that you are going to get.

Collaboration 2.0 – A book review

Sunday, June 15th, 2008

While not news for many of us, much of what is driving the developments in Collaboration and the developments in collaboration tools is the necessity to create a Virtual Team space (VTS).  Early in the book the authors define 10 trends in collaboration, the most interesting to me is the trend which they call, “Presence Everywhere” which means being able to detect which involves basically being able to quickly find a person whether they are online or on the phone or in a conference room. A typical scenario as to when this may be useful is given (and I am sure a familiar one to everyone); A and B are working together via web conference and they need C to help solve an issue. Typically one or both A and B will be looking through their buddy lists to see if C is available online, if not both may try calling C via various numbers; office, cell, etc., and if they are finally successful in finding C it may take several clicks of sending links to bring C in to the web conference. IBM is working on their Sametime product to have this type of capability to reach external contacts. LiteScape also apparently has ways to detect the availability of users not only via instant messenger buddy lists but also from your list of outlook contacts and detect their presence via mobile devices.

If you were not already familiar with the term, the book introduces you to mashups as another trend in collaboration. A mashup is the process of creating a hybrid application built from data or functionality found across a number of different applications. An example of this can be seen in a site listing real estate, for example, which uses a 3rd party site or application to provide information about criminal activity in or around the house which is for sale.

There is no shortage of collaboration tools which the book introduces you to such as TimeBridge which can help you schedule meetings faster, but a great part of the book is the emphasis on the human aspect of collaboration. As they say, collaboration is 10% tools and 90% people.
The second half of the book takes a look at the human side of collaboration with chapter 7 specifically focusing on virtual teams. A very good point is made at the beginning of the chapter that the challenge has traditionally been how to minimize diversity among the people on teams whereas the key in the future will be to embrace the differences and work with them. I agree with this whole heartedly and would extend this to all aspects of working in a distributed manner, for example – time differences, location differences, etc.

Chapters 8 through 14 also focus on different aspects of people and processes. A lot of what was written was review on how teams work, it will most likely be review for a lot of people. What I found funny was, for example in Chapter 9 on Interpersonal communication, the author mentions how important Mirroring/Identifying is in building report, but he doesn’t go in to the next step of how you do this when using collaboration tools.

Chapter 15 is supposed to bring it all together; the human side and the technology side, but I found it a bit lacking. It talked more about the different stages a company may be at in using collaboration tools, and why they may have problems implementing them, but it did not seem to go that step further and talk about how to overcome the actual road blocks to working with distributed teams and actually using the technology.

In general this is what I thought was lacking in the book overall; actual examples or case studies of the use of tools and use of team interaction processes to overcome problems. On pg. 194, the authors discuss the work of one of their clients, and I agree it is an excellent example of an operational agreement between two distinct agencies. There is a lot of detail there, however, there are very few other real life examples given in the book. Adding additional examples and case studies, which I have no doubt the authors must have from their consulting practices, would have made the book much stronger.

My first thought with this book is that it is especially good for larger companies which are working with a number of collaboration tools, or looking to implement them. However, chapters 1 through 6 which relate to the different technologies that are available, as well as the appendixes listing a number of different technologies, can also be very interesting for smaller firms which are often working virtual from the very start of their existence. As well, for most anyone who reads this book, unless you are a study of collaboration tools you will most likely be surprised at the wide range of tools available and perhaps at what is considered collaboration technology. As far as functionaries who will appreciate this book; marketing folks can certainly get a number of ideas for tools that they can use to do their jobs better, software engineering folks, and anyone who has to deal with remote teams on a daily or almost daily basis will benefit from reading this book.

Collaboration 2.0: Technology and Best Practices for Successful Collaboration in a Web 2.0 World
Authors:  David Coleman and Stewart Levine
Published: January 2, 2008

Let’s take it as a sign in Ukraine! Paul McCartney gives a free concert on the Maidan.

Sunday, June 15th, 2008

While it has nothing specific to with outsourcing, let’s take it as a sign of the attention that Ukraine is getting; for investment, for business and for entertainment events.

Myself and about one hundred thousand + other people in Kyiv were treated to a wonderfully entertaining 2+ hours of music, not to mention the thousands who had gathered to watch on video screens in Kharkiv, Donetsk and Lviv and the millions watching around the country (where they were all much drier than we were in Kyiv!).

It is great news for the country that it is being recognized as a world class country and attracting such events.

A sea of umbrellas greeted Paul McCartney on the 14th of June in Kyiv!

Best Practice #7 “Time Differences do not have to the be Enemy!”

Saturday, June 14th, 2008

Does this sound familiar to you: Outsourcing offshore can only work if I am up the same hours that they are, otherwise nothing gets done! Or from the offshore side you may here, They never want to come in early and talk with us, we always have to adjust our schedule. One of the best things you can accept early on when working with many offshore locations is that there will be time differences. The sooner you accept it as a fact of life, the sooner you will start to look for how this can benefit you and your company!

Certainly anyone can understand that separating tasks like testing in one location and software development in another location can provide benefit, such that overnight unit testing can be done in one location and in the morning the other side can pick up its development work fixing the bugs reported by the testing team.

Time differences can also be to your advantage if one side is doing 1st level customer support and another region is doing 3rd level customer, for example. It is even possible to share this type of work; bugs which need more research can be worked on continuously.

But the time differences can even work to your advantage when both sides are working on the same project; even an agile development team of five persons; four software developers + 1 QA tester with 3 of the developers in one location and one developer and a QA tester in another location. Or even more than two locations, a team can make this work and make progress faster. Let’s an issue comes up, not sure how to solve it; work does not have to stop, one side can continue trying to solve the issue overnight, and the other side can keep it going the next morning. Two years ago, Fortune magazine used a great example of a far-flung work force making it working on continuous development of the same product, MySQL. Today MySQL has 400 employees working in more than 25 countries, over 70% of whom work from home. Part of what probably made this work right from the beginning is that MySQL is an open source product and it started with a culture of individuals all over the world who believed in the product and wanted to work on improving, and improving what others did to the production, and they wanted to do it right from their homes. MySQL did not have to try and change its culture to work in many locations; it was that way from day one. Many companies do not have that luxury; the culture of the organization has to change to be accepting of working with many locations. But once that difference is accepted time difference can be an advantage to getting work done faster.

The point is that the time difference will be there no matter what, so you need to make it work for you! Be flexible and be creative, time does not have to be the enemy.

Softjourn supporting Entrepreneurs and Startups!

Saturday, June 14th, 2008

On June 20th, in Mountain View, California, Softjourn will be sponsoring the next Visibility Conference hosted by Righthand Partners and taking place at the offices of Fenwick & West LLP, 801 California Street.

The event begins at 8:00AM and continues until 2:00PM. Righthand Partners has selected seed and early stage (Series A, B, C, & Restart) companies who will each give a 10-minute presentation, and receive 10 minutes of feedback and questions from investors sitting in the audience. Usually there are more than 20 VC’s in attendance. For more information go to the Right Hand Partners site:

Softjourn is very pleased to be sponsoring this event and supporting entrepreneurs and Startups and wishes all presenters the best of luck!