Priority #1

Posted Leave a commentPosted in management

How often do you ask your main stakeholders about first priority features?

Should we analyse feature A first or feature B first? Should we start working on A, B or C?

Do you think that prioritization would remain the same with following options (assuming that we know potential users and revenue)?

  • Option 1
    • A – 1 month; B – 1 month; C – 1 month.
    • Teams involved: A – 1 team; B – 1 team; C – 1 team.
  • Option 2
    • A – 1 month; B – 1 month; C – 1 month.
    • Teams involved: A – 3 teams; B – 4 teams; C – 2 teams.
  • Option 3
    • A – 3 months; B – 2 months; C – 4 months.
    • Teams involved: A – 3 teams; B – 5 teams; C – 2 teams.

What additional information apart intuition do you use in decision making? Do you use spikes to improve decision making?

Leave developers alone

Posted Leave a commentPosted in management

If you are working in a product development company most probably you are doing something wrong if start changes and improvements in a technology departments/teams. Little by little i start to understand that.

Leave developers alone, let them do the work they love and focus instead on the flow and other challenges which require attention and might be missed:

  • Understand and communicate the essence of the product
  • Identify business value and stakeholders’ needs and make sure this is delivered regularly
  • Clarify, negotiate and communicate the important priorities and dates
  • Balance the needs
  • Work effectively with development team(s)
  • Identify, track and address things blocking progress
  • Gather and spread information

Developers can help with all these activities, but most probably they don’t love this type of work. That is why they are not managing the product and don’t want to act as Product Owner or Product Manager.

Before you want to build a feature…

Posted Leave a commentPosted in quick thoughts

Here is a couple of questions to ask before you want to build a feature.

If we built <feature name>, what measurable business benefit or other positive outcome would be achieved?

If we built <feature>, which roles or user personas would use it, and how often would they use it?

When being a Product Owner what else do you treat as important before you start building something?

Why being Product Owner is so difficult?

Posted Leave a commentPosted in management, quick thoughts

Would highlight following reasons based on my experience:

  • Wears multiple hats – marketer, designer, sales expert, business analyst, …
    • must learn delegate and educate others to avoid becoming a bottleneck
  • Must be domain expert so others and teams would trust in decisions
  • Defines demand of investments into development
  • Has to be perfect communicator as needs to clarify and negotiate important priorities and delivery dates
  • Has to love his product and be passionate about it

What is your opinion?