3 ms·
> I promised a better way... a well-written 8-page document can define the nuances of a complicated system far better than a whole cumbersome flotilla of interl
by crazygringo 10y ago
> I promised a better way... a well-written 8-page document can define the nuances of a complicated system far better than a whole cumbersome flotilla of interlinked JIRA tickets.
I'm mystified... everywhere I've ever worked used design documents to some extent -- not for simple features, but more for things that are truly "complicated systems" with nuances.
Are there really places that attempt to do project design solely with tickets? I almost can't believe it.
(Although in terms of effort estimation, breaking the design doc down afterwards into tickets, and then estimating those individually, is a very useful exercise -- a design doc describes the outcome, the tickets describe how to get there, which is what you're really estimating.)
- pat2man 10y agoAtlassian themselves even has a tool for this: Confluence. Then then integrate with JIRA for individual tickets. https://confluence.atlassian.com/doc/develop-technical-documentation-in-confluence-226166494.html https://confluence.atlassian.com/doc/develop-technical-docum...
- fiftyacorn 10y agoIts a recent trend to skip the documentation and have a sparsely documented JIRA in the belief it encourages agile development. I just groan when i see it
- tetraodonpuffer 10y agothere is also the "let's define everything by user stories" way of doing things (as if having a bunch of stories in whatever agile tool is better than a proper functional spec / design spec)
- goalieca 10y agoA lot of agile shops seem to be doing this.