Scrum Words and My Understanding

Scrum Master:

• A scrum master is the facilitator for a product development team that uses scrum
• The Scrum Master is responsible for the success of scrum.
• Scrum Master works with customers and management to identify and institute a product owner
• Works with management team to form scrum teams
• He works with Scrum teams and product owner to create a product backlog for the sprint. 
• He is responsible for conducting daily scrums, responsible for impediments are removed and decisions are promptly made, scrum master manages the process for how information is exchanged. 
• He is responsible for working with management to gauge progress and reduce backlog.

Product Owner:

• Product Owner is responsible for managing and controlling the product backlog.
• In Scrum, the Product Owner is the one person ultimately responsible for the return on investment (ROI) of the product development effort. The Product Owner influences the development effort by conveying his vision to the team(s) and prioritizing the Product Backlog.
• Product Owner is one person maintains the product backlog and his responsible that product backlog is visible to everyone.
• The Product owner is one person, not a committee. Without a single product owner, result will be floundering, spin, contention and frustration
• For product owner to succeed, everyone in the organization has to respect his/her decisions. No one is allowed to tell the scrum teams to work from a different set of priorities.
• All the decisions that the product owner makes are highly visible, as they are reflected in the prioritization of the product backlog
• This visibility requires the product owner to do his/her best and makes the role of the product owner both a demanding and a rewarding one.

Product Backlog:

• Product Backlog is an evolving, prioritized Queue of business and technical functionality that needs to be developed into a system.
• Scrum Master is responsible for employing the scrum process to build a system or product, the requirements are listed in product backlog
• The Product Backlog represents everything that anyone interested in the product/ process has thought is needed or would be a good idea in the product
• It is a list of all features, functions, technologies, enhancements and bug fixes that constitute the changes that will be made to the product for future releases.
• Anything that represents work to be done on the product is included in product backlog.
• eg: Improve Scalability of the product 
• Product Backlog can originate from any sources
• Product Marketing generates features and functions
• Sales team
• Engineering team
• Customer Support team etc.,
• Product Backlog is sorted in order of priority

Estimation Backlog Effort:

• As backlog is vreated, the product owner works with others to stimate how long it will take to develop. To reach the estimate he or she talks to developers/ technical writers/ quality control staff and other people who understands the product and technology
• This estimate includes the time it takes to perform all of the requisite architectue, design, construction and testing
• The estimate will be as accurate as the product owner and team are at estimating; this means that the accuracy may vary wildly untill the team becomes experienced at estimating. Since the team will build the backlog into code, their estimate is the best available.
• Estimating is an iterative process estimates change as more information emerges about the backlog item and item becomes better understand.
• The product backlog estimate is not bindling on the scrum team. The estimate doesn't mean. "this is how much time there is to build this functionality and no more".
• The estimate is a starting point, a best guess, from which the sprint can be emperically constructed and managed.
• The scrum team selects the amount of product backlog that it belives it can handle in a sprint based on these estimates. If the product owner hasn't worked with the team to create realistic estimates, the amount of product backlog selected may differ significantly from expectations.
• Starting with the top priority backlog, the product owner develops estimates for each item, As the project gets underway, more will be known about available components, the utility of development tools and the capability of the team, the estimates can be revised.