[ cyb / tech / λ / layer ] [ zzz / drg / lit / diy / art ] [ w / rpg / r ] [ q ] [ / ] [ popular / ???? / rules / radio / $$ / news ] [ volafile / uboa / sushi / LainTV / lewd ]

lit - literature

Name
Email
Subject
Comment
File
Password (For file deletion.)

BUY LAINCHAN STICKERS HERE

STREAM » LainTV « STREAM
Ok, who did it?

[Return][Go to bottom]

File: 1445541654017.jpg (108.63 KB, 900x882, a95c89e7133b41aa3998220ab9….jpg) ImgOps Exif iqdb

 No.2266

I've found out that FLOSS Manuals writes their manuals using a method called "book sprint". They collect a group of experts, sit them down, and declare that they have 3 or 5 days to write the manual. Apparently it's some agile way to documentation.
They also claim it works for non-technical literature, too.

They did an EU project on it:
http://booksprints-for-ict-research.eu/index.html%3Fp=26.html
"On Book Sprints" describes the whole process, look for the patterns section.

What do you think? Is this a good idea?
>>

 No.2268

It sounds similar to some technique I've heard is often used in startups. I think it's called design sprints. They'll spend one day brainstorming ideas, next day building quick rough models of the ideas, third day bring in testers and get feedback, then use that feedback to go back to the drawing board and repeat the process 2-3 times.

>>

 No.2270

>>2268
yeah it comes from Agile (ie. Scrum) as OP hints at. i hate this sort of soykaf so much personally though i can understand it's uses.



Delete Post [ ]
[ cyb / tech / λ / layer ] [ zzz / drg / lit / diy / art ] [ w / rpg / r ] [ q ] [ / ] [ popular / ???? / rules / radio / $$ / news ] [ volafile / uboa / sushi / LainTV / lewd ]