How do you rate SCRUM as a project management tool in terms of effect and user friendliness?

Scrum is an agile methodology that can be applied to nearly any project; however, the Scrum methodology is most commonly used in software development. The Scrum process is suited for projects with rapidly changing or highly emergent requirements. Scrum software development progresses via a series of iterations called sprints, which last from one to four weeks. The Scrum model suggests each sprint begins with a brief planning meeting and concludes with a review. These are the basics of Scrum project management.

Frankly i don't know too much about SCRUM since i am not specialized in IT industry, i even don't believe that agile principles suits construction industry as it do with IT, however, i'll take the chance to know more about it here maybe we can come out with something.

My point is if we cannot widely apply agile and scrum in overall project management processes (as in lean project management) , why we consider it a methodology rather than call it technique or a tool.      

I am receiving some good responses providing over view but not really answering the question about how you rate it and more importantly how user friendly it is as a tool and process?

 

Scrum is a proven and widely adopted method for achieving software agility. By working in short sprints, this iterative cycle can be repeated until enough work items have been completed, the budget is depleted or a deadline arrives. Project impetus is maintained, and when the project ends Scrum ensures that the most valuable work has been completed.

This contrasts sharply to the more traditional waterfall style approach that fixes the project scope upfront, requiring the extensive creation of requirements, analysis and design documentation before development can get started. Delays and budget overruns are common, and the failure to prioritize the feature set often results in low quality products that are overloaded with features that the customer/user does not actually require.

I'm a big fan of Scrum.  Its certainly my preferred method. Effectiveness - It solves these3 critical problems for teams: 1.  Supply/Demand - All software engineering organizations have way more demand than supply.  Showing your velocity allows you to set expectations about how much can get done. 2. Predictability - Once you have velocity, you can better estimate how fast projects can get done.  Visualize a Jira Epic or Version burndown chart. 3. Sustainable Pace -- Remember the days of "death marches" these disappear with Agile/Scrum. User Friendliness Scrum's pretty easy to grok.  Read the Scrum guide.  Distribute it in your org.  Stick to it (for the most part).  Don't vary much. "Points" can be a little hard for teams to get.  I've landed on seeding its initial value to help teams "bootstrap" -->1 Point =1 Ideal Days.  Most engineers understand "ideal days".  Then I add in more complex concepts -- points = size not effort (although effort is a common proxy for "size"), should be relative etc.

Let me try explain SCRUM with reference with waterfall model so that our friends from construction industry would have more clear idea about it.

Waterfall model is simple and oldest methodology where analysis and requirements are finalized before initiating development work, while work is done as per plan, the problem with waterfall model is lack of change management as client visibility in this methodology is low to null.

SCRUM or iterative or adaptive methodology is developed to increase clients participation in development work, in scrum methodology project is divided into multiple releases based on the nature of project, these releases are called Sprints, these sprints are delivered from 2 to 8 week spam.

Sprints may contains various related tasks that can not change during development phase.

Analysis, planning, development and testing phases are done separately for each sprint with consultation of client, we call it JAD session (Joint Application Development) where client participate in analysis and requirement gathering. since client is participation is high in this methodology mostly failure chances are less as client usually validate the sprint for release.

We can not compare both WATERFALL or SCRUM methodologies where  each have their own advantage or disadvantages.

Since client participation is too high, lots of change requests observed in SCRUM methodology which sometime causes problem in development.

SCRUM is too complex in implementation as compare to waterfall.

Waterfall methodology should not be used for long term projects as this might result in loss of client interest and focus SCRUM can be used for long term projects because client interaction is high.

Lets say if Microsoft asked their  window users to participate in development of new version, would that version ever complete on time, never because of huge number of stakeholders.

So I wouldn't suppressed SCRUM over waterfall as both methods are effective based on the nature of projects.

In my opinion scrum methodology is too good as project management tool, because scrum decreases the risk for project failure. because we are continuously getting feedback from client So at the end client get what he wants.if our project module is not according to the client demand, he will tell us with in 15 to 30 days, so this loss can be bearable instead of the loss that we get after 2 years when we come to know that our project is not up-to the client expectations as in typical water fall SDLC.Thats why i vote for agile scrum and implement it as a project management tool

 Scrum is a process framework that has been used to manage complex product development since the earlys. Scrum is not a process or a technique for building products; rather, it is a framework within which you can employ various processes and techniques. Scrum makes clear the relative efficacy of your product management and development practices so that you can improve.For more information please study scrum guide that you can find it internet.