![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
What the heck do you do anyway?
I love my family.
And the steak was good too.
I've been asked several times to explain what it is that I do at my new job. I'm not sure it's really explainable. The title is officially Senior Business Analyst.
This past week, I attended way too many meetings. Meetings about testing, about technical issues, management issues, network issues. Anything to do with the project I'm on. I helped with some compiling and some testing. I tracked down people when things didn't work. I answered questions all over the place. I wrote some test cases. I worked on scheduling and updated the status about what was done, what was expected, and what was late.
Does that help any or are you all more confused than ever?
Hmm ... Monday morning ... arrive, review test criteria written by business owner. Just to see what the system does, cause I'm still learning, and to see what sorts of things they're putting in there. What did they miss?
I got to attend a go/no go meeting. Joy. I got to help copy files and ftp test data to the UNIX server. That was a treat. I got to answer way too many emails, and chase people down about creating the UAT environment. Which they keep telling me they don't have all the information, but when we have the meetings, they don't say what they need to know. it's very frustrating.
I created 3 problem logs and shipped them to the developers. They're gonna love me monday morning, I can tell.
I requested a computer for the second tester/developer coming in next week. I tracked down the DBAs... three times. I tracked down the UNIX admin folk three or four times. I tracked down the external interface testers a couple times. I got dragged into umpteen meetings I just had to be there for. I helped someone figure out the directory structure she needed to use. I helped someone else figure out which files needed to go into the source control libraries. I coordinated getting some help from one team, for another team that couldn't connect due to a temporary network glitch.
Ain't it all fun?
Yes, I do spend my days sending emails, on the phone, or physically tracking down people. It's still exhausting. And sometime in there, I get to do some technical writing, business analysis, and testing.
Anything else I should tell you all about?
And the steak was good too.
I've been asked several times to explain what it is that I do at my new job. I'm not sure it's really explainable. The title is officially Senior Business Analyst.
This past week, I attended way too many meetings. Meetings about testing, about technical issues, management issues, network issues. Anything to do with the project I'm on. I helped with some compiling and some testing. I tracked down people when things didn't work. I answered questions all over the place. I wrote some test cases. I worked on scheduling and updated the status about what was done, what was expected, and what was late.
Does that help any or are you all more confused than ever?
Hmm ... Monday morning ... arrive, review test criteria written by business owner. Just to see what the system does, cause I'm still learning, and to see what sorts of things they're putting in there. What did they miss?
I got to attend a go/no go meeting. Joy. I got to help copy files and ftp test data to the UNIX server. That was a treat. I got to answer way too many emails, and chase people down about creating the UAT environment. Which they keep telling me they don't have all the information, but when we have the meetings, they don't say what they need to know. it's very frustrating.
I created 3 problem logs and shipped them to the developers. They're gonna love me monday morning, I can tell.
I requested a computer for the second tester/developer coming in next week. I tracked down the DBAs... three times. I tracked down the UNIX admin folk three or four times. I tracked down the external interface testers a couple times. I got dragged into umpteen meetings I just had to be there for. I helped someone figure out the directory structure she needed to use. I helped someone else figure out which files needed to go into the source control libraries. I coordinated getting some help from one team, for another team that couldn't connect due to a temporary network glitch.
Ain't it all fun?
Yes, I do spend my days sending emails, on the phone, or physically tracking down people. It's still exhausting. And sometime in there, I get to do some technical writing, business analysis, and testing.
Anything else I should tell you all about?