![]() A good asynchronous communication tool like Captivate/Snagit is useful. Lync is awesome (friends in smaller/not-so-MS-focused shops use Skype w/ success). 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. TechSmith's Snagit (the best screen capture tool I've used great for quick-and-dirty 'do this' email or doc) Adobe Captivate (decent for screencasts save time sharing your ideas inside your firewall) Rally (before HP Agile Manager, a very good Scurm product) HP's Agile Manager (expensive, but a very good Agile/Scrum product) GitBlit ('cause outside the Firewall GitHub/BitBucket isn't allowed) Microsoft Sharepoint (meh, it's better than nothing) Seriously it's only serious flaw is it needs Windows.) Microsoft Lync (excellent product! Love it. I write code and help the rest of the team write code. I work in a very large distributed enterprise so this list is a little off topic, but maybe it'll be useful for someone and maybe it will awaken a few ideas for how incredibly rich an opportunity the enterprise space is. 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Īs 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. * Interrupts - Usually this is called something else, but the gist is that some teams track operational items separately. These items generally don't take up alot of active cycles of the "Shepherd" but they are an additional context switch throughout their work * Shepherding - Work that is mostly coordinating cross-team efforts. In planning meetings and standups these are called out so we can unblock the items as quickly as possible ![]() * Blocked - Work that is blocked on something else. Some teams also use additional columns for: * 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 ![]() 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. Sure! The basics are that each team has their own board and chooses a Trello board layout that most closely matches their workflow. If you're interested in remote work, we're hiring! Are you into biking or photography? Mailing lists! Are you into Golang, functional programming, or want to chat about Linux? We have those covered too. Are you remote or based out of the SF bay area? There's a mailing list for that. Interested in an upcoming project? There's a mailing list for that. * Mailing lists! Every team has its mailing list and nearly every other thing of interest has its own mailing list. With the right workflow, we can at-a-glance know the status of all of our work-in-progress. This works great when you're widely distributed across geography and timezones. * Project/task management: Trello trello trello - If it's not in Trello, it doesn't exist. Our repos are hosted on Github and we use all the usual stuff there: Pull Requests, Issues, in-line commenting, etc * Video conferencing: Every single meeting has a corresponding Google Hangout. * Documentation: Google Drive for non-technical documentaton that might need feedback and some dynamic spreadsheets backed with dataclips. * HipChat (sync and async chat with a variety of ChatOps functionality) Some teams might have a slightly divergent set of tools or workflow, but engineering-wide this is more or less the baseline: At Heroku, we are quite distributed and typically use the following.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |