Ten years ago, when was an R and Team Leader with VISA, we had a very structured software development procedure every time a new module or feature needed to be developed, we would go through the exact same process – Marketing would create an MRD Marketing Requirements Document. Commonly a 10-20 pages document, outlining what marketing wants to view, with a couple of sketches of how they want the feature to work. My job as the R and Team Leader was going to review the record with the advertising department’s product manager and subsequently create a new record titled FRS Functional Requirement Specification. The FRS explained the technical particulars and execution to provide the desired functionality.
Would meet with Each and every engineer, review the FRS and help them compose still another record that describes the device demand spec and unit testing. While development was in progress, our in-house QA Quality Assurance department would prepare two sets of files for white box and black box testing. We would launch a new Construct every 3 weeks and the launch procedure involved several different files and steps, all carefully designed to minimize errors. Everybody aside of the QA people hated this system. For some reason QA loved it. Said it makes their job easier. But since it took so long to receive a brand new feature fully developed, tested and deployed, often we would find ourselves deploying a feature/functionality that is no longer required in domycoding.com.
We missed the window of opportunity, the customer went off or Marketing changed their mind. Now everything has changed. Time to market Time to money Increasing rate of change in the online world all gave birth to Web 2.0. Ajax. Along with also a new software development methodology code called Extreme Programming. At Software Projects we no longer compose 5 Documents to acquire a brand new feature deployed. We no longer wait for black box and white box green-light from QA before going live. And we no longer miss the window of opportunity. Extreme Programming is working so well for us we developed a shocking5 percent credit for each and every day we are late penalty system when dealing with customers. Yikes my old boss would freak out back in the days of 1997 where each project has been destined to be late and incorporating additional programmers to an already late project only made it a much bigger tragedy.