Satyaprakash Joshii

OK.What can be the appropriate category to choose for this task. E. G Coding, Design, Testing. Since a have helped the fresher and guided him on what has to be done and how, I have not actually done coding on his eclipse, so category of coding will now make sense. Whether I have a task like internal discussion with Team member or I use same taskId as the fresher what category should I use out of coding, testing, design etc?  

The reason why I need taskId and task title for those 24-16=8 hours ,is that I need to enter atleast 40 hours in the timesheet. As told above, entering it as "helping fresher.." will solve the purpose. Can I instead create a task like "Internal discussion with team member" or something like "team coordination activities"?

In that case if the fresher has worked on a coding task Task1 for 24 hours in the first 3 days of the sprint, I have worked on Task2 for 16 hours during these days and have helped him from time to time in Task1 (in all 8 hours) so what should my second task title be like (where 8 hours were spent in helping him)?

Suppose "Create database scripts for test data" is the task on which the fresher is working with. If this fresher completes this task in 24 hours and I also have to spend 8 hours from time to time to help and guide him then what should be the title of my task in that case ?

In Sprint I create tasks for myself under user stories such as for design or coding implementation or for unit testing. However when working with freshers a lot of your time goes in helping them. How to create task for such things. I have another question. If a task requires analysis does it come under coding implementation itself?

I will try to do this way. Thank you.

In my previous organization,  we used to write comments in a portal about our feedback (self feedback)  during the year and also we could mention our contributions. Then then the one doing appraisal used to read those, give his comments and the rating. This was better process. In current organization we do not have any such process. We can just give our rating on various parameters like requirement gathering, on time delivery, quality of deliverable and then we get actual rating and final overall rating by them. But we cannot write comments.

For some tasks, I know how to easily break into smaller tasks. However in some cases I do not know this. For. E. g Task-
Coding to parse multilevel nested JSON structure. How do I break this into smaller tasks?

I read that agile tasks under user stories should be such that any task should not be taking more than 1 day?. How to keep them within 1 day when some tasks can be complex and long. For e.g persisting data in database table may be a 1 hour task but parsing multilevel nested JSON structure may certainly more than 1 day?

In our organization,  we are called inside handed over hike letter and at that time a discussion happens as what you wrote above. However when this discussion happen, then hike is already given and nothing can be changed based on the discussion at that point of time as hike is already given minutes before this.

Is it a good way to not remind anything related to appraisal to them and not do anything from your end regarding this and just wait for it, that's all.?

What does that mean that manager will have file to hand before seeing for appraisal?

He would be knowing buy thought he may have been  busy with thousands of works and things might have slipped from mind.

Before the appraisal is it right to send an email on what all good you think you have done in the year. I know the manager would be already knowing but sometimes in busy work he may forget some of the good points. Is it right to put all in an email and send?

We have a team with many freshers. They are working on different work than what I am doing and on different technologies too so often I am not working with them. What is the good way to mentor freshers in the team.