Deprecated Garbage Collections – Kenny Lee Chee Wei

A truckload of garbage by Kenny Lee Chee Wei

Time to abandon the Waterfall SDLC and/or Business Analysts?

with one comment

Part 1 – Abandon Waterfall SDLC?

I feel gone are the days whereby software companies should force customers to sign off system requirements.

Reason? There is no guarantee that the requirements gathered during the “System Analysis” phase of the Waterfall cycle is fully complete. So if you’re forcing the customer to sign off and get ready to accept something that they might not fully embrace after delivering, then there might be a problem late on.

Instead of contract disputes in the end, why not have constant customer collarboration/communication throught the lifecycle through an agile development methodology like Extreme Programming or Scrum? Customer should be as involved with the success of the project as the project development team.

Your company is foolish not to tap on the customer’s feedback during the project development. At the end of the day, it’s the customer who mark the acceptance tests.

Part 2- Abandon Business Analysts?

This one is abit controversial. Did i meant let the developers take over the job of business analysts? Possible, why not? Developers are supposed to be smarter than BAs, although BAs generally have better communication skills. Generally developers create prototypes anyway, so if there is any mis-communication, changes can be done swiftly.

The key problem is having good communication skills alone does not allow a BA to analyst customer IT problems and churn out technical user requirements/specifications.

It is easier to find a developer with decent communication skills than a sound business analyst with development background or is IT-savvy. And if you ever find one, do whatever it takes to keep him/her. My working experience also made me believe that BAs should come from a technical background. It improves the specs they write, trust me.

Even though generally managers prefer decision-biding employees rather than employees whom speak up and challenge decisions, you can be sure you’ll get more of those if you have such developers. “Can’t these developers just write the damn code” they thought. I’m one of those. CTOs doesn’t scare me 1 bit.

I generally prefer to gather requirements directly from customers. If information gets filtered by BAs, 100% customer requirement accuracy might just be left 80%. If specifications are written incorrectly, you are left with maybe 60%.

XP suggests that a customer be placed at the development site, Thoughtworks practises placing the development team within the customer’s site, with the latter sounding more practical to me. Simply having a key customer decision maker’s MSN account would be fine for me though.

Written by kennii

September 2, 2007 at 12:10 pm

Posted in Software Dev

One Response

Subscribe to comments with RSS.

  1. poda vennai


    October 8, 2009 at 7:19 am

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: