Why not use the word 'project' in Scrum?
When I attended Scrum Master training I distinctly recall being told not to use the word project. For the life in me, I can't recall why. Is there an explanation or is this just down to personal preference?
I even recall another candidate explaining that any CVs received by their organisation with terms like 'Agile Project Manager' in were immediately rejected.
Any advice or guidance would be much appreciated.
When I attended Scrum Master training I distinctly recall being told not to use the word project. For the life in me, I can't recall why
In Scrum the focus is upon products rather than projects. It may reasonably be argued that the emphasis is upon having product-oriented endeavors rather than project-oriented ones. However, the validity of the project construct is not in question. Do a search on the Scrum Guide for the word "project" and consider the context in which it is used.
I even recall another candidate explaining that any CVs received by their organisation with terms like 'Agile Project Manager' in were immediately rejected.
I could put Agile Delivery Manager in my CV because that was the title I had on an engagement about 6 years ago, although it was not a Scrum role. Being rejected on the basis of that would be a shame, because I would gladly discuss the impact and ramifications of such things with an interviewer.
Thank you so much for the guidance. This will help me immensely in my current situation