Timeline for Going from project manager to scrum master (career progression)
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 29, 2015 at 7:41 | comment | added | matt_jay | As long as you're fine with playing that type of game, I hope the other answers help you do so. If you are curious if e rules can be bent or if there's a more fun sport to pursue, how about applying for a position you are not really interested in (other location, different industry) and see if you might not be able to sell yourself on other criteria? ;-) | |
| Aug 29, 2015 at 7:40 | comment | added | matt_jay | I can see how there are environments where people rely on that type of information to assess and judge candidates. But I think it also tells a lot of those peoples' understanding of and appreciation for a candidate's track record. In the worst case it's the first sign that the recruiter (internal or external) does not understand the requirements for the position itself. It may also just be a matter of habit specific to companies of a certain size that I am not all too familiar with, or even a cultural thing in the place that you live in. | |
| Aug 29, 2015 at 5:49 | comment | added | AgileTeamMember | Thanks for your input. I appreciate it. As much as I would like to believe that job titles are not important, my experience in interviewing tells me that it is a big factor in even being shortlisted for an interview. If this role was that of a project manager with some scrum master skills, I guess I could take a temporary hit in responsibilities , viewing it as a learning experience. But the issue arises when the job title spells out scrum master, stripped of all PM responsibilities. So, someone looking to hire a candidate with recent PM experience may not find scrum-mastering sufficient. | |
| Aug 28, 2015 at 12:39 | history | answered | matt_jay | CC BY-SA 3.0 |