![]() Here is a quick list of environmental items that feed into our pairing tool’s features. Since many of Zeal’s developers are remote and not sitting with our clients (or each other), we have a need for tools that will solve this geographic problem. ![]() Our daily work includes pairing with other members of our company and pairing with our client developers. The reason this is important to us is because we are a consultancy that prides itself in XP methodologies, including pair programming. There were other screen sharing solutions, but no other tool gave the kind of interactive session between two or more people that Screenhero offered. When Screenhero came along there was nothing filling the seamless pairing tool space. Finally, I will quickly review what contenders are out there. Then, I’ll define types of tools and their ability to meet our features. From there, I will extract some features that are important to us. I will use it as a way of defining our environment. Screenhero is a good place to start our review as it gives a baseline of why it solved our business problem. While Screenhero wasn’t perfect (as really nothing can be) it did its job very well for our environment. ![]() With Slack’s notification of Screenhero being end-of-life’d we at Zeal are looking for new solutions to a problem that had been already solved. ![]() Update: Article about the newly released Tuple pair programming application. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |