www.scrum.org Open in urlscan Pro
34.233.202.171  Public Scan

Submitted URL: https://go.pardot.com/e/395772/nsiderations-new-product-owner/z6n3gh/1878190907?h=fWt9BrhwKH06Y8q-jiG2FIRzy5zAfXN9wwjA...
Effective URL: https://www.scrum.org/resources/blog/giving-back-considerations-new-product-owner
Submission: On July 26 via api from US — Scanned from DE

Form analysis 2 forms found in the DOM

GET /search/node

<form action="/search/node" method="get" id="search-block-form" accept-charset="UTF-8" data-once="form-updated" data-drupal-form-fields="edit-keys">
  <div class="form-item form-group form-type-search form-item-keys form-no-label">
    <input title="Enter the terms you wish to search for." data-drupal-selector="edit-keys" type="search" id="edit-keys" name="keys" value="" size="20" maxlength="128" placeholder="Search" class="form-search form-type- form-control">
  </div>
  <div data-drupal-selector="edit-actions" class="form-actions js-form-wrapper form-wrapper" id="edit-actions">
    <input data-drupal-selector="edit-submit" type="submit" id="edit-submit" value="Search" class="button js-form-submit form-submit form-type- form-control">
  </div>
</form>

POST /resources/blog/giving-back-considerations-new-product-owner?destination=/resources/blog/giving-back-considerations-new-product-owner

<form class="user-login-form" data-drupal-selector="user-login-form" action="/resources/blog/giving-back-considerations-new-product-owner?destination=/resources/blog/giving-back-considerations-new-product-owner" method="post" id="user-login-form"
  accept-charset="UTF-8" data-once="form-updated" data-drupal-form-fields="edit-name,edit-pass,edit-submit--2">
  <div class="form-item form-group form-type-textfield form-item-name">
    <label for="edit-name" class="js-form-required form-required">Email address</label>
    <input autocorrect="none" autocapitalize="none" spellcheck="false" data-drupal-selector="edit-name" type="text" id="edit-name" name="name" value="" size="15" maxlength="60" placeholder="email address"
      class="form-text required form-type- form-control" required="required" aria-required="true">
  </div>
  <div class="form-item form-group form-type-password form-item-pass">
    <label for="edit-pass" class="js-form-required form-required">Password</label>
    <input data-drupal-selector="edit-pass" type="password" id="edit-pass" name="pass" size="15" maxlength="128" placeholder="password" class="form-text required form-type- form-control" required="required" aria-required="true">
  </div>
  <input autocomplete="off" data-drupal-selector="form-i-bbnkrvmh3foa-udeb5ulnygxtveil4zp2zj7c6lfo" type="hidden" name="form_build_id" value="form-i-bbnKRVmH3FOa_uDEB5uLNYgxtveiL4ZP2zJ7C6lfo" class="form-type- form-control">
  <input data-drupal-selector="edit-user-login-form" type="hidden" name="form_id" value="user_login_form" class="form-type- form-control">
  <div data-drupal-selector="edit-actions" class="form-actions js-form-wrapper form-wrapper" id="edit-actions--2">
    <input data-drupal-selector="edit-submit" type="submit" id="edit-submit--2" name="op" value="Go" class="button js-form-submit form-submit form-type- form-control">
  </div>
</form>

Text Content

Skip to main content
Home
X
 * login
 * register
 * partners
 * support
 * Search

 * Home
 * About
   * Back
   * About
   * Who is Scrum.org
   * Why Scrum.org
   * Partners
   * News
   * Staff
   * Professional Scrum Trainers
   * Diversity & Social Responsibility
   * Careers
   * Support Center
   * What is Scrum?
   * Professional Scrum Defined
 * Training
   * Back
   * Training
   * All Courses
   * Class Schedule
   * Applying Scrum
   * Scrum Master
   * Advanced Scrum Master
   * Product Owner
   * Advanced Product Owner
   * Agile Leadership
   * Evidence-Based Management
   * Scaled Scrum
   * Scrum with Kanban
   * Scrum with User Experience
   * Developer for Software Development
   * Request a Private Class
   * Find a Trainer or Coach
   * Students Reviews
 * Certification
   * Back
   * Certification
   * All Certifications
   * Professional Scrum Master
   * Professional Scrum Product Owner
   * Professional Scrum Developer
   * Professional Agile Leadership
   * Professional Agile Leadership - Evidence-Based Management
   * Scaled Professional Scrum
   * Professional Scrum with Kanban
   * Professional Scrum with User Experience
   * All Practice Tests
   * Scrum Open
   * Product Owner Open
   * Scrum Developer Open
   * Agile Leadership Open
   * Evidence-Based Management Open
   * Nexus Open
   * Scrum with Kanban Open
 * Community
   * Back
   * Community
   * Blog
   * Forum
   * Meetups
   * Events
   * Become a Professional Scrum Trainer
   * Register for our Newsletter
   * Search Professional Scrum Certificate Holders
 * Innovations
   * Back
   * Innovations
   * Scaling Scrum with Nexus
   * Evidence Based Management (EBM)
   * Scrum with Kanban
 * Resources
   * Back
   * Resources
   * All Resources
   * Professional Scrum Competencies
   * The Scrum Guide
   * Webcasts
   * Videos
   * Case Studies
   * Books
   * Scrum Masters Learning Path
   * Product Owners Learning Path
   * Software Developers Learning Path
   * Agile Leader Learning Path



X
Back
X


LOGIN

Email address
Password

 * Forgot Password


NOT REGISTERED?

If you don't already have a Scrum.org account, you can sign up in just a few
seconds.

Register Here

Due to the Russian invasion of Ukraine, we have paused all purchases and
training in and from Russia.  Read Statement

Subscribe to our blog by signing up for the Scrum.org newsletter, or by
subscribing to the RSS feed.

 RSS
Back to Blog Listing Prev Next
July 4, 2022


GIVING BACK : CONSIDERATIONS FOR A NEW PRODUCT OWNER

Paul Ralton

Paul Ralton website Paul Ralton LinkedIn Paul Ralton contact View profile


5 from 2 ratings
0 Comments

Following on from my previous post (Considerations for a new Scrum Master) this
blog aims to help those just starting out as a Product Owner.

Like my previous blog - the following items are in no particular order of
preference.

The aim is to outline some of the key aspects that are probably worthwhile you
considering as you get started on your Product Owner journey.  

 * Know your product
   * Make sure you know just what your product is, what problem(s) you are
     trying to solve and for whom
     * "A product is a vehicle to deliver value. It has a clear boundary, known
       stakeholders, well-defined users or customers. A product could be a
       service, a physical product, or something more abstract." [The Scrum
       Guide 2020]
 * Generate a Business Model
   * Take time to explore something like the Business Model Canvas or the Lean
     Canvas in order to try and ensure that others around you begin to
     understand your product and its unique value propositions
 * Create and share your Product Vision
   * Your product vision should inspire those that are working towards achieving
     that long term goal
   * Keep it short, focussed and to the point - this will help others understand
     and remember it
   * Explore some of the many online templates available to help get you going
   * Pull in others to help you create your product vision - don't feel that you
     have to do this alone
   * Aim to communicate and share your product vision at every opportunity that
     you have (as a minimum think about the core Scrum events)
 * Create a Product Goal
   * This should be an intermediate goal acting as a step towards your longer
     term product vision
   * Make sure it is measurable otherwise how will you ever truly know that you
     have achieved it
   * Ensure it is well understood by your Scrum Team(s) and wider organisation
   * Remember that the intent is to achieve or abandon a product goal before
     then moving onto the next one
 * Start to build your Product Backlog
   * Your active product goal should be in your product backlog but note that
     not everything in your product backlog has to directly relate to your
     product goal
   * Get others involved and consider exploring techniques like user story
     mapping to help get started
 * Identify key stakeholders
   * Consider running a brainstorming activity with everyone that you think
     would have an opinion in order to build a stakeholder map:



 * * For the stakeholders that you have identified then consider placing them on
     a "2X2 power-interest grid" in order to know how best to involve them:

 * Make use of your Scrum Master
   * Remember that Scrum Masters are there to help you as a Product Owner. Ask
     for their help and support around product backlog management and
     conversations/collaboration with stakeholders (particularly around
     facilitation). 
 * Make use of your Developers
   * Try to make sure that you don't spend all day every day just gathering
     requirements, uploading them into some web-based tool, adding as much
     detail as you can and including things like acceptance criteria and then
     handing such items off to the developers. That's clearly not a hugely
     valuable use of your time plus is not enabling true business agility. Get
     the rest of the Scrum Team involved to take more responsibility around
     product backlog management and remember that it will always be the shared
     understanding through conversation and collaboration that is most
     important.
 * Metrics, metrics, metrics
   * Consider which metrics make sense to measure in your context. Without
     metrics then how do you know that what you are doing is the right thing?
     How will you know it's valuable? How will you know when to try something
     different?
   * Take a look at Evidence Based Management and begin to understand how the 4
     key value areas relate to each other plus explore some of the candidate
     metrics that you might consider for your product (but remember this is not
     an exclusive list of all possible metrics).
 * Experiment, experiment, experiment
   * Consider what experiments you might run in order to better understand
     whether to pivot or persevere
   * Try to adopt the mindset and behaviours of an entrepreneur
 * Focus on shortening the feedback loop
   * Shorter feedback loops accelerate learning. Up until releasing then
     everything is simply a hypothesis. Remember therefore that you need to
     release in order to validate and potentially realise value.
 * Continue your Product Owner learning
   * Access the myriad of excellent learning opportunities available via the
     Product Owner Learning Path on Scrum.org

I hope you find these thoughts useful as you begin on your Product Owner
journey.

If you decide that you would like to come along to a Professional Scrum Product
Owner class then feel free to reach out to me at paulralton@bagile.co.uk or take
a look at our course schedule. We offer both public and private courses to fit
your needs.

Also let me know your thoughts on the above....what's missing....what else would
you add for new Product Owners?


SHARE THIS POST

 * Email
 * Facebook
 * Twitter
 * LinkedIn
 * Reddit
 * Pocket

Blog Comments

Prev Next
By using this site you are agreeing to the Privacy Policy and Terms of Service X

© 2022 

Scrum.org. All Rights Reserved.
 * Contact
 * Privacy
 * Terms of Service
 * TM and © Guidelines

 * https://twitter.com/Scrumdotorg
 * http://facebook.com/scrum.org
 * https://www.linkedin.com/company/scrum-org
 * https://www.youtube.com/user/Scrumorg