Artigo muito bom do David Pereira fazendo algumas provocações sobre o papel do PM e como evoluir.
1. Ask for forgiveness, not permission
2. Do what’s needed, not what’s easy
3. Deliver results beyond tasks
Outstanding PMs don’t talk about velocity. They don’t care about it. Creating more features cannot guarantee more value. (Ponto importante mas pode ser sensível falar disso…)
Shipping five features a week doesn’t matter if nothing changes. Your output isn’t your value. Your impact is.
4. Lead with context, not control
5. Write broken stories, not perfect ones
PMs are not story writers. Your job isn’t to tell software engineers what to do. Your real job is to tell them what to achieve and figure out together. (OOF!)
6. Define success, not just acceptance
7. Challenge the status quo, don’t conform to it
Comfort is a trap. Just because something worked yesterday doesn’t mean it works today. The challenge is that you don’t know when something will stop working.
Your job is not to protect the current way of working but to evolve it. Growth never happens without discomfort.
Vale a pena ler o conteúdo completo no link:
