Tuesday, 25 October 2016 14:39

Don’t Be An SDLC Extremist!

Written by
Rate this item
(1 Vote)
  • Do you follow process as a Fan or Fanatic?
  • Are you a Loyalist or a Zealot?
  • Are your suggestions Revolutionizing or Revolting?

In the 1980s Pepsi was tired of hearing that people prefer the taste of Coca-Cola over Pepsi. So they came up with the Pepsi Challenge. It was genius, and the results surprised more than those that were blindfolded. Characters in the ads always picked Pepsi, of course, but so did most people who tried it in real life—the sweeter taste was more appealing. So how did Coca-Cola keep their market share and brand loyalty? People continued to have positive feelings toward Cola-Cola, not because of the flavor of their soft drink or because they had a better product, but because they were loyal to the brand.

Related Article: 5 SDLC Project Management Pitfalls & How to Avoid Them

I wish there was a blind taste test for Software Development Lifecycle Methodologies, so people can see that SDLCs are not so different after all!

Diehard sports fans are the same way. When I was growing up the New Orleans Football Team was lovingly referred to as the ‘Aints’ as in “They AIN’T ever gonna make it to the Super Bowl.” So how did the Superdome get sold out Sunday after Sunday? Because Saints Fans were proud of their team whether they won or lost! No matter the projections, the odds, or the score a Saints fan would fight tooth and nail to defend their team.

I wish there was a super bowl for SDLC so we would know which SDLC has the most success.

Heaven’s Gate was an American UFO religious group from California. They believed that the earth was going to be “recycled” meaning wiped clean. They believed that the only way to survive was to leave the planet - that a spacecraft was trailing the comet Hale-Bopp. A large group of followers believed that their way onto this vessel was to leave their human bodies. Over 39 members killed themselves over a three day period, believing the whole time that they were ascending to the “Next Level.”

I am very glad that I do not yet know anyone who is willing to die for their SDLC beliefs!

Though they may not die for it, you probably know a few people who will fight for it. I know people who have argued themselves hoarse and even quit jobs because of their beliefs in a specific SDLC.

There is a psychological reason why people hold so dearly to their chosen methodology. Having a methodology in place reduces the team’s or person’s responsibility when things go wrong. When something bad happens, it is human nature to want to blame something. It is easier to be the victim of the process, than the person responsible for the failure. Identifying a breakdown in process as a source for blame provides closure for past problems, gives a sense of present control, and often eases fear of future failure.

Let’s look at it from a different angle.

  • Has any SDLC claimed that it works perfectly every time no matter what?
  • Do you think any SDLC would grow and be recognized simply by name if it was prone to continuous failure?

I am not advocating No Methodology. After all, a failure to plan is surely a plan to fail. What I am suggesting is that you think of an SDLC as a tool, there are many different kinds and it is up to you to have the right ones available and which one to use for the job at hand.

Read 2659 times
Deena Chadwick

Through more than 15 years of diverse experience as a Business Analyst in the complex and ever-changing digital marketing arena, Deena has built a solid reputation for delivering award-winning work. She has lead teams in scope definition, requirements management, architecture, design, build, deployment, and optimization. She is known for her ability to infuse innovative processes and techniques that facilitate strong collaboration between Technology and Creative teams.

Latest from Deena Chadwick

Comments  

0 # Omar Mughal 2016-10-26 13:24
I was once interviewed for a job managing packaged software implementation where the interviewer asked me which methodology my employer used. I explained it was really the same methodology that everyone else used to implement packaged software. I explained having worked for three large consulting firms I knew in reality there isn't really any difference between the consulting methodologies. I illustrated how it might work for his company and that a generic form would suffice for a generic ERP package. He didn't like it. Needless to say I wasn't hired...
Reply | Reply with quote | Quote
0 # Ajit 2016-10-27 00:44
There is some merit in that all methodologies have their pluses and minuses. Can we say for sure that ALL Agile projects are successful? The devil is in the people behind the implementation. The best methodology can give nightmares if the person implementing it is not competent. So in a way, i am saying the person is as important as the process!
Reply | Reply with quote | Quote

Add comment

Security code
Refresh

Search Articles

© ProjectTimes.com 2016

DC canada 250