This article is designed to provide specific steps for understanding your development effectiveness. Getting this right will help move your software development group toward being a true business partner, if it is not already.
The tag-line for Feature Injection is "As we pull value from a system, we inject features." So before we can start, we need to identify the business value. But how do we do that? This edition also expands on the 20/20 vision conference concept.
Vinay Krishna explains why agile development includes testing and coding concurrently, which is also what test-driven development emphasizes. The transformation from coder to developer to tester is needed in all agile software development projects.
This article discusses how testing teams can improve their test coverage and better communicate with technical support to uncover issues earlier than during product implementation. This kind of collaborative work can stop most defects from getting into production.
Beware of the hidden sirens in your rewrite project. They will sing the words you want to hear--that the project is easy to complete. Don't be fooled: Sirens are mythological, but the lure of rewrite projects can be quite real. Rewrite may seem a simple task, but it isn't until you're deep into it that you'll start to realize the true nature of the project. In this article, James Shore offers some words of wisdom (and warning) to help guide your rewrite project in the right direction.
We are leaving the "last responsible moment" for a while. This month we start a discussion of Feature Injection, an analysis process based on real options and Kolb's circle of learning. The first episode ( of five ) introduces the "Information Arrival Processes.
Peter Schuh writes that it is not a good thing that the use of the term refactoring has grown so common, which makes him cringe every time he hears a business person say the word. Refactoring is meant to be one skill of many that is second-nature to a journeyman programmer.
Getting all of the necessary people together to define what "done" means in a software development project will be difficult. Facilitating such a task will probably be a challenge, but there is nothing like working in an organization that works like a well-oiled machine, where everyone knows what is expected of him or her and just naturally does it.
This article is dedicated to telling you how good developing software can be. Austin Hastings describes many software development practices working together, some of which you don't have. If you like an idea you see here, implement it. After your first implementation steps, you can return here to find yet another idea to implement.