Three steps to predictable software delivery - part 1 - Preparing your work items

Rapid innovation and being first to market is something we all strive for. However, measuring the performance of a development team is anything but easy. No single measure is enough. If you only track velocity it quickly leads to decreased quality. Although your customer would like you to deliver quality work fast but at low cost, the age old truth is that from those three, you can only pick two.

Working in sprints with Trello just got easier!

Scrum is one of the more popular frameworks for implementing agile. It’s also the flavour that teams tend to pick first when they want to get started with Agile methodologies.

With scrum, the product is built in a series of fixed-length iterations called sprints that give teams a goal of delivering new software capability every 2-4 weeks. And it's no longer just software teams that are using Scrum, as it had spread to other business functions such as marketing, which can also benefit from Scrum's ability to address complexity and ambiguity. 

Agile & Lean Metrics: Cycle Time

Great teams constantly improve the way they work in order to deliver high quality software. This series of blog posts will help you do just that. We'll introduce a set of Key Performance Indicators (KPI) that you can use as a baseline for your continuous improvement efforts. We think that a good indicator is easy to understand, and it should be leading rather than lagging i.e it should predict successful software development.

Experiences from launching in Product Hunt

Three weeks ago we officially launched our Agile team dashboard on Product Huntafter two years in the making. We knew PH is an active community of early adopters but didn’t have any experience of it and therefore did not really know what to expect.

This post is to share our experiences for those who are in the same situation, with some practical tips on how to make most out of you PH submission.