Agile PLM Configuration or Customization Efforts – Estimation
Appreciate if anyone could share or direct me to an estimation approach (or tool) in sizing the effort (hours) for implementing Agile PLM in general (across each or all of its modules).
Bottom up, top-down approach or guidelines are all welcome and would be helpful right now.
That’s a fairly broad question. There are so many things to consider (just a few);
On-prem or cloud?
What version if on-prem?
How many locations and where are those locations?
Are you integrating CAD?
Do you have dedicated technical resource?
Are there any data integrations?
What’s the size of the legacy data?
Will there be data cleansing efforts?
Is this a lift and shift from an existing change management system?
If not then training will be a longer path.
Are we looking at process review and best practices?
How many workflows?
How many subclasses?
How many NPI templates do you have (major, minor and change)?
This is just not an easy question to answer until a deeper dive. A partner can come in and easy indicate a 9 month project for PC alone yet once you dive deeper into the scope and requirements that could easily stretch to 12-18 months.
PQM also depends on the scope and requirements of the Quality folks…. do they have an existing system or not. How adept are they at using technology, etc…
PPM is usually pretty quick depending on the number of PMO templates.
And EC can be a royal pain.
So there is no simple template to use of path for success. I have found that each company’s need are fairly unique although the path to success is the same. Best bet is to get a partner company to come in and assess. There are also resources here that are private contractors that can help you out.
Now I cannot answer to cloud and perhaps someone else can jump in here on that.
BTW, even once you have an assessment the time frame and effort will be tied to a SOW so any deviation downstream will extend your project here. So many variables to consider…. it really is mind boggling to say the least.
Best of luck.
cathidioco
As always thanks for the thorough answer, Patrick!
Sorry for not being clear earlier. My immediate need right now is for some standard estimation guideline in enhancing an existing production instance or installation of Agile PLM on premise (not cloud) on v9.3.6 to be exact. The enhancement could either be considered configuration (native objects/classes can suffice) OR might require customization (hard coding/programming required).
Is there some t-shirt sizing guideline for Agile PLM on-prem minor enhancements, something that follows a similar approach such as:
Configuration – Small/Simple – 10 hours, Medium – 20 hours, Large/Complex – 40 hours
Customization – Small/Simple – 15 hours, Medium – 30 hours, Large/Complex – 60 hours
Obviously supported by some definition and factors that are assumed to be considered as part of “Simple/Small”, “Medium”, and “Large/Complex” minor enhancements.
I say “minor” enhancement in this case to distinguish it from a “major” enhancement would typically take over 2 weeks/10 days of man-hours.