Skip to main content

Certified Scrum Product Owner - Mission, Principles and Approach


I’ll be embarking on the ‘Certified Scrum Product Owner’ course tomorrow. Ye gods I hear you cry, ‘You’re going to be certified (or certifiable)!’ and ‘It’s methodology specific, what about context, won’t somebody please think of the context?’ 

Before we all get bent (!) out of shape, hear me out. For a great many activities I undertake I define a mission (my statement of intent), principles (thoughts that may guide me) and an approach (how I will behave, act and actions I’ll take).


My Mission
‘In my recent experience, a lack of focus on return on investment has led to a number of unsuccessful product outcomes and identified a gap in my knowledge. Testing is rooted in return on investment (time, effort, thought) and more empathy with a Product Owner and the decisions made can help focus testing on what’s really important.’
My Principles

  • The course I am about to embark on is theory. Theory is a good grounding but context remains as the focus. I remind myself, ‘there are no best practices only good practices in context.’
  • The skills I learn will be added to my overall toolkit, for me, the certification is arbitrary but welcome. The expansion of the tools I have is the aim.
  • Quality can be defined as value to ‘some person.’ That ‘some person’ may have a stake in the Product. I’ll bear this in mind when discussing quality on the course.
  • Testing and return on investment are interdependent. Development on a product can be subject to a similar law of diminishing returns as the amount of testing executed is.
  • Acknowledge the bias I bring to the course. I approach the course as a tester, which influences my focus and aims.
My Approach

  • Make my mission available to all participants, accept challenges and critically assess that mission on a continuous basis.
  • Listen (yes, I do need to remind myself to do this)
  • Learn, engage with the new, and contrast that with your current world view.
  • Identify where the knowledge is of use to you in the ‘real world.’ Plan to apply that. 

So, those are my thoughts, I sincerely hope that what I learn will dramatically change these ideas. I will create a review blog and let you know how I got on!



Comments

  1. The product owner is someone who has an in-depth knowledge about business needs for the product being delivered. The product owner has to be an individual as the decision making power cannot be given to a team. If there is a team of stakeholders that helps the product owner, the final decision making power should lie with the product owner .

    ReplyDelete
    Replies
    1. Hi Casey

      I agree up to a point but the relationship between Product Owner and Team must have an element of give and take. Keeping the team engaged and focused on value (and not dictated to) is also part of the role for my money.

      As a Product Owner, I want teams to make some decisions. If you are doing your job, your team feel empathy with the business too, enabling them to make certain decisions with a nod in your direction so you can input if you need to.

      Large, paradigm shifts should be the reserve of the Product Owner as decision maker (as a heuristic). When in that role, I tend to sweat the small stuff on a periodic basis and do a deep dive on a story.

      Maybe thats just my style.

      Thanks

      Ash

      Delete
  2. Scrum has become one of the most popular Agile methodologies used for software and product development. Various factors have contributed to this popularity. The methodology works very well with complex projects where requirements change often and/or the technology is new and not used before.

    ReplyDelete

Post a Comment

Popular posts from this blog

Testers Guide to Myths of Unit Testing

One area that testers might be able to enhance their contributions to software development teams is how we perceive and contribute to unit testing. I believe testers busting their own illusions about this aspect of building something good would bring us much closer to developers, and help us realise what other layers of testing can cover most effectively.

Also, I want to do a talk about it, so I figured I would test the premise, see if potential audiences were into it. I put this on Twitter:
Working on a talk about what testers might believe about unit #testing & how we interact with developers creating unit tests. Any challenges/additions for my list below? #development#agilepic.twitter.com/4oT5HE4qs3 — Ash Winter (@northern_tester) December 19, 201730 replies with ideas tends to indicate that people might be into it. 
The ListI thought, as my final blog of 2017, I would provide a super useful list of the myths and legends we as testers might believe about unit testing:
That developer…

Wheel of Testing Part 2 - Content

Thank you Reddit, while attempting to find pictures of the earths core, you surpass yourself.
Turns out Steve Buscemi is the centre of the world.

Anyway. Lets start with something I hold to be true. My testing career is mine to shape, it has many influences but only one driver. No one will do it for me. Organisations that offer a career (or even a vocation) are offering something that is not theirs to give. Too much of their own needs get in the way, plus morphing into a badass question-asker, assumption-challenger, claim-demolisher and illusion-breaker is a bit terrifying for most organisations. Therefore, I hope the wheel is a tool for possibilities not definitive answers, otherwise it would just be another tool trying to provide a path which is yours to define.


In part one, I discussed why I had thought about the wheel of testing in terms of my own motivations for creating it, plus applying the reasoning of a career in testing to it. As in, coming up with a sensible reflection of real…

Wheel of Testing Part 3 - Applications

I've only had to quit two jobs to finally find the time to finish this blog series. Winning at life. If you need reminders (like I did) check out Part 1 and Part 2 before reading on...

After the first two blogs regarding the Wheel of Testing, I was delighted to receive a few requests for the wheel itself, which got me thinking about applications of it, beyond what its original intent was, which I've explored in detail in part 1 of this series of intermittent blogs. Most models need a little air time to show their value, in software development we crank out models all the time, but I'm not sure how many get used. I am inspired by models such as the "Heuristic Test Strategy Model" by James Marcus Bach, as I have used it and seen the benefits it has brought for my clients, particularly the ability to ask questions. So, I wanted to create a model which has a number of use cases, both real and imagined:

Helping to unlocking a career in testing which may be stuck

It is no…