Skip to main content

Screenplays and Requirements

Yesterday I was reding about movies screenplays and found some analogies with writing requirements.

The screenplay must be readable, because filmmakers need to understand
- what they are talking about,
- who will be there,
- how much it will costs
- etc.


It is usually roughly divided in three parts: the set-up, the development, the epilogue (eg. 30, 60, 30 pages)

Many things change before and during shootings: dialogues change, sometimes you shoot a scene at night instead of during the day, etc. so....
"If you don't like changes, then go write poetry". This one rings a bell, doesn't it ?

Also, it will be read by the actors, who will interpret it and change it in some ways.

Comments

Popular posts from this blog

Crash course - 2

Why ? The more I think about it, the more "why" is the word when it comes to requirements gathering. The question "Why ?" has two different meanings: THE PAST : you ask questions to understand the cause, what has happened in the past. THE FUTURE : we ask questions to understand what the user will need in the future, what he wants to do.

"Volere" Requirements process

I found in my library the "Mastering the Requirements Process" book , that some might know as the " Volere " book. After many years I still find it very useful. I don't think the good Robertsons invented anything really new, but I do believe that this book covers 90% of the "how to" solve requirements problems in software development.  And 90% is a lot ! The parts I appreciated more, this last time are: Chapter 12. Prototyping the Requirements  Working together to the prototype, can really take out the users' implicit knowledge, correct lapses and help in many other ways. Chapter 11. The Quality Gateway You could try put an analyst that doesn't work on the same project, to read the project's requirements and have him refuse: all incomplete or inconsistent entries, frills, etc. I think it can be a very powerful practice.