How We Started Releasing Features Twice As Fast (Case Study)


When businesses rely on your app for their day-to-day work, you have to be agile enough to quickly address their needs. If you don’t, others definitely will. In the unforgiving world of SaaS, delaying a critical feature (or rushing a bug-ridden piece of code) will mean losing clients. A solid agile workflow can make all the difference.
We’re the team behind Active Collab, a project-management app with an ever-growing set of features and a sizeable user base. This means that even the smallest change in functionality will affect a large number of people. Therefore, the development process needs to run smoothly and up to a standard, with delays reduced to a bare minimum.
The post How We Started Releasing Features Twice As Fast (Case Study) appeared first on Smashing Magazine.
From our sponsors: How We Started Releasing Features Twice As Fast (Case Study)