Quote:
Originally Posted by muttiah
As a lead isn't it your job to define these tasks and set timelines based on expected progress?
Maybe? But am I a lead? It's kind of unclear except when I get blamed when something goes wrong. Until a few weeks ago that was definitely my boss' role. Now it's *probably* my role? Except when she wants to get involved again.
So the other devs seem to look at is as basically a partnership with me, but ultimately they report to my boss, not me, and can work on things they way they see fit and in what order they want.
They have a prototype to work off of and while they'll listen to me I think ultimately they feel the prototype is boss. Even though it doesn't cover detailed requirements like how to handle and display certain errors, which errors to worry about, how to handle real time form validation, etc. Also stuff that my boss isn't really interested in, but still has to work.
And there's been some necessary back and forth with the prototyper which has caused some moderate scope creep, but made the first pass of this app a lot better. However since we have no real timelines or detailed tasks - there's no way to show the effect the scope creep. And since we spent 3 months dicking around with a completely useless contractor, we now have no extra wiggle room and people are getting pissy about why we haven't delivered anything.
I'm also the only one who actually drags the jira tickets from backlog, to development, to feedback. Do I want to make a big stink about this and either get my boss to talk to them over it, or try to cajole them to do it? Not really. So if I think something's done I just drag the task over.
My boss tells me to make jira tasks so I do. It's never been 100% clear if I can assign the jira tasks to devs but that seems like what she wants me to do. Could I ask her to clear this up? Yes. But something in my spidey sense just tells me that's a conversation I don't really want to have, as the answer I get could hamper me from my ultimate goal of just trying to deliver the project. Or it turns into some version of me sounding like Cartman yelling "Respect Mah Authoratah!"
And there's a fun culture of working on something for 3 days then checking it in w/o any sign off. So now for me to go back and say it's not right - I'm the one reopening some kind of issue that a dev thought they were done with.
Btw we're pretty much a 3-person team right now and all of the above is basically from having to work with the CSS person - who's the kind who needs every single tiny detailed requirement spelled out for her - but is clearly not on board with me being the one to spell these out.
For example - the prototype shows a username not found error and password invalid error at the same time. Well that's what she programmed. I have to explain to her those are two different errors for different cases, and they don't make sense together. For which I basically get the passive aggressive blank stare and who know when or if she's going to change it to the behavior that I want.
So am I the lead or not? If the boss asks her she'll probably say she's getting to it. But if not I could easily see me not being able to get her to change it w/o some kind of rank pulling pain. I could always change it myself. But for all I know she's already changed it and just not checked it in yet. Also she doesn't really get git and is clearly annoyed at me for trying to get her to use it in a way that doesn't cause conflicts. So if I break her **** and cause conflicts - it will be a blast.
I'm hoping when the main react dev gets back from vacation next week things will go better.
Last edited by suzzer99; 02-18-2019 at 02:21 AM.