I believe there are six steps to project/task scheduling.
1. Plan Schedule Management - Define policies, procedures, and documentation
2. Define Activities - Work Breakdown
3. Sequence Activities - sequence of work
4. Estimate Activity Resources - resources such as labor, tools, facilities, fixed cost items
5. Estimate Activity Duration - estimating the number of work periods
6. Develop Schedule - develop a schedule to analyze sequences and resource requirements

I agree with the 6 steps outlined by moniquet07. I would just like to elaborate on the importance of the PM developing the the task scheduling with input and feedback from the resources who will be executing the tasks. The PM often does not understand the specifics of what exactly is required for task completion, and therefore they will not be able to accurately estimate the amount of time that each task will take without getting this input directly from the team members responsible for each task.

Going off of what srg36 said in response to moniquet07, I think the project scheduling would need a "Clarification" or a "Agreement" step. This way all parties know what they are up against, and if something is not correct (either time wise or design wise), the PM can make adjustments. And with any schedule, you I also think it should include the "execution" phase where the project actually begins production and "updates" where they make sure they are on track with their predicted schedule.

I agree with Monique that those are the necessary 6 steps to the project/task schedule. However, I do believe that other steps should be included. There should be another Risk Analysis step because there could have been a lot of changes that occurred in between processes that could have changed the project. The step should outline what risk are still relevant from the predetermined risks list and what new risk the project had incurred. In addition, the schedule should be devised knowing about what risk could happen in order to develop an accurate time table of the project. I agree with f-dot that there should be an update phase so they can adjust the time line of their project. Also, changes that happen could affect other parts of the project and can affect their time line and efficiency and it is important for all groups and members of the project to communicate so that there are not delays from unknown changes.

I agree with f-dot and msc52 about the suggestion of adding an "Updates" step to the steps of project scheduling. This allows for the project manager to be aware of any potential delays to the original timeline, and will allow him or her to be able to communicate to the other members of the project team who may be affected by it. I came across this when one of the tasks that I was assigned was dependent on the completion of another task by another department. The completion of their task was delayed because the resource that was assigned at the beginning of the project left the company and was never replaced. The project manager was not made aware of this until I was ready to begin my task, and had to push the other department to provide the necessary resource that they committed to. By adding an "update" step, these kinds of situations can be avoided.

I agree with the discussion above . I would like to mention that we need a use the tools for scheduling. Instead to making a false things that you can schedule it by your own skills. We need to use the project management tools for project scheduling or task scheduling.While scheduling we need to understand the priority . What task is depends on the other? What need to be performed first. It can be well understood by laying out the project step by step using a task scheduling tools like Gantt chart.

I agree with the steps mentioned above for managing a project. I would only emphasize on how important to keep a record of everything and keep the document up to date and to follow up to make everything is going as it suppose to be. one member delay can cause the whole team to fail. While the simulation, we might not need that as we only 5 members and project is only for a week. So, we don't have a lot of factors can go wrong. However, In a real work environment, things can get much more complicated. So keeping a track of every single detail can save a lot of problems later. Also, It helps to better risk manage the project.

I Agree but the first step should always be understanding the scope of the project because without that you will find new components that need procedures or additional tasks you didn't account for. The step should also have some form of feedback as mentioned above since feedback is the key to success. Only after defining the scope and consulting the necessary individuals can you begin with the steps mentioned by moniquet above. And those steps are usually not all done by the PM but are managed by the PM and other employees actual make them such as the procedures or estimates. Also many of the steps require inputs from qualified personnel or consultants within the company such as finding dependencies. As a PM you are not required to have a PhD in molecular chemistry if you are managing a research project for a new tissue engineering scaffold but you need to have a consultant that is knowledgeable enough to define certain aspects that are out of your expertise.

I agree with everything that is said above. In addition, I think there should be a re-evaluation step which happens once the project has started to make sure that the way everything was planned is working out and that nothing needs to be changed. For example, during re-evaluation it may bring to attention that there was too much work put on the resources and the team needs people or that the work breakdown needs to be adjusted. No matter how well-planned out something is, things can always go wrong and by planning a re-evaluation step on a specific date, small problems can be caught and adjusted before they turn into large problems.

The project management schedule is a document that outlines what work needs to be done, the order in which it needs to be done, what resources are required, how they will be distributed, and how long different parts of the work will take. The schedule helps project managers communicate and collaborate with team members and stakeholders, and keeps the project on track.

More specifically, a project schedule covers:

Project milestones
Deliverables
Tasks required to complete the deliverables
Dependencies between tasks and milestones
Resource requirements and allocation
Deadlines, time frames, and task durations

Essential steps for creating project schedule:
1. Hold a brainstorming meeting.
2. Determine clear, measurable milestones
3. Create a WBS that includes all project deliverables.
4. Outline and sequence all tasks/activities.
5. Define the critical path.
6. Estimate task duration.
7. Estimate resources.
8. Note assumptions
9. Determine and document risks.
10. Review and revise schedule.

Unforeseen occurrences are should be factored in with task scheduling. If a schedule is too tight then any delay will cascade into other tasks which depend on the initial task. This will in turn cause those tasks to be delayed, and so forth. In order to help with this task duration should be established with considerations in place in case of any delay that may occur.

Posted by: @aasutosh-purohit

we know that in Project scheduling or task scheduling, the following are the steps needed:
Defining Activities, doing proper Estimates, determining Dependencies and assigning Resources. According to you guys, are there any other factors that need to be added to these for the task scheduling?

Although these factors are important in project scheduling, planning schedule management is an important step to do before actually defining activities. During this phase, how the schedule will be developed, who to notify in any situation, how intense the project will be, and what actions will be taken if the project gets behind are a few of the things that are discussed. After defining activities, arranging activities, and estimating resources and durations, the last step that was not mentioned is developing a schedule. This includes five tasks: creating the network diagram, determining critical paths and floats, drawing the initial Gantt chart, performing resource levelling, and if necessary, compressing the scheduling. Overall it is also important to create a schedule using the resources that are available. 

Reference:

“Develop Schedule.” ProjectEngineer, 7 Jan. 2016, www.projectengineer.net/knowledge-areas/project-time/develop-schedule/.