I am working in software industry with more then 10 years now and have worked in capacity of developer and team lead too.
From perspective of team lead estimates provided by the team for the tasks to be completed are something which any TL doubts.
You can have confidence on estimates only when you have detailed understanding about changes to be done at what level.
Once who is working with a system for a long can give a real detailed estimates
1. What would be the change in Database level like stored proc or tables?
2. Changes at Business logic classes
3. Changes in Business entities
4, Changes in front end controller
5, Change in Models and Views.
6. Unit testing
7. Executing test cases written by test team.
All this constitutes estimate of a task
1. Create a traceability matrix for requirements, Clearly mention requirement number and mention the comment in the code mentioning the requirement detail so that it is easier for the person who reads the code.
2. Database document is very important to create which clearly shows which table stores what and that knowledge helps to understand application.
Beware of the test team some times test team goes overboard in the way that they might want to get features done in their way which they think is correct so one needs to be cautious for the bugs which they mention whether they are saying some thing inscope of the project or out of scope.
From perspective of team lead estimates provided by the team for the tasks to be completed are something which any TL doubts.
You can have confidence on estimates only when you have detailed understanding about changes to be done at what level.
Once who is working with a system for a long can give a real detailed estimates
1. What would be the change in Database level like stored proc or tables?
2. Changes at Business logic classes
3. Changes in Business entities
4, Changes in front end controller
5, Change in Models and Views.
6. Unit testing
7. Executing test cases written by test team.
All this constitutes estimate of a task
1. Create a traceability matrix for requirements, Clearly mention requirement number and mention the comment in the code mentioning the requirement detail so that it is easier for the person who reads the code.
2. Database document is very important to create which clearly shows which table stores what and that knowledge helps to understand application.
Beware of the test team some times test team goes overboard in the way that they might want to get features done in their way which they think is correct so one needs to be cautious for the bugs which they mention whether they are saying some thing inscope of the project or out of scope.
No comments:
Post a Comment