This week's book giveaway is in the OCPJP forum. We're giving away four copies of OCA/OCP Java SE 7 Programmer I & II Study Guide and have Kathy Sierra & Bert Bates on-line! See this thread for details.
Please do a SearchFirst (←click) as the definitions for these roles are readily found on the internet. Check out http://ScrumAlliance.org - then come back if you have more specific questions that you can't find answers for there. Thanks.
There is a very basic difference between a scrum master and product owner role. A scrum master is a facilitation role where as the product owner decides the features, communicates between clients and the scrum team and so forth. Quite simply put Product owner is a evolved role from an ordinary business management ( unnecessary if you ask me). However if you are looking for certifications i would suggest Scrum Master Certification over product owner. I did mine at www.scrumstudy.com , you can pick and choose what suits you best.
Ashley Morris wrote:What are the differences between Scrum Master and Product Owner?
The Product Owner represents the stakeholders and is the voice of the customer. He or she is accountable for ensuring that the team delivers value to the business. The Product Owner writes customer-centric items (typically user stories), prioritizes them, and adds them to the product backlog. Scrum teams should have one Product Owner, and while they may also be a member of the development team, it is recommended that this role not be combined with that of ScrumMaster.Scrum is facilitated by a ScrumMaster, who is accountable for removing impediments to the ability of the team to deliver the sprint goal/deliverables. The ScrumMaster is not the team leader, but acts as a buffer between the team and any distracting influences.
If you wish to enhance your knowledge on this, there are different certifications availabe like CSPO, CSM, SMC,PSM etc for Scrum Master and Product owner training. SCrumstudy.com, Scrum Alliance and Scrum.org are the Scrum Master certification providers.
Joined: Feb 01, 2013
@ Ashley Morris : I personally believe that we have a habit of complicating simple roles and rules to sound fancy. At the end of the day a product owner role is an evolution of a standard business analyst profile and hence the term product owner is unnecessary. The need of the role is to communicate the customers / stakeholders POV during the SDLC which till before this was being effectively done by a Business Analyst and hence i stand by what i said. However you are entitled to your own views so cheerio.
Sometimes a different name can influence how people think about the role. I know it may seem like a silly Jedi mind trick but many people really are influenced by the title. I'm not saying it's the same as changing the title from Janitor to Sanitation Engineer or Environmental Champion but the name "Product Owner" does give you a sense that the job is different from that of a "Business Analyst". To me, Product Owner conveys more authority to determine the direction and having more of a vested interest in the success of the project. "Business Analyst" is a bit detached, like someone outside looking in and not having as much of a vested interest in the project's success.
Joined: Feb 01, 2013
I think that is a very valid point, people do get influenced by the name now be it Scrum Master or Agile Expert or what ever it may be its the name that influences the response from people. Thanks for the insight, well put