|
Ashutosh Trivedi
Project Manager, India
|
How to Convert a Project into a Road Map for Product Development?
Please suggest me: we started a project and successfully implemented it for two different customers and at two different sites. The project is now implemented and we want this to be converted as a product. If you people can suggest that what should be the road map for a project to product and other issues I have to look at?
X
Sign up for free
Welcome to the Program and Project Management best practices of 12manage.
Here we exchange knowledge and experiences in the field of Program and Project Management.
❗Sign up now to gain access to 12manage. Completely free.
X
Continue for free
Please sign up and login to continue reading.
Here we exchange knowledge and experiences in the field of Program and Project Management.
❗Sign up now to gain access to 12manage. Completely free.
| |
|
|
| |
|
mursal bashir, Kenya
|
|
Road Map for Product Development How about identifying honest expert collaborators that you can trust with details of what you want to do. This should give you insight on the way forward.
|
| |
|
GS RADJOU
CEO, France
|
|
Road Map for Product Development As you comment is very general and it is looking like you are simulating something. I cannot go into details with you. Anyway, I have a couple of options (and maybe more...)
I give you one now-you may test it-.
As I understood, you want to convert your project into a product. Two options:
+ You work with a couple of specialists, they give you steps to follow.
+ You organize a meeting, invite all stakeholders, let them work on the solutions in a free manner, but you need to provide them with the materials for reflection / some tracks and/or development goals.
|
| |
|
Charles Nainggolan, Canada
|
|
Road Map for Product Development First you have to make sure to pass all the tests that required on the project level.
The next step will be production trial, evaluate the result before the real production process such as machineries, human resources, supply chain, regulations and codes of conduct, etc.
|
| |
|
Dirk Schaele
Management Consultant, Belgium
|
|
Road Map for Product Development What would you gain by turning your project deliverable into a product?
Would you be able to increase your efficiency (time, cost..), time-to-delivery, quality, revenue, knowledge?
|
| |
|
Charles Nainggolan, Canada
|
|
Road Map for Production Of course you can.. I suggest you to use the lean manufacturing system to evaluate what you are asking about. For efficiency, you have to increase productivity by appling automization and provide skilled workers, avoid downtime, apply just-in-time inventory system, avoid reworks, all individuals understand about the quality on their phase.
|
| |
|
GS RADJOU
CEO, France
|
|
Road Map for Product Development The builder paradox or quality triangle (cost, speed and quality) tells one cannot have all the angles of the triangle right, but only 2 at the same time. Either you get the speed and the quality right so, it is an expensive project. If it is slow, not a good quality project, so it should not be expensive... etc.
|
| |
|
Umer kayani
Project Manager, Pakistan
|
|
Road Map for Product Development Identify the customer needs and their satisfaction level.
|
| |
|
GS RADJOU
CEO, France
|
|
Customer Needs and Satisfaction Levels Indeed: are the customers happy? Does the company have a policy to monitor quality assurance? Customer needs and satisfaction are normally present in the project deliverables - usually in written form.
|
| |
|
Charles Nainggolan, Canada
|
|
Road Map for Product Development A project is the organization of a new idea, and the project must be proceeded and converted to become an operation. This is what we call a "road map".
Steps that we have to do in the project stage: new idea, analysis, design, test, and deployment.
Identifying the customer needs should also be part of the project stage, since the customer satisfaction should be part of the operation.
|
| |
|
Franky He, China
|
|
Well Define Criteria of Input and Output As my understanding, the criteria of input and output should be defined well at at each planning stage.
What you should do is to lead project team to work on it and go together with your target as project progess, and have a record to show how project is going with target.
Finally, when you will transfer the project into a mass product, create a summary of the project status and share them with all stakeholder, the stakeholders will tell you whether to move into a mass product or not, bases on the information that you provided.
|
| |
|
mursal bashir, Kenya
|
|
Criteria and Measurement Tools Yes, what gets measured gets done, therefore what needs to be done must be prescribed from the beginning with specified requirements, standards and targets set and the tools of measurement must be agreed upon.
|
| |
|
BURLEREAUX, France
|
|
Release Management And next question is how to smoothly aggregate projects / product evergreening into the release road map, and ensuring a good transition into production.
|
| |
|
PATRIK MARIEN
Consultant, Belgium
|
|
Road Map for Product Development Look for tangible things (object, model, proto) that can perform (know the acceptance criteria) to test (prove) how close you are to the final goal. Set the tangible things in a timeline and organize to act for getting the objects [model-object-test- driven]. Keep focus on the object (especially when thing go wrong). Do this for products, technology, services.
|
| |
|
Umer kayani
Project Manager, Pakistan
|
|
Three Levels There are three levels (steps)
A/ level of customer needs and satisfaction.
B/ feasibility level.
C/ consistently testing system.
|
|
Log in
Comments by date▼