10 ms·
Yeah, you've described my challenge exactly. I'm all three and it's annoying. My title is Architect or Principal Architect. Boss sees me and uses me as Tech Lea
by tunesmith 4y ago
Yeah, you've described my challenge exactly. I'm all three and it's annoying. My title is Architect or Principal Architect. Boss sees me and uses me as Tech Lead across multiple teams (and the teams have really needed it). For me it's more about coding standards, best practices, and education than it is about interpreting product needs into stories - we have others for that. Boss's Boss doesn't appreciate that stuff and wants me as Architect, which puts them into battles. And in practice, I get pulled off both to be Solver - they call them "emergent issues", and the hard ones come to me. There isn't anyone technical above me that I can ask for help. Meanwhile I get dinged at quarterly reviews by our scrum-master for not having a predictable velocity.
- gtirloni 4y agoStory of my life. Please please let us know if you ever come to a satisfactory solution. I'm starting to take my head of the sand about this now, finally.
- dalyons 4y agoTell your scrum master to go jump (or even better don’t work anywhere with a scrum master). If your title is principal architect, then the business expects different things out of you than story points.