I draw thoughts from the books I have forgotten,
Trying to justify myself before God,
But what if I can confess,
In co-authorship of swirling intrigues.
When you are just starting to develop a software product, there is a temptation not to write the TOR and quickly sketch out the product mockup, which was discussed "last Monday."
The development team is still small and everything can be discussed without leaving the table.
If luck smiled and the product turned out to be in demand, then it should already be tested to be rejected from the developers.
We invite a tester to the project, and if fortune is our face again, the question is inevitable: on what basis to test?
Tomorrow there is a similar question from a technical writer: How does a product have to work in order to describe it correctly?
And now, ATTENTION, the main question!
How to fix the requirements for a product in conditions when there is no technical specification for the final product, because no one yet knows what will eventually be included in it?
, , , .
, . .
agile .
. .
, , .
. , . . . , . .. .
. - , . , . , , , API, … . . , , .... . . . .
, , . . .
, . . , . , . , , . . , , . . , , .
… , .
, , . . . . , , , , , , .
: , , …
. , , . TDD (Test Driven Development). , , . , , . – . , . . . , , . / . CI (continuous integration). , . , ... .
- Why you call this version “beta”?
- Because it’s betta than nothing