TeamGrowth- The Art of working together

“Salon’s Scott Rosenberg explains why even small-scale programming projects can take years to complete, one programmer is often better than two, and the meaning of ‘Rosenberg’s Law.’ After almost 50 years, the state of the art is still pretty darn bad. Scott point out you’re trying to do something that has already been done.

Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Transcendent Software sets out to understand why, through the story of one software project — Mitch Kapor’s Chandler, an ambitious, open-source effort to rethink the world of e-mail and scheduling.

Robustness testing is a part of the corroboration process which consists in testing the performance of a system accomplishment under exceptional execution conditions in order to check if it still fulfills several robustness requirements.

* Look forward to potential interfacing problem.

* Test all information coming from different elements of the system.

* Conduct a series of test that replicate the potential errors at the software interface.

* Make sure that the system elements have been properly integrated and perform allocated functions.

* Record the results of tests.

* Participate in design and system test to get ensure that software is adequately tested.

Robustness testing makes sure that the system operates correctly in the presence of exceptional inputs or stressful environmental conditions

Some projects lengthen unnecessary a software development schedule considering its requirement than they actually need resultant the performance requirement become more critical and hence it lengthen further the original software schedule time frame. The Users tend to be more interested in development, launching and marketing particular software rather than interested in complex features, these complex features unreasonably lengthen a development schedule.

Even though the developer are successful at avoiding requirements, the average project experience about a 25 percent change in requirement over its life time. Such a change can produce at least a 25 percent addition to the software schedule.

Some software developers are attracted by new technology & new features and they want to make changes during software development process without considering at the necessity of the new technology in their product. Such effort require to implement design features, test document, testing schedule and other support features that eventually lengthens the estimated project schedule. Rememeber, the customers want solutions specific to their actual requirement and so you should aware of their real need and solve the important problem and so on manage work to get their high-pressure development schedules under control.

If a developer focus mainly on user needs up-front recording user feedback, they can shorten the time frame and undergo on rapid development phase. It can also partially not going to affect the overall costs especially to the customers those having limited budget.