SPaMCAST 508 – Product Owners and Scrum Masters, An Interview with Vasco Duarte

http://www.spamcast.net

Listen Now
Subscribe: Apple Podcast
Check out the podcast on Google Play Music

SPaMCAST 508 features our interview with Vasco Duarte!  Vasco and I discuss vision and product owners. The product owner role is crucial. To be effective, the product owner must be able to articulate a vision for the product they champion.

Vasco Duarte’s Bio in his own words:

I want to transform product development organizations into product business organizations. I do that by focusing the work of the product development teams on the end-to-end life-cycle of their products. From Concept to Cash and Back!

Currently a Managing Partner at Oikosofy.

Product Manager, Scrum Master, Project Manager, Director, Agile Coach are only some of the roles that I’ve taken in software development organizations. Having worked in the software industry since 1997, and Agile practitioner since 2004. I’ve worked in small, medium and large software organizations as an Agile Coach or leader in agile adoption at those organizations.

I was one of the leaders and catalysts of Agile methods and Agile culture adoption at Avira, Nokia, and F-Secure.

I host a daily podcast where I interview Scrum Masters about their daily challenges and insights: https://scrum-master-toolbox.org/

You can read more from me at my blog: http://SoftwareDevelopmentToday.com

You can join me on twitter: @duarte_vasco

Re-Read Saturday News

In week 4 of re-read of The Checklist Manifesto by Atul Gawande (use the link and buy a copy so you can read along) we tackle Chapter 3, The End Of The Master Builder.  In Chapter 3 Gawande identifies the scenarios in which checklists have an impact.  Checklists provide value even in the most complicated scenarios.

Current Installment:

Week 4 – The End Of The Master Builder – https://bit.ly/2BmIGBc

 

Messing Up Product Roadmaps

Map of the Fredrick Half-Marathon

A product roadmap is a powerful tool.  Roadmaps help link products and services to the strategy, objectives and key results.  Roadmaps are directional, answer the question of where we are going and why.  Roadmaps are powerful – unless they are messed up!  There are four common mistakes that will reduce the value of a roadmap.

 

A Hierarchy of Roadmaps, or Don’t Start in the Middle!

Product roadmaps come in many sizes and flavors and depending on size and flavor answer a myriad of questions.  There are several common threads through all product roadmaps.  The common threads are:

1.      Roadmaps are tied to the business strategy.
2.      Roadmaps answer where are we going.
3.      Roadmaps answer why we are making the choices we are making.
4.      Roadmaps are tied to objectives and key results (business outcomes).

 

Product Roadmaps: Basics and Context

A Roadmap Provides Direction

Product roadmaps are a tool used to visually present an approach to translating a business strategy into the real world. The visualization of the impact of a strategy on a product allows all relevant constituencies to grasp how a product and its enablers are intended to evolve.  

In order to create and use product roadmaps, there are several key concepts and components that need to be agreed upon.  

 

SPaMCAST 447 – Product Owners and The Business Analyst with Angela Wick

http://www.spamcast.net

Listen Now
Subscribe on iTunes
Check out the podcast on Google Play Music

 

SPaMCAST 447 features our interview with Angela Wick on the role of the Product Owner and Business Analyst in Agile efforts. These two roles are critically important for delivering value in an Agile environment. Angela provides a fresh take on the Product Owner role and the Product Owner’s relationship to other roles Agile teams.

Angela is the founder of BA-Squared, LLC, a training and consulting practice.  She is passionate about modernizing requirements practices and helping organizations collaborate on a Product Vision aligned to strategy and guiding them to a meaningful backlog and iterations that keep the customer and organizational value top of mind.

She trains, coaches and teaches organizations on Product Ownership and Agile BA!

Email: Angela@BA-Squared.Com

Web: http://www.ba-squared.com

LinkedIn: https://www.linkedin.com/in/angelawickcbap

Twitter: https://twitter.com/WickAng

This is not first time the SPaMCAST has featured essays and conversations on the role of product owners ( for exampleSPaMCAST 430 and SPaMCAST 325).

 

Re-Read Saturday News

Chapter 9 continues the third section of Holacracy, Evolution Installed: Living Holacracy.   Holacracy: The New Management System for a Rapidly Changing World by Brian J. Robertson was published by Henry Holt and Company in 2015.  This week’s chapter is titled If You’re Not Ready To Adopt: Moving Toward Holacracy.  In this chapter Robertson softens his if-you-can’t-do-it-all-don’t-do-anything approach.  

 

SPaMCAST 444 – Product Owner – The Hard Role, QA Value, Work In Process Limits

http://www.spamcast.net

Listen Now
Subscribe on iTunes
Check out the podcast on Google Play Music

This week’s Software Process and Measurement Cast features our essay revisiting the product owner role. The product owner role is hard, often messed up and a great opportunity for improvement.

The second column features the return of Steve Tendon talking about Tame The Flow: Hyper-Productive Knowledge-Work Performance, The TameFlow Approach and Its Application to Scrum and Kanban published J Ross (buy a copy here). We tackle Chapter 17 which is titled Challenges of Work-State Work in Process Limits. WIP limits have their plusses and minuses when discussing hyper-productivity.  

Our third column this week is from Jeremy Berriault. Jeremy discusses how to show the value of QA and why knowing and showing value is important!   Jeremy  blogs at https://jberria.wordpress.com/  

 

Re-Read Saturday News

This week we tackle Chapter 6 of Holacracy: The New Management System for a Rapidly Changing World by Brian J. Robertson published by Henry Holt and Company in 2015.   Chapter 6, Facilitating Governance, puts the ideas and processes defined in governance to work.

 

Product Owner Role Problems: Part-time and Overly Controlling Product Owners

Control!

The product owner (PO) role is incredibly important in any Agile effort. The product owner leads, manages and prioritizes the backlog and networks with stakeholders, customers, and developers of all stripes.  All sorts of problems can beset the role. However, most of those problems are either self-inflicted or a result of poor organizational design.  A laundry list of problems based on observation and responses from other product owners include:

1. Product Owners Are From IT
2. Product Owners Are Not Part of The Team
3. Having a Project versus Product Orientation
4. Overly Broad and/or Ill-Defined Product Owner Role
5. Using Proxy Product Owners
6. Adopting Technical and Business Product Owners
7. Allowing Part-time Product Owners
8. Failure of Product Owner to Lead
9. Product Owner with Controlling Personality

The next set of difficulties are: