Ensure that development output happens frequently … at the expense of formality and even some bugs.
In any organization, but especially at a small, lean organization, output matters more than almost anything else. This is our individual, internal measure of efficiency. In the Agile software development language, this correlates with a high “velocity” of software feature output. Without requiring a casual reader to understand the nuances of Agile software development, there are some very relevant by-products of this concept that are easily understood. For example, continual output fosters frequent input from users. This input, in the form of usability testing, customer feedback, and analysis of software usage trends (analytics), can be integrated into all future product plans. When this occurs, the benefit is immediate. Short feature release cycles are supported by tangible, real-life data on what has previously been successful. The voice of the customer is reflected in subsequent output almost as quickly as it is received. When this occurs, even the occasional bug or issue is forgotten in the face of how radically the software advances, and how revolutionary the features become for all customers. Oh, and even the bugs are corrected quickly.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment