Exit criteria

So did you determine your exit criteria for working project?

If you did then what is the base? Time, Budget or Context?

Something did you forgot? What about Maintenance testing?

So you are not assigned for it? Not in the Requirement? Not your job?

Think, think reasonably, think once again. From my experience the finest bug's came from customers, after deployment. Bugs which are really tough to think of, very much functional and realistic. Bugs which are delicious for Programmers to fix. Those bugs can build a very strong reputation in your carrier. But those visions came from experience. Experience with a good eye, reasonable mindset and with a lots of notice points. Remember if you are not noting down something very interesting facts of your application then 70% chance is there that you will do the same miss again. So, very careful about your exit criteria may be its out of spec but it is in spec for your knowledge. To grow your knowledge, and it will be big plus in that context application.

P.S
- Keep an eye on your tested software, know its behavior and cause of unexpected
- Must must must note it down, or may be it will lost in your complex brain