S
skier9er
Can someone explain the difference between Production Scheduling vs
Development Scheduling?
Thank
Development Scheduling?
Thank
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
J
Jan De Messemaeker
Hi,
Few expressions are as ambiguous as "Production Scheduling"
In many companies, Production is a repetition of identical processes (say
you assemble 10000 cars).
This is hard to simulate with a project-oriented (and I mean project like in
project management, not necessarily the product Project).
On the other hand, companies that produce complex, built-to-order stuff
(typically prototypes or customized goods) have a scheduling system that is
very much project planning, because your work has all the properties of a
project (unique, a distict end, budget, limited resources, you name it,
we've got it): scheduling this kind of production is very similar to
application development (I suppose that is what you mean by development - if
not I can comment). The main difference is often that classical scheduling
techniques work BETTER for this production because durations and work
estimates are generally better known (like machine speeds).
That is my experience... insofar we understand the words "Production" and
"Development" teh same way!
Greetings,
--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
+32 495 300 620
For availability check:
http://users.online.be/prom-ade/Calendar.pdf
Few expressions are as ambiguous as "Production Scheduling"
In many companies, Production is a repetition of identical processes (say
you assemble 10000 cars).
This is hard to simulate with a project-oriented (and I mean project like in
project management, not necessarily the product Project).
On the other hand, companies that produce complex, built-to-order stuff
(typically prototypes or customized goods) have a scheduling system that is
very much project planning, because your work has all the properties of a
project (unique, a distict end, budget, limited resources, you name it,
we've got it): scheduling this kind of production is very similar to
application development (I suppose that is what you mean by development - if
not I can comment). The main difference is often that classical scheduling
techniques work BETTER for this production because durations and work
estimates are generally better known (like machine speeds).
That is my experience... insofar we understand the words "Production" and
"Development" teh same way!
Greetings,
--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
+32 495 300 620
For availability check:
http://users.online.be/prom-ade/Calendar.pdf
V
vanita
Hi
It depends in what context you are looking at these two terms.
Even in same project,whether it is a construction project, product design
and production project like in automobile industry or a service project like
an advertisement project, the design stage will have a 'Development schedule'
and the execution stage or the production stage would have a 'Production
schedule'. Both the schedules would have some linkages and would not be
standalone.
I hope it helps.
Vanita
It depends in what context you are looking at these two terms.
Even in same project,whether it is a construction project, product design
and production project like in automobile industry or a service project like
an advertisement project, the design stage will have a 'Development schedule'
and the execution stage or the production stage would have a 'Production
schedule'. Both the schedules would have some linkages and would not be
standalone.
I hope it helps.
Vanita
H
Hardip
If your developing a new product (or service) then you'll have a defined
start and finish date for releasing the new product. Development tends to be
interative, involves building/designing individual components of the product,
testing, rework, documentation, support methods, implementing new processes,
training, end user comms etc whilst aligning to the project and technical
governance to ensure all deliverables meet acceptance criteria prior to
release into production. All of these items have to be scheduled as part of
the project.
Once released into production then the standard ways of producing a product
take over that either exist in the Operation or your project has implemented
these prior to release. For example, your production schedule will not have
designing a product as part of the schedule components unless your in a
specific industry (I guess). Most production schedules focus on fulfilling
the order book.
In my experience I'm yet to see an organisation use MS Project to do
production scheduling and will deploy some type of integrated ERP tool/system.
There's no right answer to this one. Hope this helps regardless.
Hardip
start and finish date for releasing the new product. Development tends to be
interative, involves building/designing individual components of the product,
testing, rework, documentation, support methods, implementing new processes,
training, end user comms etc whilst aligning to the project and technical
governance to ensure all deliverables meet acceptance criteria prior to
release into production. All of these items have to be scheduled as part of
the project.
Once released into production then the standard ways of producing a product
take over that either exist in the Operation or your project has implemented
these prior to release. For example, your production schedule will not have
designing a product as part of the schedule components unless your in a
specific industry (I guess). Most production schedules focus on fulfilling
the order book.
In my experience I'm yet to see an organisation use MS Project to do
production scheduling and will deploy some type of integrated ERP tool/system.
There's no right answer to this one. Hope this helps regardless.
Hardip