Over the course of the last year, CURTIS Digital made the switch from being a primarily Waterfall software agency to an Agile one. If you are at all familiar with the software world, you likely know that each methodology has an almost cult-like following.
Many first time software buyers don’t know to consider software maintenance when planning their annual budgets. This shortsightedness is understandable—software is expensive to build and most dev shops don’t want to spend a lot of time on long tail cost curves.
An Agile Story can be defined as ” short, simple description of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system – Mike Cohn”
Most of the systems we develop here are CURTIS Digital now have a input pattern around Twitter handle inputs, e.g., @quotientaustin or @social_quotient .
Sometimes, users need a little help with inputting full, proper URLs. While working with Dibster, a local start-up MVP client, we ran in to a small usability problem while going through user testing. A lot of the users of the system are non-technical, and we kept finding that they were not inputting URLs the way that our system wanted.
Is the architect expected to know everything about construction or welding?
This topic of discussion has been passed around the Internet for quite a few years now and elicits passionate responses from both sides as well as every point of view somewhere in the middle.