I would love to start, but I don't
know where. I looked at Microsoft
Project, but it's confusing.
It's not confusing at all! Just start MSProject (or the software of your election, many of my colleagues still prefer MSExcel) and write this:
My Project
Under that task create the followings:
Interation N
Define Requirements
Design
Construction
Test
Deploy
Don't worry about estimation at first. At first you must do the breakdown of work creating as many task as you need to make your point. Usually, a tasks that last less than two days isn't worth mentioning.
Split your project in various iterations.
All this work of planning is based on previous experience. If you don't have the experencie, ask for required tasks to get a deliverable and ask for an estimation.
When you get a sufficient granularity of tasks, and everyone estimated, make sure to register the dependencies between tasks (you can't start testing comm. classes until comm. classes get constructed)
Assign resources (programmers, users, testers) to every tasks adjusting estimations accordingly (at first MSProject assume a task of 10 hours will get completed in 10 hour by a person, but in 5 hours by two people; when everyone knows it will take 12.5 hours for two people. Resolve overwork. Consider holidays.
Now you get a perfect plan of your project. You know what will be doing everyone everyday, and you know the exact day when the project ends.
Now is time to redo everything again. Because a plan is a map for a flooding river and you'll have to redo it frequently.
But look: that Gantt Diagrams looks so pretty! Your Mama will be proud of you.
Besides that, you'll have the power to foresee how much delay will be introduced if someone decides not to work for a week. You'll have also the power to see what thinks can be reorganized to reduce the slippage from a month to only 3 weeks and 2 days.
Enjoy!