Skip to main content

10 things a Product owner must do

In a Scrum team, a Product owner is the person who has the vision about the product and is responsible for maximising value of the product and the Scrum team.Product owner is always one person and not a group of people.

Here is a list of 10 things a efficient Product Owner must do....

  1. Have a clear vision about the product and communicates the same to the stakeholder and Development team
  2. Creates, owns and keeps Product Backlog up to date. The Product Backlog should be ordered to best achieve goals.
  3. Express Product Backlog items clearly with acceptance criteria
  4. Ensure the Development team have a clear understanding about the Product Backlog items
  5. Attend the key sprint events like Sprint Planning, Scrum stand-up, Sprint Review and Retrospective
  6. Always available for the Development team queries
  7. Liaise with the stakeholders and build a strong relation with stakeholders so that they respect his/her decisions
  8. Agree a clear definition of Done with the development team
  9. Decides on the release date
  10. Represents stakeholders/users/clients.
Ideally a Product Owner should be responsible for only one Product at a time but in real world the same person may be managing multiple products. 

Who can be Product Owner?

Any person who has a clear understanding about the business and the product can be a Product Owner. In some organisations, Business Analyst act as Product Owners. In some organisations, Product Managers become Product Owners. Recently some organisations have started recruiting dedicated Product Owners. These days there are courses for becoming Certified Product Owners.

Labels:

Comments

Post a Comment

Popular posts from this blog

Why there is semicolon at the start of a JavaScript function?

Very often while reviewing the code for my team, I will come across a semicolon at the start of JavaScript function as show below ; (function () { 'use strict'; ...and I often wondered what purpose it served. Guess what. It is an insurance to make sure your script works fine when all other scripts are merged together;  The leading ; in front of immediately-invoked function expressions (iffe) is there to prevent errors when appending the file during concatenation to a file containing an expression not properly terminated with a ;. So there you go. Now you know what that little semicolon is doing there in your code.
3 comments
Read more

C# Performance Improvement - The Power of StringBuilder

 Often when we are wring code we don't think about performance and go with the default options available to achieve a task. String concatenation is one such scenario. If you are doing simple and few string catenations, then you can use the following result = string1 + string2; string1+= string2; result = String.Concat(string1,string2); String.Format and string interpolation are few other options.  However when you are performing large and repetitive  operation, string catenation can be expensive. Here is an example to prove the point.  As you can see it took 41 seconds to perform 100k string catenation. Now lets replace this with StringBuilder and see.  8 ms!!!!!! That is a massive performance difference. Hope you get the point. More info on StringBuilder can be found here https://learn.microsoft.com/en-us/dotnet/api/system.text.stringbuilder?view=net-7.0
Post a Comment
Read more