This is something I have read from an external resource and that is taking so much time from me:
The recognition that the development of a solution really cannot be profitable is very hard for the person who studied it.
Sometimes, the defense of this viability is done as a matter of life or death.
There are so many hours, effort and personal expectative when you are doing it and your ego does not let you to think in the failure of this initiative. On the other hand the creation of higher expectations can be bad. This should be avoided.
If business case is well prepared and the answer is “… no this solution is not viable for us!”. No problem, this is a valid answer and you are taking a good decision for your company.
This has to be explained during early phase of the analysis to avoid future frustrations.
LCC requires decisions during R&D phase. Just at this moment is when you need to start the LCC analysis. A silly example, you are working on R&D and you have 2 designs for a solution; both requires the same cost for manufacturing but the maintenance is cheaper in one of the cases.
Of course real life is a little bit complex, but this process is necessary to avoid unexpected expenses at a point where you have not an alternative.
The scope of this LCC is all the cost to the organization for the creation of a product/solution: R&D, production, operation, support…
Then, what you have to do is the systematic evaluation of alternatives with the objective of chosing the best way to employ your resources.
You can detect a good/bad business analyst just seeing the way they take care about the future expenses of its analysis.
This answer let me understand the ignorance of this person about his understanding of what a meeting minutes can mean with regards to its value in terms of ‘agreement’ during the execution of a project.
This meaning was explained and understood by the other part, so the issue was closed just at that moment.
I can understand the lack of knowledge or an inappropriate comment at a given moment, but what I don’t like was the arrogance showed and the way it was expressed, but anyway, it’s other issue.
- Allow the current users to access to their Web applications with the existing configuration pattern.
- Allow the mobile users to access to the WSDL elements using the Session Authentication = “Disable”.
With it, the access of the mobile users is done with the credentials entered when the user access to the application (an username/password screen is shown).