Normally, packaging requests are categorised in 3 types; Simple, Medium and Complex.
Do we have any rules to apply while deciding level of complexity for packages?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

1
We are having the same discussion at work atm.

How do we categorize them? Size, Complexity, Difficulty to re-package?
How would you combine them and filter out a definitive answer?
If you only go by size, then for sure you'll get a small app that is a pain to repackage and vice versa.

There is a saying in Sweden, "What you lose on the carrousels you'll get back on the swings". Which basically means that everything will even out eventually.

I know there aren't only one answer to this question, but how do the rest of you do?
Answered 01/12/2012 by: andemats
Second Degree Black Belt

Please log in to comment
1
My approach would be the following:

ask a number of questions regarding packaging size, complexity, etc... along the lines of

- is the package bigger than 500MB?
- is the source a legacy installer (as opposed to vendor msi)?
- does the package upgrade previous versions?
- will setupcapture be used (instead of silent install parameters)?
- if silent install parameters are to be used, are they unknown at the time?
- does the package contain environment-specific settings (UAT/DEV/PROD)?
- are database connections included in the package?
- are there custom actions required?
- what is the number of seperate installers included in the installation source?
- does the vendor provide a proprietary customisation tool?
(yes =0, no=1)


etc.. etc.. I'm sure you can think of some, just decide what to you makes a package more difficult.

then for each question, if you answer yes, add 1 to a total, if you answer a number, add that number. At that point just decide on some cut-off points to distinguish different difficulty ratings, add up the points for a package, and there you go. You could even take it up a notch and weigh certain answers heavier than just a 1. You get the idea I'm sure.

PJ
Answered 01/12/2012 by: pjgeutjens
Red Belt

Please log in to comment
1
We don't, because it's easier to sell to the customer, easier to understand and let's us be more competitive.
Answered 01/12/2012 by: GrGrGr
Orange Belt

Please log in to comment
1
ORIGINAL: pjgeutjens

My approach would be the following:

ask a number of questions regarding packaging size, complexity, etc... along the lines of



Valid point Pieter.
We were planning on having some sort of template for our customers, so that they would know themselves roughly what kind of category a package will be before they order it.
After we receive the order, we'll approve or revise the category.

Thanks for the examples, Pieter. I'll probably use most of them for our template. [;)]
Answered 01/12/2012 by: andemats
Second Degree Black Belt

Please log in to comment
1
Thanks Pieter. This does help.
Also I think, in-house developed apps directly come under complex umbrella as no documentation is available most of the times.
Need to mention that whatever comes from Oracle, IBM is always a complex one.
Answered 01/13/2012 by: SandeepPanat
Orange Senior Belt

Please log in to comment
Answer this question or Comment on this question for clarity