On April 19 Disciplined Agile Consortium ran a webinar entitled Disciplined Agile Offshoring: Making it Work for Both the Customer and the Service Provider (follow the link for the recording and other stuff). During the webinar we received a lot of very good questions, most of which we were able to answer. We’ve decided to write up the answers to these questions here. We’ve organized the answers into the following topics:
- Product Owners
- Common Pitfalls
Ideally, what will be the Product Owner and Team Leader’s location in outsourced agile team? Can a Delivery Manager role be infused? The Team Lead and Product Owner (or a proxy) should be on site with the development team. Many times, however, the PO is located with key stakeholders who are rarely at the same location as the development team. In this case there will be a need for a proxy, either a business analyst or better yet a (Junior) Product Owner at the site with the team who interacts with the (Chief) Product Owner regularly. You will likely need to apply the Ambassador strategy and have people fly between locations regularly.
Do most successful outsource agile projects have a product owner (junior or otherwise) and team lead role at all sites? I would suggest that. The team needs someone who can answer questions regularly. The (Chief) PO needs to interact with stakeholders regularly.
What is included in the scope of the Outsourced Work? Should it include system testing and QA testing? This depends on what the contract calls for. It is possible to outsource most of the testing effort if you choose to.
What cannot be outsourced apart from UAT/Integration Testing? Actually, you could probably outsource a lot of your integration testing effort if you choose to do so. User Acceptance Testing (UAT) needs to be done by stakeholders and those people work for the customer organization, not the service provider.
When you’re working for outsourcer, I think it is better to do manual test, to see all bugs before than spend time on automating tests. Is automated test writing always better than manual testing? I think we lose the time on automation. Automation of yours tests, or I guess more accurately your checks, is absolutely critical to your success. You can’t afford to not automate as much of your testing as possible. Yes, some testing will be manual at first, but once you understand how to run the test manually you should be able to automate it in most instances.
What the metrics to evaluate the outsourced agile delivery? This depends on what your priorities are. Are you trying to improve time to market? Quality? Return on investment (ROI)? What you measure will be driven by what you’re trying to achieve. We’re a firm believer in an agile approach to GQM.
How to measure the performance of team during outsourced agile delivery? Once again, it depends. A very good strategy is to include code analysis tools in your continuous integration (CI) strategy that provide the customer with real-time insight into the quality being delivered by the service provider.
Are Development Intelligence (DI) dashboards and code analysis tools something the consumer should expect the Service Provider to have and be using, or is this something that the Consumer needs to acquire and then share with the Service Providers? It would be incredibly foolish not to use such tools. There are many very good ones available free of charge via open source, as well as some very good commercial tools.
Apart from sending ambassadors, can you suggest any other approaches to eliminate cultural differences and we-they attitude? The only way to reduce cultural differences is to work closely together. If you’re not willing to spend at least some money on travel then I would seriously question why you’re doing offshoring at all.
What kind of indicators stand out for failing offshoring activities? The primary cause of failure of an offshoring effort is an inappropriate procurement process by the customer itself. Other failure factors include an inflexible approach to changing requirements, inadequate monitoring/governance of the project, unwillingness to pay for travel, and unrealistic expectations by the customer.
Do you recommend doing development in one place and testing in another? No. Organizing teams by function injects a lot of overhead, cost, time and risk into your software development efforts. A much better approach is to have a whole team at each location with the skills and resources required to get the job done. Some testing may still need to occur on the customer site of course, but that should be a small part of the overall testing effort.
How can we possibly be called agile when the offshore team is developing while the onshore teams sleep, and vise versa? We fix this with 20 min standups, and heavy process, and using process over comms is by definition, not agile. Should we be happy with water-agile in this case? You can strive to be as agile as possible in the situation that you find yourself in. As you learned in the webinar there are many strategies that you can apply to become more agile. You might also find our article on Agile GDD to be of interest.
How do you encourage a move away from sign-offs? There isn’t an easy answer to this one. It is quite common for us to work with organizations to help them to evolve their IT governance strategy to be more agile in nature. We often coach and mentor IT governance people to help them to move away from signing off on artifacts to a more light-weight, risk driven approach. My suggestion is to contact us for help.
Can you share any successful case study in more details? You can find some fairly easily via a quick web search.