What about the project management itself?
Like, how do you provide a scheme that takes control of how much time we need to use up? What can I do to extend my original 6-weeks scheme into a 50-weeks scheme?
If a group of people wanted to do a project, and keeping the software part out (programming, version controlling, etc.), and wanted to plan how the work force, what work should be done, how the work is like, and how long the total amount of work should be done by the time that group is about to reach a deadline, shouldn't they start off with a plan/scheme/something that the group members can rely and work without worrying about what should be done next?
I am grasping that little concept of project management. I hoped that I can get more from this.
EDIT:
@Tom Sloper, do you mean (after reading your post for the third time), you want me to read both of the books' chapters (Production chapter and Foreword)?
EDIT 2:
@Telastyn: Do you mean on how I should develop my plans instead of what they are? When it comes to developing a plan, what are the key aspects if you're starting out from scratch? Do you start from the beginning of the project or from the end? What did I miss out? Thanks.
Show differencesHistory of post edits
#1tom_mai78101
Posted 21 January 2012 - 12:34 PM
What about the project management itself?
Like, how do you provide a scheme that takes control of how much time we need to use up? What can I do to extend my original 6-weeks scheme into a 50-weeks scheme?
If a group of people wanted to do a project, and keeping the software part out (programming, version controlling, etc.), and wanted to plan how the work force, what work should be done, how the work is like, and how long the total amount of work should be done by the time that group is about to reach a deadline, shouldn't they start off with a plan/scheme/something that the group members can rely and work without worrying about what should be done next?
I am grasping that little concept of project management. I hoped that I can get more from this.
EDIT:
@Tom Sloper, do you mean (after reading your post for the third time), you want me to read both of the books' chapters (Production chapter and Foreword)?
EDIT 2:
@Telastyn: Do you mean on how I should develop my plans instead of what they are? When it comes to developing a plan, what are the key aspects if you're starting out from scratch? Do you start from the beginning of the project or from the end? What did I miss out? Thanks.
Like, how do you provide a scheme that takes control of how much time we need to use up? What can I do to extend my original 6-weeks scheme into a 50-weeks scheme?
If a group of people wanted to do a project, and keeping the software part out (programming, version controlling, etc.), and wanted to plan how the work force, what work should be done, how the work is like, and how long the total amount of work should be done by the time that group is about to reach a deadline, shouldn't they start off with a plan/scheme/something that the group members can rely and work without worrying about what should be done next?
I am grasping that little concept of project management. I hoped that I can get more from this.
EDIT:
@Tom Sloper, do you mean (after reading your post for the third time), you want me to read both of the books' chapters (Production chapter and Foreword)?
EDIT 2:
@Telastyn: Do you mean on how I should develop my plans instead of what they are? When it comes to developing a plan, what are the key aspects if you're starting out from scratch? Do you start from the beginning of the project or from the end? What did I miss out? Thanks.