Product Manager own the product while the product owner manage it. Scrum Manager work both towards management and the team and everyone is an engineer, but have no scientific approach to anything they do.
Sometimes I feel that the world has gone mad and that titles as well as words are used without logic or even thought sometimes.
A Product Owner, owns the product.
A Product Manager, manages the product.
It is defined in the titles themselves...
A Scrum Manager is just a manager in a fake Scrum setting, or you would not need a manager to begin with. Just throw out Scrum and start working properly instead and call the position a team leader or team manager that fit the work that is being done. Or just use Scrum if you prefer that and have a Scrum Master.
A Business Analyst work on the business side to help sort out business needs. A Requirement Analyst help to break down business needs to requirements.
Both roles are facilitating to act as translators and guides. They have no deciding authority, but work as the bridge between the business side and the implementation side.
Requirements are legally binding contracts of work the defines what should be done and how to verify that the work is done according to what is being needed. Requirements should be defined based on the level of trust between the business side and the implementation side.
A Full Stack anything is just a junior pretending to know more than they do. Unless you define the stack and what full means, you are just...well full of it.
Engineers work with a scientific approach and unless you actually can explain how you conduct our work with a scientific approach, then you are not an engineer. And no, Agile is not a scientific approach.
Projects are fixed in time, cost and scope, and they are funded as investments, not operational work. If whatever work you are doing is not fixed, and it is not funded through an investment budget, then you are not working in a project.
I know making things up to make you feel important and using words that are wrong because that is "how it has always been", but we are just spiraling towards understanding what we do and what we mean less and less.
How about we stop using what has always been and start applying logic to our workplaces?
Or has that ship already sailed, and we are doomed to a future when words no longer have meaning or logic to them? Will we just talk gibberish like management consultants and c-level management spewing buzzwords to sound important?
What do you think?
.webp.dc8b5391ca140cb7161774334d0b9581.webp)
Recommended Comments
Create an account or sign in to comment