|
The following is true for custom solutions:
- Being late is bad for business, having small bugs is acceptable if you show you are fixing and releasing often.
- Having a "working" software is a necessity, by working we mean getting the basic job done.
- Implementing the full feature set in the initial release is not cost/time effective as the users will generally only use 70% of the feature set anyway.
Its the man, not the machine - Chuck Yeager
If at first you don't succeed... get a better publicist
If the final destination is death, then we should enjoy every second of the journey.
|
|
|
|
|
No,most probably it should not is not possible to release app bug free in its first version (IMHO).
so i am going with to provide planned features and it should be the first preference from my point of view.
modified 14-Nov-11 2:17am.
|
|
|
|
|
Pritesh Aryan wrote: it is not possible to release app bug free in its first version
Yes it is!
Why should the first version be any more prone to bugs than any other version? If you can ship V2 bug free, then you should be able to ship V1 in the same condition.
Admittedly, it rarely happens, but that doesn't mean you can't aim for it.
Saying "it is not possible to release app bug free in its first version" is just saying "I can't be bothered to test this properly - let the users do it"
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
|
|
|
|
|
ok,..i should have to use word probably i think.
actually English is not my first language so i can't express my exact ideas or views over here .
modified 14-Nov-11 2:47am.
|
|
|
|
|
Yep!
(I dunno who downvoted you, but since it is modified, I have compensated)
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
|
|
|
|