Triple T

Finishing point of task is complex to report; as there is no specific time period to test the application, there is just completion time specified (module end/release date).

If some specified time is likely given from managers, there could be a few minor functional items omitted at that point of time taking in explicit major functionalities alone in the account.

Overall test execution will be specified in days but generally in a module base testing, it will be mentioned only in hours; as it’s easy to track-in. In some cases, the time specified for a module in job card will be adjustable.

If handful functionalities are there then it can be easily analyzed and tested well before the scheduled time. Task estimate is always a recurrence procedure.

In our test estimation, time consumption happens (double the time from the initial estimation) because of slippages (build delays & iterations) from incorrect estimation.

Apart from meetings, a project task is generally estimated half a day (or) a day (or) in hours. I can observe that we all have a pattern to manage our teams but strategy is identical.

Question: So what's "Triple T" ???
Answer: Triple T >>> "Task Taken Time"...

Testing always depends on Task and Time to make a software look like a Triplet...