Does partnering add people or costs to a project team?
A good partnership between the analysts, testers and developers actually reduces the total headcount and total time to market/cost to market by about 25-30%, and when you deliver you’re at or near zero defect. That’s because you’re minimizing scrap and rework—where we spend a huge portion of our effort. If you have people testing the requirements early you get those defects out, and the process we use leads pretty quickly to defect avoidance, not just defect detection. What are some examples of how analysts and testers partner? One of our key processes is ambiguity review. By looking for problems early in the requirements writing process, we find that after we’ve reviewed four or five use cases of a given analyst, we find the initial ambiguity rate drops by a factor of 95%. The analyst has gotten feedback about what was not overly clear in the prior use cases and they tend to clean that up. What’s more critical about this is we have studies that show if something is ambiguous in the re
Related Questions
- What is the best way of keeping your research useful for people outside the project team and convincing others (perhaps future funders?) of the usefulness of past work?
- Are technical skills or people skills more important to the team manager in a software development project?
- How do I get people to donate money for the overall project costs?
