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.
Software-as-a-service is what the great majority of our users want, but we're getting a steady trickle of requests to run Screenful on customer premises, too. Some companies just prefer to keep their sensitive data behind a firewall and host their own tools.
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.
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.