As part of our ongoing architecture redesign, we've also had to redo all of the individual dashboard screens. That has been a lot of work but It also gave us an opportunity to make improvements based on the learning we've gained along the way.
Tracking your lead and cycle times help you to understand how quickly your cards move across your Trello board. If your cards represent user stories, then it tells you how quickly you can deliver new features to the users of your product, and allows you to answer questions like
How long will it take to have a feature delivered to end users after it was added to backlog?
We’ve been busy with redesigning our analytics backend and now we’re ready to introduce some filtering capabilities that you have been asking for a while already. With the new filtering feature, you can get answers to questions like:
We have some good news for you. We’ve added a new Time in State chart that allows you to break down your cycle time by workflow state and see how it develops over time. Wanna know how long your review step takes? Now you have the answer.
Workflow is the process that a company uses to get things done. In software development, it’s a process that creates software, from early specifications all the way down to production deployment. While it is not a secret that software development is often chaotic, there are ways to make it more predictable. Or at least a bit more predictable as it used to be, by applying some small incremental improvements.
Trello made a big move by opening the Power-Ups (i.e. third party extensions) for all of their 16M users. It means that the Screenful Power-Up is now available for all Trello users, not just for those using Trello Business Class.
The idea of a user story is simple: rather than writing extensive documentation about the features we’d like to build, why not just write them as stories instead? And not just any stories but stories of real users using the product. Not with a lot of technical details but just in plain language that a user might use. Hence the name user stories.
One of the biggest changes that a company faces when transitioning to the agile mindset, is the empowerment of the team. For some, it can come as a surprise that there may be less people telling how to do things than previously. There are only as many as the team needs. That’s because the team is self-organising and it will let management know if external resources are needed.
Everyone gets pleasure from ticking tasks off of the todo-list, right? At least, I do. But it’s no longer fun when you feel like you’re drowning in work with too many things to do, or feel like you’re trying to juggle too many balls at once. That’s what kills motivation and creates unhappy employees. But it doesn’t have to be that way – more often than not, situations like this can be avoided!
In late 2014 after opening up our service to beta users we were faced with a dilemma that I suspect is pretty common to many startups. Automatic functional testing is almost a requirement to run a modern Agile software process. But building those capabilities takes time and money, both of which are in short supply at a typical software startup.