sxdemetriusu的部落格

Ten age ago, when I was an R&D Team Leader with VISA, we had a incredibly organized computer code progress process!

Everytime a new module or element had to be developed, we would go done this self route -

Marketing would build an MRD (Marketing Requirements Document). Typically a 10-20 pages document, outlining what merchandising desires to see, with a few sketches of how they would like-minded the property to work.

My job as the R&D Team Leader was to assessment the written material near the marketing department\\'s trade goods superintendent and in circle initiate a new written material styled FRS (Functional Requirement Specification). The FRS delineate the precise account and finishing to mouth the in demand functionality.

I would get together next to all lonesome engineer, second look the FRS and aid them jot yet other piece of writing that describes the definite quantity measurement description and unit experiment. While development was in progress, our in-house QA (Quality Assurance) section would ready two sets of documents for whitebox and blackbox carrying out tests.

We would unbind a new put up all 3 months and the escape system mixed up several else documents and steps, all with care designed to minimise mistakes.

Everybody (aside of the QA those) despicable this group. For quite a few reason QA loved it. Said it makes their job easier. But because it took so long-range to get a new characteristic full developed, proven and deployed, habitually we would discovery ourselves deploying a element/functionality that is no longer enforced. We incomprehensible the frame of opportunity, the patron went distant or Marketing changed their knowledge.

This was all vertebrae in 1997.

Today everything has changed. Time to marketplace. Time to burial. Increasing speediness of silver in the online world all gave kickoff to Web 2.0. Ajax. And a new software arousing epistemology code named Extreme Programming.

At we no long keep up a correspondence 5 documents to get a new feature deployed. We no long suspension for blackbox and whitebox green-light from QA before active in performance. And we no longer missy the skylight of chance.

Extreme Programming is functional so all right for us that we came up beside a indecent \\"5% commendation for every sui generis day we\\'re late\\" penalty grouping when treatment beside clients. Yikes! My old company would mutant out support in the years of 1997 where on earth all separate work was orientated to be past due and adding together optional developers to an just delayed task retributive ready-made it an even larger blow.

So what is all about?

In concise it method committal to writing at the acceleration of rumination. Whenever thing wishes to get done, we happening it fluff to the littlest units allegeable (OOP), use extant objects whenever possible, fast part try-out and on to the crop restaurant attendant.

A lone written material describes what requests to be done and the tough grind is wrecked behind to various engineer, each accountable on writing and deploying their element of the jut out over.

Initially this sounds resembling devastation or a formula for disaster, even so past the art of revolutionary planning is mastered, the end outcome is swift web 2.0 applications launched in weeks as opposed to months/years.

Extreme Programming is active channel memo near the customer, it\\'s just about instant changes near instant production to manufacture environment. It\\'s almost just deed material possession done, next to no further officialdom and no auxiliary stairway.

For us - we stay alive and breathe XP and we\\'ll never go hindmost.