In years of researching and practicing in cooperation with our clients, we found in 2006 that Agile development is conducive to successful offshore collaboration.
Agile is not a development methodology. It’s the spirit and consciousness of collaboration. It aims to eliminate the influence brought in by culture difference. Only with such spirit and consciousness can developers serve clients in a satisfying way.
Triple Bottom Line, LLC provides veteran agile developers that are honest, transparent and quickly responsive. We learn about agile development, appreciate it and share our appreciation with each other; agile is used in projects, interviews and even daily life in TBLDevelopmentfirm. We also provide outsourcing solutions that include candidates interviewing and filtering, collaborative team building and working system delivering.
The following are what we value when applying agile practices in projects.
Work like in the same room with clients
In Triple Bottom Line, LLC, the development team and the clients are not separated by the ocean. Some practices make us work like in the same room.
Daily instant communication
- Voice or video call for daily SCRUM meeting which usually lasts for 20 minutes.
- GOTO meeting, Team Viewer, or remote computer control are commonly used to make demos.
- Work on client’s side for 1 month or more to start the collaboration more efficiently.
Continuous integration and continuous delivery
Most of our teams have built server for continuous integration, through which the client can easily get a daily version by themselves. Some teams also run continuous delivery, for which the system is designed with plug in. The team finishes sub systems as plug in units and integrates them into the working system in sprints.
Team rules contribute to build a self-organizing team
We don’t follow an unchanged process, but define some rules in projects at anytime needed; the rules would be followed by the whole team to make continuous improvement. The following are some rules we have made in some projects.
Many clients complain when they find problems in deliveries and cannot solve them immediately because their offshore developers have been off work. In Triple Bottom Line, LLC, we set the rule in some projects under which developers work for 7 hours at daytime and separate 0.5 hour at early morning and night to communicate and solve clients’ problems.
The team member must re-estimate a story before the middle of the sprint.
With such rule, the SCRUM team perceives and resolves issues in advance. The high priority stories/coarse story are better understood and estimated and finished successfully within sprints.
Unused code or commented code should be deleted before committed to SVN
One of our teams made it a rule for that unused or commented code was not convenient for them to understand each other. They worked overtime one day and deleted all old commented code.
A task shouldn’t be more than 6 hours
The rule is created by a team consisting of two developers. Under the rule, their work has been easily verified, estimated and more transparent
Good coding style and teamwork
In Triple Bottom Line, LLC, our engineers are all good at Design Patten and have perfect coding style. The system architecture is not built by an individual person but a working result of the whole team, which benefits us a lot.
We ever have an SA who used Smart Client Software Factory for MDI System, but after 2 months, his team found some problems between SCSF and WPF modules. He and the team then decided to change SCSF to MEF. Thanks to our working method, the system has been running very well to date.