|
Fluegel posted:I was recently hired as a Requirements Engineer at the frontend branch of a software development company. I have about as much IT-knowledge and experience as your average goon and a humanities degree with a professional background in media and journalism. I cannot write a line of code to save my life. My main task will be to work with the PO and produce good user stories. My team more or less uses Scrum and they aim to follow it more closely. I`m in for one hell of a ride. Take this with a big grain of salt, as I've never been fortunate enough to work in a place where there was someone dedicated just to writing decent specifications (which are ... wonderful when you have them, speaking as an engineer).  1) In addition to user stories, since you mention being in a frontend group, consider reading up on UI / UX in general (if nothing else, you'll be a good sounding board for the PO that way). I'm a backend engineer and sometimes ops person so sadly I have no specific references to books or whatever to give here. 2) As part of UX, on top of textual user stories, consider whiteboarding / wireframing tools to give visual guidance as well. Sometimes a picture's worth a thousand words. What does the user see when they do something? Literal pencil-on-paper-scanned-in can work here. I've also heard good things about Balsamiq, fwiw, but have not used it (see above re: being a backend nerd). 3) It wouldn't hurt to dabble a bit in how this stuff is done; you don't have to be a developer, but it helps to have some fluency so you know better what is in (and out) of the realm of technical feasibility. Nobody was born knowing any of this, we all learned somehow. 4) Don't panic! Your background has already prepared you for the crucial bit of translating/recording things in one domain for an audience in a different domain. You'll definitely have a learning curve but ... as mentioned, everyone has to start somewhere.
|
#
¿
Feb 12, 2016 20:41
|
|
|
|
| # ¿ May 9, 2024 00:11 |
|