For years, I’ve worked without thinking much about feature specifications. I had worked in several teams that were reluctant to embrace opinionated methodologies because these were usually tied to specific tools.
So, these teams (and I) stayed in this limbo of empty Trello cards, neglected Jira tickets, and misaligned communication.
But last year, some coworkers and I started iterating on a feature specifications template. Something that’d help us get the ball rolling much faster.
So today, I want to share my template on how to write better specifications for your features.
Here's what you'll find in it:
- Gather all the information you need.
- Never assume. Always make sure.
- Check input, output, and expected behavior.
- Graphs! Charts!! Drawings!!!
- Write your testing scenarios.
Hope you'll find it as helpful as it is for me. 🤞
ps: Hey mods, this is my first post in this community. I've checked the community's rules and didn't find anything against posting one's own content. I really believe this can be helpful, but if you disagree, let me know and I'll adjust. Thanks!
submitted by /u/Remozito
[link] [comments]
from Software Development – methodologies, techniques, and tools. Covering Agile, RUP, Waterfall + more! https://ift.tt/MucsalJ