arrow-left arrow-right brightness-2 chevron-left chevron-right circle-half-full dots-horizontal facebook-box facebook loader magnify menu-down RSS star Twitter twitter GitHub white-balance-sunny window-close
Switching to Trello
1 min read

Switching to Trello

This is an old post and doesn't necessarily reflect my current thinking on a topic, and some links or images may not work. The text is preserved here for posterity.

One of the things I'm noticing about running my Micro ISV is that I have to constantly change my mind :)

Until today I had been using AgileZen to manage the Octopus backlog. There is also a discussion board on Tender for people to post suggestions/ideas on improving Octopus.

AgileZen is great, but one of the downsides was that a suggestion would get added to the board, but people could never see how it was progressing or where it sat in the queue. There was also no voting, so I couldn't gauge how many people thought a suggestion was good.

Today I switched to Trello, which is very similar to AgileZen but also allows public visibility. I'm hoping this will create much more transparency in how Octopus develops:

View the Octopus Trello

If you create an account on Trello (or use your Google account) you can:

  • Vote for suggestions/features you like
  • Add comments to items
  • See how a suggestion progresses

Trello doesn't yet allow you to create new suggestions, so they should still be posted to the Octopus discussion board. I'll then add the suggestion to Trello so you can see how it progresses.

Paul Stovell's Blog

Hello, I'm Paul Stovell

I'm a Brisbane-based software developer, and founder of Octopus Deploy, a DevOps automation software company. This is my personal blog where I write about my journey with Octopus and software development.

I write new blog posts about once a month. Subscribe and I'll send you an email when I publish something new.