- P2 WordPress theme from Automatic: http://p2theme.com/
- Sqwiggle: https://www.sqwiggle.com/
- Trello: https://trello.com/
- GitHub: https://github.com/
- Campfire: https://campfirenow.com/
- Zapier: https://zapier.com/
- RelateIQ: http://relateiq.com/
- Help Scout: https://www.helpscout.net/
- HelloSign: https://www.hellosign.com/
We wrote a lot more about how we use them here: https://zapier.com/blog/how-manage-remote-team/
* HipChat (sync and async chat with a variety of ChatOps functionality)
* Documentation: Google Drive for non-technical documentaton that might need feedback and some dynamic spreadsheets backed with dataclips: https://postgres.heroku.com/blog/past/2012/1/31/simple_data_...
* Video conferencing: Every single meeting has a corresponding Google Hangout. For some meetings we might use Fuze
* DCVS: git. Our repos are hosted on Github and we use all the usual stuff there: Pull Requests, Issues, in-line commenting, etc
* Project/task management: Trello trello trello - If it's not in Trello, it doesn't exist. This works great when you're widely distributed across geography and timezones. With the right workflow, we can at-a-glance know the status of all of our work-in-progress.
* Mailing lists! Every team has its mailing list and nearly every other thing of interest has its own mailing list. Interested in an upcoming project? There's a mailing list for that. Are you remote or based out of the SF bay area? There's a mailing list for that. Are you into Golang, functional programming, or want to chat about Linux? We have those covered too. Are you into biking or photography? Mailing lists!
P.S. - If you're interested in remote work, we're hiring! http://jobs.heroku.com/
Generally, we'll start with new work on the left side of the board and completed work at the right side of the board; this roughly resembles a kanban board. The standard columns are:
Ready/Next (backlog) -> Doing -> Done
* Ready/Next are the top items from the backlog (usually a separate Trello board just so only active items are on the primary board) that are next in the queue
* Doing is work-in-progress
* Done is completed work (of course :))
Some teams also use additional columns for:
* Blocked - Work that is blocked on something else. In planning meetings and standups these are called out so we can unblock the items as quickly as possible
* Shepherding - Work that is mostly coordinating cross-team efforts. These items generally don't take up alot of active cycles of the "Shepherd" but they are an additional context switch throughout their work
* Interrupts - Usually this is called something else, but the gist is that some teams track operational items separately. For example, if support escalates a support ticket to an engineering team, the trello card referencing the ticket and any troubleshooting info will end up in one of these columns
As for ensuring that the Trello boards are up-to-date, many teams have standups and walk through their Trello board and confirm that it's consistent with reality.
We use Jira w/ Agile for tickets & project management, Confluence for knowledge base, HipChat for communication, Bitbucket for code repository et al. Wrote about this and how we use it here: http://www.theroadtosiliconvalley.com/engineering/medlert-ca...
Hope this helps!
- chat during the day (hipchat)
- skype for voice calls, usually to quickly discuss something
- Google hangout (highest bandwidth communication, I run my daily standups on google hangout and sporadically for "crisis" moments or "clarification" moments)
So the trick is to have a daily scrum meetup on google hangout every morning so that you can explain tasks, check how far everybody got the previous day and update the trello board to reflect the new state. It's the only moment in the day that communication is cheap and high bandwidth.
Google docs and github wiki
There are other auxiliaries like github, airbrake, circleCI and papertrail that report into hipchat so you can get a sense of the work being done.
Totally agree with the morning meetings though, plus we have one longer scheduled weekly.
1. Searchable backlog for all discussions.
2. API for connecting bots (which can be used for C&C).
3. Web-based and native clients.
4. Public and private rooms chat rooms.
HipChat is more like IRC than like IM, which, for distributed teams, is often very useful.
- Hipchat: Internal discussions and exchange, syntax highlighting, easy room and pwemission management, updates from other services (github, new relic etc). Furthermore to push notifications to email, mobile device and/or via text.
- Skype: easy 1on1 communication with externals (sometimes replaces the regular phone), internal LAN file transfer
- Google Hangouts: group video conferences (our company uses Google Apps so everyone has it and can access it from anywhere through a browser)
I probably missed some features and usecases, but I think I got the most important ones :)
- Microsoft Lync (excellent product! Love it. Seriously it's only serious flaw is it needs Windows.)
- Microsoft Outlook
- Microsoft Sharepoint (meh, it's better than nothing)
- Trello (useful for ad-hoc teams)
- GitBlit ('cause outside the Firewall GitHub/BitBucket isn't allowed)
- HP's Agile Manager (expensive, but a very good Agile/Scrum product)
- Rally (before HP Agile Manager, a very good Scurm product)
- Adobe Captivate (decent for screencasts; save time sharing your ideas inside your firewall)
- TechSmith's Snagit (the best screen capture tool I've used; great for quick-and-dirty 'do this' email or doc)
- IntelliJ IDEA (great IDE, we don't use it collaboratively or anything but it got into our Enterprise because individual DEVs could buy it at a reasonable price for themselves, then other DEVs wanted it and mgmt started signing POs... smart tactic).
Sum it up. Lync is awesome (friends in smaller/not-so-MS-focused shops use Skype w/ success). A good asynchronous communication tool like Captivate/Snagit is useful. Some shared space to manage the work is necessary (Trello, HP Agile Manager, Rally, numerous other good products). I wish I had Campfire or something like it.
You'd be surprised how good many MS tools make remote development/communication. I don't work at MS HQ in Redmond (I'm in Boston) so my whole team does tons of work with people remotely every single day.
For example, Lync on the Windows Phone is really great: you can join a meeting from your calendar/meeting reminder and instantly get video or a PowerPoint slide deck. I am frequently running late to a meeting in the morning so I just dial-in on my phone while I walk to work.
Remote desktop performance is good enough to actually code on, which I never found to be the case with VNC (even TightVNC which was darn good and I was happy to rely on for everything but coding). This is huge for me since all of my development machines can be headless (no kb/mouse), for use remotely or in my office.
Outlook makes starting an online meeting/conference call one click.
I don't think Roundtable devices are for sale anymore, and they don't always work which is really annoying, but they work most of the time and make conference calls with video and lots of people really good.
Screen sharing over Lync isn't super amazing (I don't even think you can go full screen) but it's so convenient I use it frequently.
Presence is baked into everything really well, so if you're actually using MS for everything you will get presence everywhere. It's also pretty good about being more than just presence, so you get pictures/avatars, online status, location, out-of-office messages/status, quick links to start an email/IM/etc.
As for non-MS software, I really like using Sublime Text as a code navigator. It has AMAZING performance when browsing code on a network share. I can load all the MS Office code from a remote development machine, over the network, into Sublime Text and the file-search works within seconds. I have no idea how it indexes all the files so quickly.
If you're looking for a more stable multi-platform chat product with video support, Ignite's Openfire works great (and also has AD integration).
And its usually pretty hard to say anything nice about Bugzilla.
* google docs
* google mail
* google hangouts (with perma-rooms)
* our own awesome chat (http://chat.stackoverflow.com)
* trello from everything from shopping lists to kanban boards
* our own hosted git and hg, with a kiln "skin" for the looks (plus pretty much any public repo for the myriad open source projects we maintain)
* our own live status (https://github.com/opserver/Opserver)
* team city for CI/CD
* vydio for large whole company meetings
Campfire for chats, dumbot as a minimalistic task manager in campfire https://github.com/tadast/dumbot#tasks
Github issues for technical/code problems.
Google hangouts for standups
- New Relic for LAMP stack monitoring http://www.newrelic.com
- Zabbix for infrastructure monitoring https://www.zabbix.org/wiki/Main_Page
- Splunk for storing all syslog http://www.splunk.com
- TargetProcess for agile pm http://www.targetprocess.com
- burndown chart generation http://www.conceptuel.co.uk/burnDown (one of mine actually)
- reviewboard for code review http://www.reviewboard.org
In job #2 (remote, almost 4 months in): Features, bugs, release planning, code and some documentation, all in Github. Chat: IRC Cloud or Skype. Calls and screen sharing: Skype or Google Hangouts. No VPN but lots of SSHing into machines on Digital Ocean. Some other documentation in Google docs.
- IRC (most of us use IRCCloud)
- Discourse (a forum, I can really recommend this even if you have chat, and Discourse is particularly good)
- Skype (only used for one on one meetings)
- Oovoo (like Skype, but has free video conferencing, we use it for meetings with more than two people)
- Rietveld (a review system, we have mandatory reviews for all changes, really really important for distributed teams IMO)
- Trello (we're in the middle of migrating to a real bug tracker (Roundup, what bugs.python.org uses) though)
- Google Drive (mostly as a wiki replacement)
* Google Mail & Calendar
* Hipchat. Main communication method, water cooler and catch-all for any new activity for our deployments and GitHub repos
* GitHub. We use everything it has to offer and have actually migrated to Issues from Trello for task management
* Google Docs. For feature specs and anything that needs to be in sync outside the development team
* Dropbox. Mainly used by the design team right now, as a single source for assets and putting mocks in
* Skype. Usually for one-on-ones and interviewing candidates
I like Hamster for time tracking, https://projecthamster.wordpress.com/
Cloud9 IDE (https://github.com/ajaxorg/cloud9/)
Timer Tab (http://www.timer-tab.com/)
Bitbucket and Github
VirtualBox (running Ubuntu with all the usual stuff)
That's pretty much my entire toolbelt.
Photoshop for remote working? I fail to see how it relates.
"VirtualBox (running Ubuntu with all the usual stuff)"
All my terminal stuff is in there. I also use Secure Shell for Chrome for SSH.
- Github for source code mostly (I've made some pull requests since I'm new on the project)
- Hipchat, since I've join, Skype before that.
- Dropbox for file sharing and design.
- Google Apps
- Basecamp for project managment
and I may not know the full stack yet but we use cloud services for everything!
Has anyone tried sqwiggle.com, we tried it, but we get the same thing from impromptu google hangouts for free. A truely native sqwiggle app that integrates more into what we are doing makes sense.
* JIRA - issue tracking and feature management
* Agile - scrum management
* Confluence - documentation, mockups, feedback
* Bitbucket/Git - code repository
* Facetime or Google Hangout for video chat
* Salesforce chatter for IM though Hipchat is a better solution. We're a small company so we need to be able to answer questions from marketing, sales, operations throughout the day
Pretty short list when i think about it.
Also basecamp for communication with the managers and between them.
EDIT: I use Asana and Google Docs as well.
was v impressed by Cisco video in contract recently but they were Fortune 500 so I assumed it was beyond us mortals
No idea how much the video costs either, but my employer is a Fortune 500 company.
('cstub' is a wonderful program that is downloaded over HTTP and runs as root. It's supposed to monitor security, or something. I did mention I run this on a VM, right?)
- Google Hangouts (thrice weekly check-in meetings)
- Asana (task management)
- Github (all code is submitted as PR to be reviewed by someone else)
git, Bitbucket, Github