What is lessons learnt document?Explain.
- 6 Answers
- 11469 Views
- Infotech, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / rahul petare
Lessons learnt document is a document generated as a
feedback for the client and the vendor. This clearly
explains the functional issues that came along in the
project and how they could have been avoided.
It gives details on some of the new practices followed
which were successful and cost saving so that they can be
used in future.
In short this document should provide a guideline so that
the same problems do not get repeated for the next project.
| Is This Answer Correct ? | 9 Yes | 0 No |
Answer / anil
In brief Lessons Learnt are usually the DO's, which proved
us wrong and eventually turn out to be DON'Ts for the next
assignments.
| Is This Answer Correct ? | 5 Yes | 3 No |
Answer / naveen bt
Is a document at the end of project phase. this explains the
various pains the team had to undergo and how and what they
did to resolve the issues. This document also serves as
knowledge sharing between projects.
| Is This Answer Correct ? | 3 Yes | 1 No |
Lessons learnt document is nothing but base document
Those may be URS/FRD
or use cases which makes u To learn about the application
| Is This Answer Correct ? | 5 Yes | 5 No |
Answer / jaya
This is the document drafted by the team members at the end
ot the project phase. This document mainly speaks about the
challenges faced and the lessons learnt from the project.
Ex:the docuemnt contains like i learnt from the project How
to be good team player and How to be an assertive perosn ,
some thing like tat.
| Is This Answer Correct ? | 1 Yes | 1 No |
Answer / gopi
This is not answer, pls send me example document for this.
| Is This Answer Correct ? | 1 Yes | 2 No |
what is difference b/w Quality assurance & Quality control
How will you Test a Website manually?? Tell me any 5 different ways to Test a Website.
pls explain company testing process in detail (if anybody working as a test engeneer)
8)What is the actual need for an alpha and beta testing? A)For the developers it is impossible to predict how the end user with really use the application B)Misinterpretation of instructions for using the software C)End users may use strange combinations of input data D)All the above
Why are initial and end conditions necessary?
What should be done after a bug is found?
How many members can write the single test case?
I would like to know about the steps to follow for testing a .NET web application. Please provide detailed steps with more general scenarios.
How do you go about testing a web application?
what types of bugs will we find out in banking projects
What is parallel Testing?
How to prepare boundary value test cases for 3 input values eg: to get the triangle type i am giving 3 sides a, b, c values should be 1<=a<=200,1<=b<=200,1<=c<=200....
Automation Testing 
