Home > Agile, Process Life Cycle, Project Management, Quality, Quality Management System, Review, Testing > How SCRUM Methodology is different from the traditional methodology?

How SCRUM Methodology is different from the traditional methodology?

This is most frequent question we hear in the arena of SEPG. Will try to address it in the forum to the best and appreciate the viewer’s response.

As part of the engineering position SCRUM is no different from normal traditional methodology of SDLC (Iterative method), but the way the project management is implemented in the SCRUM is interesting and appreciable.

In the traditional methodology the managerial position is done by managers, whereas is in SCRUM it is responsibility of SCRUM team to do that. For example in traditional, estimation is done by head or manager where as in SCRUM it is done by team in conjunction with product owner and SCRUM Master during the SPRINT Planning Meeting.

Assumptions, Constraints and dependencies (ACD) are documented by manager but the implementation rate is very low, whereas it is plugged or enable in the SCRUM through the channel of Daily standup meeting.

Communication Plan / Escalation plan is documented in the traditional methodology but the usage of the same is minimal whereas it is implemented effectively through daily standup meeting here in SCRUM.

Sprint Review meeting is the channel through which the acceptance criteria for the product is met in the SCRUM methodology. Also it’s the responsibility of the SCRUM team to demonstrate the product to the product owner and prove that things are done according to the definition of Done (DOD). We mean to say SCRUM team defines the boundary of acceptance criteria during the Sprint Planning, whereas in the traditional methodology no where the team which is going to develop the product involved to define the criteria for acceptance.

Changes during the SCRUM are not allowed is the Thumb rule in SCRUM.

Configuration Management should be take care during the Zero sprinting or during the Sprint Planning a line item, need to be addressed.

Lessons learned during the project are not documented in formal or informal manner in the traditional whereas here it is reported through retrospective meeting in SCRUM.

Implementation of the Risk Management in the SCRUM will post later.

Advertisements
  1. July 13, 2013 at 4:53 am

    Hi there just wanted to give you a quick heads up. The words in your post seem to be running off the screen in Opera.
    I’m not sure if this is a formatting issue or something to do with web browser compatibility but I figured I’d post to let you know.
    The layout look great though! Hope you get the problem fixed
    soon. Thanks

  2. January 8, 2014 at 3:21 pm

    Hello there, I discovered your blog via Google while looking for a related topic,
    your website got here up, it appears to be like great.

    I have bookmarked it in my google bookmarks.
    Hello there, just turned into aware of your blog thru Google, and found that it is truly informative.

    I’m gonna watch out for brussels. I will be grateful in case you continue this in future.
    A lot of people will likely be benefited out of your writing.
    Cheers!

  3. Shela
    January 25, 2015 at 5:40 am

    Thanks for one’s marvelous posting! I definitely enjoyed reading it, you happen to be a great
    author. I will remember to bookmark your blog and will come back
    very soon. I want to encourage one to continue your great work, have a nice morning!

  1. No trackbacks yet.

Leave a Reply

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

WordPress.com Logo

You are commenting using your WordPress.com 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: