- serious about rigorously testing the system soon.
- Achieving Venus/Mars Harmony: User acceptance testing is a developer term, and often developers have a condescending way of hinting that its contents should be obvious to anyone with any business savvy. From the IT customer viewpoint, it would make sense to work together to define what needs to go into a "good" user acceptance test plan, so that the IT users could then develop one. While all of the permutations and testing combinations might seem obvious to a seasoned developer, the occasional IT customer doesn't know the terms or the test plan development rules by heart. Working together without acronyms blocking the communication will go a long way to having successful testing experiences.
- Changes during the Project
- Venus Perspective: In business, change is the natural state, and we adapt to it as part of our jobs. As soon as we realize that we've missed something in the requirements for the software, we let the developers know. It is frustrating that they often are less than appreciative and even blame us for not telling them about the changes sooner. It seems like the further we get into the project, the more resistant the developers get about making changes, yet you would think that they would want to deliver software that truly meets our needs as much as possible.
- Mars Perspective: Some of the changes introduced late in a project could have been avoided altogether if the IT customers would have taken the time on requirements in the first place. The cost to us to make these changes now is substantial. Other (legitimate) changes sometimes come to us way too late-long after coding has begun-and then we might not be able to incorporate them and still stay on schedule. You'd think that the IT customers would know how scope change impacts us, but it never seems to improve.
- Achieving Venus/Mars Harmony: Again, the solution to the conflict arising over change management lies in clear communication. Contrary to popular belief, many IT customers do not understand the impact of change that is introduced late in a project. Like the frustrated construction manager whose customer insists on adding a second kitchen that was missing from a floor plan, developers get frustrated when IT customers don't participate in the requirements phase, but later demand that changes be made after construction (coding) has commenced. In many IT shops, an early discussion between IT customers and the project team about the exponential cost of change (a change costs $1 to make at the requirements phase, $10 to change it after design, and $100 to change it after coding) has illuminated the issues concerning change late in the lifecycle. Understanding that when a change is introduced is as important as the change itself can lead to improved software quality and better relationships all around.
These examples illustrate common occurrences on software projects and suggest preventive actions to reduce their impact. Without a solid relationship, the partnership of developers and IT customers can deteriorate into "sides," which causes software products to miss the intended mark. In the universe of software projects, if Mars and Venus are out of alignment, the entire solar system is disrupted.