|
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. What I'm asking is, I guess, do you guys have any thoughts regarding requirements engineering? Do you have tips on what to read up on regarding the position in general and the writing of user stories in particular?
|
#
¿
Feb 3, 2016 15:06
|
|
|
|
| # ¿ May 8, 2024 04:53 |
|
|
Thanks for these, managed to get the first one ordered through the company and bought the other one for myself. Tremendous help in getting a grip on the theory. Messyass posted:I'm officially a Requirements Engineer as well. The position is in a bit of weird place nowadays because it's not like the role exists in Scrum or anything. Ideally you'd have the developers talking to the PO and other domain experts directly anyway. It's weird since I'm not really part of the whole Scrum-Framework and basically get to do a little bit of everything wherever it helps. What I am trying to do is correlate information, get the right people talking to each other and deliver whatever information the developers need post-haste. At the moment I'm struggling with getting the right information out of huge technical spec documents and translating it into bite-sized pieces the developers will understand. This will take time I reckon. volkadav posted: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). Thanks for the feedback! 1) I made a push to tidy up the language used in our user stories and actually creating something akin to understandable acceptance criteria. I got a general sense for UI and UX when I was dabbling in Game Studies academically but I could definitely use more knowledge on that front. 2) I've been playing around with Balsamiq and did some test wireframe concepts, I really like to program. A little Mockup really goes a long way in making a concept understandable. 3) I've been trying to wrap my head around how our stuff works as quickly as possible. It's hard to really get into the code and deeply technical stuff but yes, it helps tremendously to be at least competent at the most important user interfaces and whatnot. It'll be a long while until I can make sense of any code. 4) I'm trying not to get in over my head and just improve step by step. It's a steep learning curve but yeah, I feel up for it. At least for the moment. Famous Last words right here.
|
|
#
¿
Feb 16, 2016 19:51
|
|
