loading...

re: How do you write requirements? VIEW POST

FULL DISCUSSION
 

I have worked in all kinds of organizations over the years, and used many different requirements formats, the most structured of which went from strategic product definition (market input, competitor analysis, etc) to formulate meta-epic definitions, through to Jira as a Project and then into actual epic-story-task structures with increasingly refined requirements at each level. It provided amazing tracibility at the sacrifice of time investment up front.

I've also worked in very informal, iterative environments (such as my current employer) where requirements usually start in a meeting or a sales call, then come in through a helpdesk ticket, and refined into a development ticket in VSTS (soon to be Gitlab) and then acted upon, with several rounds of interaction with internal and external customers to refine concept and implementation.

I prefer that internal customers do some level of requirements definition with at least a minimal amount of expectation/requirement, as it gets them thinking about what they really want, and gets them engaged with skin in the game early. That approach needs to be supported by the culture which unfortunately my current environment does not. We may get there over time though as we are going through a sea change in tech leadership right now.

Regardless of tool, I prefer to get everything I can captured in the project wiki, where ever it resides, both for current use and future maintenance.

Keep posting Dylan - This is an old but ongoing issue in every organization and we all need to tip over those stones regularly and get rid of the worms and lizards living underneath!

 

Thanks John!

At my current place of work we’re still trying to find a solution that works for us. We don’t have a dedicated project manager or BA yet (been searching for around a year now). This means that us developers are left to our own methods for deciding what we write.

I’m still a very young developer, but I’ve seen us make the same mistakes enough to know we need some structure. I’m hoping to come up with some sort of system that gets us more correct information about what we’re building without being so burdensome that no one does it.

Not an easy task 😅 but a worthwhile goal I think.

Code of Conduct Report abuse