I'm looking for consensus for one or the other
Beta; Release software with a limited audience and allow users until the application is complete.
No beta; Determine all the functionality based on previous user reviews and / or business logic, software and check it for the time you give yourself (or give).
Hmmm ... Beta for a product that you think is complete ... until you let Beta users play with it and they break it the way you didn't think. <sh> So yes, go with Beta if you don't want to record your product to many users.
I do not agree with both cases.
What about internal QA? You know, they find mistakes too. Only release beta to customers if you don’t have known serious bugs.
Also, always check adequately. If time is pressed and you have not finished all your tests, then it is simply difficult. Complete the test whether you have time or not.
, , , :
1) . , , - . - ? , , , - , , -.
2) . , -, "-"? , , .
3) . - , , ERP, 101 , - , , , .
4) . -, , , - , .
5) . , -, , , - . , , .
, , , -, - .
, !
-...
.
, , , . , , , "Release Early Release ".
: , ?
"", -.
"", , Beta - - , .
. . -. , Beta, . , , .
. . , , , , .
-, , , , .
, , , , , , - .
, (1) .
( ) , , -. , .
-, , .
-, , . - . . , - , , - , , . , - .
As for the second option - if you are not an extraordinary tester, you will not be able to test it, as well as end users (they will do the most stupid things for your software). And if you “check this with any time you give yourself (or get),” you will not have enough time.