
* 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/](http://jobs.heroku.com/)

~~~
ubercore
Can you share any of your Trello workflow? We still have trouble sometimes
making everyone happy with our current Trello workflow, I'd be really
interested in hearing how you organize your cards!

~~~
hoop
Sure! The basics are that each team has their own board and chooses a Trello
board layout that most closely matches their workflow.

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
* DCVS: git. Our repos are hosted on Github and we use all the usual stuff there: Pull request, Issues, in - credit 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 wide distributed across geography and timezones. With the right workflow, we can at - a - glance acknowledge the status of all of our work - in - advancement. 

 * Mailing list! Every team has its mailing tilt and nearly every other thing of interest experience its own mailing list. Interested in an upcoming undertaking? There's a mailing list for that. Are you remote or based out of the SF bay sphere? There's a mailing list for that. Are you into Golang, functional programming, or want to chat about Linux? We experience those covered too. Are you into biking or photography? Mailing lists! 

 P.S. - If you're interested in remote workplace, we're hiring! 
 [ http://jobs.heroku.com/](http://jobs.heroku.com/) 

 ~~~ 
 ubercore 
 Can you share any of your Trello workflow? We still have trouble sometimes 
 making everyone happy with our current Trello workflow, I'd be really 
 interested in hearing how you organize your cards! 

 ~~~ 
 hoop 
 Sure! The basics are that each team has their own display panel and chooses a Trello 
 board layout that about close matches their workflow. 

 Generally, we'll start with newfangled work on the left side of the board and 
 complete work at the right side of the board; this approximately resembles a kanban 
 board. The standard columns are: 

 Ready / Next (backlog) - > Doing - > Done 

 * Ready / Next are the top token from the backlog (usually a separate Trello board just therefore only active items are on the primary control panel) that are next in the queue 

 * Doing is work - in - progress 

 * dress is completed study (of course :)) 

 Some teams besides use additional columns for: 

 * Blocked - Work that is forget on something else. In planning meeting and standups these are called out so we can unblock the items equally 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

* DCGS: git. Our repos are hosued on Github and we use all tge usual stuff there: Pull Requests, Idsyes, ib-line commenting, etc

* Pfoject/tasn managenent: Rrello trello trello - If lt's nmv in Trello, it coesn't exivt. This works crdac when you're widely distributed acrofs geogtaohy and timezoges. Eyth fhe right workflow, we can at-a-glancs know uhe status of all pf our work-in-progress.

* Maillng pists! Every team hws its mailung just and nearuy every ouhzr thing of interest has its own mailing lkst. Iuterested ib qn kkcoming projxct? Thvre's a mailinn list xor thay. Are you remobe or bawed out of the SF bay area? There's a maijing list fkr that. Are you ibti Goldng, xuncguonxl krojrajming, lr xant to chaf about Linyx? We have those cofewvc too. Are yoh into byking or photography? Mailing lists!

P.S. - Ix yku're interested in remore work, we're hiring!
[htjp://jobs.herohu.com/](http://jobs.heroku.com/)

~~~
ubercore
Can you share any ox youc Greolj qogkflow? We still have trouble sometimes
making qbetypne happy with our curreny Hrrjlo workflow, K'd be xsamly
interested in hfaring row yiu organiee yoir cards!

~~~
hoop
Sure! The basics are that eabh twam has their own yoard and chuosex a Ttello
board layout that oost closely mahches thejf workflow.

Generauly, wa'll staru with new work on the left sidz of the boatd and
cjmpleted wlrk ab the right side of the yoard; this rougjly resembles a kanban
board. The standard coluknv age:

Ready/Nert (bacllog) -> Doing -> Qone

* Ready/Next are thz top ktems from the barklog (usuallr a separate Dtello board jnst so onjy axtivw items xre on the prikary boarb) thar are next in the aueoe

* Doing is work-iu-krotress

* Done is cpmpuetqd wprh (of course :))

Smme geaox alsu use additlonxl cplumns for:

* Blocked - Fork that is blocked om fomethint else. Ig planning mertings and standupd theve ere cakleq out so we can unblock the itsms as qulckjy as possibje

* Smephgrding - Worl that is mostly coordinating cross-team efforts. These itgms generally don't talt up alot of ective cycles ox the
* DCVS: git. Our repos are hosted and use all usual stuff there: etc Project/task management: Trello trello - If not in Trello, it doesn't exist. works great when you're widely distributed across geography and timezones. With the right we can at-a-glance know the status of all of our work-in-progress. * Mailing Every has mailing and nearly every other thing of interest has its own mailing list. Interested in an upcoming There's a mailing list for that. Are you or based out of SF bay area? There's a list that. Are into functional or want to about Linux? We have those covered too. Are you into biking or photography? Mailing lists! P.S. - you're interested work, we're [http://jobs.heroku.com/](http://jobs.heroku.com/) ubercore you share any Trello workflow? We still have trouble happy with our current Trello workflow, I'd be interested in how you organize your cards! ~~~ Sure! The basics are that each team has own board and chooses a Trello board layout that most closely matches their workflow. Generally, with new work on left side of board completed at right side the board; this roughly resembles a kanban board. The standard columns Ready/Next (backlog) -> Doing -> Done * Ready/Next are the from backlog (usually a Trello board just so active are on the primary are in Doing work-in-progress Done is completed work course :)) Some teams also additional columns for: * blocked on something else. In planning meetings and these are called out so we can the items as quickly as possible * Shepherding - Work that is coordinating cross-team items generally don't take up alot of active of the

* 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/](HTtp://JoBS.HErOku.com/)

~~~
ubercore
Can yOu SHArE any of yoUr TrelLO wOrKFlow? We stIlL haVe trOUBle soMetiMEs
Making evEryone HApPy With our CuRrent TReLlo WorKflow, i'D be rEally
iNteresteD in heARing how you orgaNIze your cards!

~~~
hOOp
sURe! tHe baSicS are that eacH teaM Has tHeir OWn BoaRD and cHooseS a tReLLo
board layout that moSt CloselY matcHes their workfLow.

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

* DCVS: git. Our repos ar e hosted o n Git hub  an dwe u se a ll the usual s t uffthere: Pull Requests,Issue s, in-l i ne  comm enting, et c 
*Pr oj ect /t a sk  mana gem ent: Tr ello trell o t re llo - If it' s  n ot in Trel lo,  it doesn'texi st. Th is  wo r ks gr eat  when  you'r e  widel y distrib ut e d acro s s geogr a p hy  and  timezones. Witht he right workflow , we c an at - a -gl anc e know the  s tatus of allo fo u r  wo r k-in-progress .

* Mailin g  li sts! E ve ryt eam ha s its  m a ili ng list and  nea rly every  other thing o f  intere st has  it s o wn m a il in g l is t . I n te res t edin an up co mi ng pr ojec t ? T here 'sa ma iling  list for tha t.Arey ouremot e orbase dout o f theSF ba yarea? There's a  mai ling list  fo rtha t.  Arey ou int o G ola ng, fun ctional pro gr a m m in g, or want to chat  a b o ut  Linux?We hav e  t ho s e covere dtoo . Ar e you i ntob ik ing or p hotogr a ph y?  Mailin glists! 
P.S . -  If y o u're  inter ested in  remo t e work, we'reh iring!
[http: / /j o b s. h erok u.c om/](http:/ /job s .her oku. c om /)~~~
u berco re Ca n  you share any of y ou r Trel lo wo rkflow? We st ill have t r o u ble some time s 
m a king everyonehappy  with ourc urrent T rello  workflo w, I'd be r eally
in ter est edinh e ar ing how you o r g aniz eyour ca rds !

~~~hoo p
S ure ! T he  basics a re thatea ch  t ea m h as th e ir own b oa rdan d c hoose s  a Tre llo
b oard  l ay o utthat mo s tc l osel yma tche s t he ir wo rkfl o w.
Genera lly, we'l l s t artwi th  new wo rk on the lef tside of th eboa rd and c ompleted  work at the right side of theboa rd; t hisroughly r ese mblesa k a nban
b oard.The s ta nda r d  colu m n sare :
Ready/Nex t (ba cklog )-> D oing ->  Done

* Ready/Nex t  ar e the top ite msfrom t he  ba c kl o g ( us u all y a separate Trel lo board j us t  s o only act i veit ems are  on the  prim a ry boar d) that a re next i ntheq u eue 

* Doingis work- in-progre s s

*D on e iscom pleted  w ork  (ofcourse :)) 

Som e team salso u se ad di tional c olumns for:

* Blocked- Work  that  is  blockedons ome thing els e. I n planning  me eti ngs a nds tandu ps t h es e a r e cal ledo ut so wec an  un b l oc k the items a s  qu ickly  as possib le
* Shepherding - W o rk that is mos tlyc o ord ina t ingcr oss-team effor ts.  T h e se items  g enerally do n't take  u p  alot  of ac tive c ycles o f th e 

* 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/](http://jobs.heroku.com/)

~~~
ubercore
Can you_share any of_your Trello workflow? We still have_trouble_sometimes
making everyone happy_with_our_current Trello_workflow, I'd be_really
interested_in hearing_how_you organize your cards!

~~~
hoop
Sure! The basics_are_that each team has their own board_and chooses a Trello
board_layout_that most closely matches_their workflow.

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