Member-only story
What does it really mean to be an Agile Product Manager?
Itโs all about:
โข Profit ๐ผ๐๐ฒ๐ฟ greed
โข Motivation ๐ผ๐๐ฒ๐ฟ burnout
โข Doing things right ๐ผ๐๐ฒ๐ฟ fast
โข ROI ๐ผ๐๐ฒ๐ฟ doing what you are told
โข Using great ideas ๐ผ๐๐ฒ๐ฟ choosing the plan
โข Efficient MVP ๐ผ๐๐ฒ๐ฟ expensive ideal version
โข Clear communication ๐ผ๐๐ฒ๐ฟ confusing details
โข Overall product results ๐ผ๐๐ฒ๐ฟ your teamโs delivery
โข Short, relevant backlogs ๐ผ๐๐ฒ๐ฟ long, full of BS ones
โข Getting things to work well ๐ผ๐๐ฒ๐ฟ working perfectly
โข Learning from your mistakes ๐ผ๐๐ฒ๐ฟ the blame game.
โข Career growth based on results ๐ผ๐๐ฒ๐ฟ playing politics
โข Listening to userโs voice ๐ผ๐๐ฒ๐ฟ stakeholderโs demands
โข Monitoring a few relevant metrics ๐ผ๐๐ฒ๐ฟ dozens of them
โข Transparent prioritization ๐ผ๐๐ฒ๐ฟ working off gut feelings
โข Problem-focused roadmaps ๐ผ๐๐ฒ๐ฟ feature-focused ones.
โข Giving the team space to grow ๐ผ๐๐ฒ๐ฟ micromanagement
โข Well-planned sprints ๐ผ๐๐ฒ๐ฟ relying on stories estimations.
โข Problems looking for solutions ๐ผ๐๐ฒ๐ฟ the other way round
โข Pursuing the best opportunity ๐ผ๐๐ฒ๐ฟ sticking to the roadmap
โข Having a single, achievable, but ambitious ๐ผ๐๐ฒ๐ฟ several goals
โข Prioritizing true value bringing stories ๐ผ๐๐ฒ๐ฟ stakeholder requests
โข Fixing issues that jeopardize user experience ๐ผ๐๐ฒ๐ฟ fixing every bug
โข Commitments to solving problems ๐ผ๐๐ฒ๐ฟ feature delivery date ones.
โข Iterating a releaseโฆ










