What are the differences between Scrum and Traditional Project Management Method?

Although there are similarities in Scrum and traditional project management methods with regard to definition of ‘quality’ (i.e., the ability of the product to meet the agreed Acceptance Criteria and achieve the business value expected by the customer), differences exist in terms of how the approaches address the implementation and achievement of the required quality levels.

In traditional project management methods, the users clarify their expectations; the Project Manager defines those expectations in measurable terms and gains agreement from the users. After detailed planning, the project team develops the product over an agreed period of time. If any of the agreed criteria are to be changed, changes can happen only through a formal change management system where impact of changes is estimated and the Project Manager gets approval from all relevant stakeholders.
In Scrum, however, the Product Owner collaborates with the Scrum Team and defines the Acceptance Criteria for the User Stories related to the product to be delivered. The Scrum Team then develops the product in a series of short iterations called Sprints. The Product Owner can make changes to the requirements to keep pace with the user needs and these changes can be addressed by the Scrum Team either by terminating the current Sprint or including the adjusted requirements in the next Sprint as each Sprint is of very short duration (i.e., one to six weeks).
One of the major advantages of Scrum is the emphasis on creating potentially shippable deliverables at the end of each Sprint cycle, instead of at the end of the entire project. So, the Product Owner and customers constantly inspect, approve and accept deliverables after each Sprint. Also, even if a Scrum project is terminated early, there is some value created prior to termination through the deliverables created in individual Sprints.

To know more click on: http://www.scrumstudy.com/blog/

Is SBOK Guide relevant only for Scrum Master Role?

Professionals who want to implement Scrum in their organizations, usually ask – ‘What are the recommended books if we had a team of developers who are usually new to Agile and Scrum?’ That is, there are currently lot of books in the market that target only a specific audience (e.g., a Scrum Master) and do not consider the interactions required between different Scrum roles to make Scrum work effectively. Which book or guide would you give them to improve their knowledge about Scrum and make them understand the tasks they should be doing in a Scrum project?
This is tricky question to answer as it is quite generic. However, A Guide to Scrum Body of Knowledge by SCRUMstudy, provides Scrum guidelines and knowledge relevant for each of the core Scrum roles – Product Owner, Scrum Master, and the Scrum Team. If you don’t have time to read the complete book, you can read the sections relevant to your role as per the details in the ‘Roles Guide’ topic mentioned in each chapter.
The SBOK™ Guide was developed for organizations and professionals who want to implement Scrum or those already doing so who want to make improvements to their Scrum processes. It is intended for use as a reference and knowledge guide by both experienced Scrum and other product or service development practitioners, as well as by persons with no prior experience or knowledge of Scrum or any other project delivery methodology.
The SBOK™ Guide is especially valuable:

• to Scrum Core Team members including:
  • Product Owners who want to fully understand the Scrum framework and particularly the customer or stakeholder-related concerns involving business justification, quality, change, and risk aspects associated with Scrum projects;
  • Scrum Masters who want to learn their specific role in overseeing the application of the Scrum framework to Scrum projects;
  • Scrum Team members who want to better understand Scrum processes and the associated tools that may be used to create the project’s product or service.
  • as a comprehensive guide for Scrum practitioners working on Scrum projects in any organization or industry;
  • as a reference source for anyone interacting with the Scrum Core Team, including but not limited to the Portfolio Product Owner, Portfolio Scrum Master, Program Product Owner, Program Scrum Master, Scrum Guidance Body, and Stakeholders (i.e., sponsor, customer, and users);
  • as a handbook for any person who has no prior experience or knowledge of Scrum but wants to learn more about the subject.

The first chapter of the SBOK™ Guide and a free introductory course about Scrum is available at SCRUMstudy. Try these resources and if you find it relevant, you can order a physical copy of SBOK^TM Guide.

 To know more click on : http://www.scrumstudy.com/blog/is-sbok-guide-relevant-only-for-scrum-master-role/