Comments on: I need some advice on project management and how to juggle multiple project so each one is done on time.? http://www.adaptaproject.com/blog/project-time-management/i-need-some-advice-on-project-management-and-how-to-juggle-multiple-project-so-each-one-is-done-on-time Project and Planning Management for the Professional Project Manager Thu, 02 Sep 2010 23:47:42 -0500 http://wordpress.org/?v=2.8.4 hourly 1 By: fremont_guy http://www.adaptaproject.com/blog/project-time-management/i-need-some-advice-on-project-management-and-how-to-juggle-multiple-project-so-each-one-is-done-on-time/comment-page-1#comment-675 fremont_guy Tue, 16 Mar 2010 07:13:59 +0000 http://www.adaptaproject.com/blog/project-time-management/i-need-some-advice-on-project-management-and-how-to-juggle-multiple-project-so-each-one-is-done-on-time#comment-675 I like the previous answer and focus on personal software process. It would be nice to know what type of projects you are juggling with. There is a whole body of knowledge on project management that you can get exposed to. Please check out pmi.org. If you are a project manager by profession, having a PMP and PgMP would definitely help in your career. Good luck!<br><b>References : </b><br>pmi.org pmisv.org I like the previous answer and focus on personal software process.

It would be nice to know what type of projects you are juggling with. There is a whole body of knowledge on project management that you can get exposed to. Please check out pmi.org. If you are a project manager by profession, having a PMP and PgMP would definitely help in your career.

Good luck!
References :
pmi.org
pmisv.org

]]> By: icprofit6000 http://www.adaptaproject.com/blog/project-time-management/i-need-some-advice-on-project-management-and-how-to-juggle-multiple-project-so-each-one-is-done-on-time/comment-page-1#comment-674 icprofit6000 Tue, 16 Mar 2010 06:59:59 +0000 http://www.adaptaproject.com/blog/project-time-management/i-need-some-advice-on-project-management-and-how-to-juggle-multiple-project-so-each-one-is-done-on-time#comment-674 I found that many software engineering and many system engineering development methods can be adapted to other types of projects management . Although it designed for software development, the Personal Software Process and the Team Software Process are approaches to improving software with concepts which can be applied to general projects. Sometimes it pays to be lazy. One of the problems I seen is that people will have slack time (times between projects) where they don't have anything to do, and rather than appear lazy that will take on projects that they can not complete in the time available. that why I recommend that you 1. Don't try and do too much. Avoid overcommitment 2. Don't try and do other people's job. Stay focused on your work. 3. Plan ahead. a. Make sure you will have the resources when you need them b. Set priorities. Make sure you know what REALLY needs to be done. Define your requirements and the required level of performance (QA) know what the job is before you start. 5. Define delieverable, What MUST you deliever at the end of the project. 6. Deliever early and often. If you can not deliever early, demo early. Involve you customer (or boss) in the development project, keep them aware of what going on 7. Track changes, and issues yet to be addressed in your project. 8. A workable solution on time is better than the best solution too late.<br><b>References : </b><br>What is the Personal Software Process http://www.sei.cmu.edu/tsp/psp.html Critical path method http://en.wikipedia.org/wiki/Critical_path_method I found that many software engineering and many system engineering development methods can be adapted to other types of projects management . Although it designed for software development, the Personal Software Process and the Team Software Process are approaches to improving software with concepts which can be applied to general projects.

Sometimes it pays to be lazy. One of the problems I seen is that people will have slack time (times between projects) where they don’t have anything to do, and rather than appear lazy that will take on projects that they can not complete in the time available. that why I recommend that you

1. Don’t try and do too much. Avoid overcommitment
2. Don’t try and do other people’s job. Stay focused on your work.
3. Plan ahead.
a. Make sure you will have the resources when you need them
b. Set priorities. Make sure you know what REALLY needs to be done. Define your requirements and the required level of performance (QA) know what the job is before you start.
5. Define delieverable, What MUST you deliever at the end of the project.
6. Deliever early and often. If you can not deliever early, demo early. Involve you customer (or boss) in the development project, keep them aware of what going on
7. Track changes, and issues yet to be addressed in your project.
8. A workable solution on time is better than the best solution too late.
References :
What is the Personal Software Process
http://www.sei.cmu.edu/tsp/psp.html

Critical path method
http://en.wikipedia.org/wiki/Critical_path_method

]]>