[PNewling]

>Perhaps these are becoming a relic of a lost era? Paper is too much of an "air-gap" when everything is done on computer. Moreover, the standard 2-week Agile "sprint" leaves no time for careful thinking and writing. One can't put epiphanies gained from writing up notes into "the deliverable" for a freaking Jira Ticket

So, I get what you're getting at here (I think), especially as someone who came from research labs and then moved into computer science, but teams should be building doco into the tickets and pushing back on anything that doesn't have some meaningful documentation built in.

Easier said than done in some organizations, I know, but I still think we need to be the ones to push back.

[crispyambulance]

Yeah, it depends on the team.

FWIW, some do structure a "data review" state prior to closure of a ticket where the deliverable is some type of report (often with a presentation). Obviously, this can't be done for every ticket but it's appropriate for periodic "capstone" tickets.