Capability Maturity vs. Work on Proposals: Difference between revisions
No edit summary |
No edit summary |
||
Line 9: | Line 9: | ||
The first is the amount of unpaid work I can put in on a lead before I must have some payment if I have not decided to do the work on some other basis. | The first is the amount of unpaid work I can put in on a lead before I must have some payment if I have not decided to do the work on some other basis. | ||
</blockquote> | </blockquote> | ||
<blockquote> | <blockquote><a style="text-align: right;" href=https://juan.ai-integration.biz/everything/index.pl?node_id=1109><img height=300 src=https://meansofproduction.biz/images/img333-5434-10.png></a> | ||
I am just a single struggling worker so I am forced to spend no more time on a lead than a rational expectation of closing and completing a job indicates is justified. Necessarily there will be some misappraisal and some potential biz will be lost, that's the way free markets work. I started my professional programming career as a junior engineer in a division of a conglomerate that was a subcontractor to IBM in the acquisition and award phases of a contract for the modernization of the </html>[[:en:Air Force Satellite Control Facility|Air Force Satellite Control Facility]]<html> that spanned two years. <br/><br/>I am risk averse however and I also am loathe to perform work for nothing in this era, in which one must work very fast, in requirements analysis and design. This doesn't mean I won't do it, but the party requesting such unpaid service must be such that I can be reasonably sanguine about the aforementioned expectation, as Litton and IBM were because they knew the Federal Government had already decided to award IBM the contract. For that reason the IBM team was willing to spend maybe a million or so to get an award worth billions. | I am just a single struggling worker so I am forced to spend no more time on a lead than a rational expectation of closing and completing a job indicates is justified. Necessarily there will be some misappraisal and some potential biz will be lost, that's the way free markets work. I started my professional programming career as a junior engineer in a division of a conglomerate that was a subcontractor to IBM in the acquisition and award phases of a contract for the modernization of the </html>[[:en:Air Force Satellite Control Facility|Air Force Satellite Control Facility]]<html> that spanned two years. <br/><br/>I am risk averse however and I also am loathe to perform work for nothing in this era, in which one must work very fast, in requirements analysis and design. This doesn't mean I won't do it, but the party requesting such unpaid service must be such that I can be reasonably sanguine about the aforementioned expectation, as Litton and IBM were because they knew the Federal Government had already decided to award IBM the contract. For that reason the IBM team was willing to spend maybe a million or so to get an award worth billions. | ||
</blockquote> | </blockquote> | ||
Line 15: | Line 16: | ||
The second is so-called </html>[[:en:Capability Maturity Model|'''Capability Maturity (CMM)''']] and its [[:en:Antipattern|''antipattern'']] [[:en:Capability Immaturity Model|'''CIMM''']] <html>, which has to do with the reliablity of estimates in CMM Level I or lower situations. | The second is so-called </html>[[:en:Capability Maturity Model|'''Capability Maturity (CMM)''']] and its [[:en:Antipattern|''antipattern'']] [[:en:Capability Immaturity Model|'''CIMM''']] <html>, which has to do with the reliablity of estimates in CMM Level I or lower situations. | ||
</blockquote> | </blockquote> | ||
<blockquote> | <blockquote> | ||
Of course the lack of adequate requirements analysis and design is a major penultimate root cause of failure in software development projects (the ultimate root being the universal antipattern Failure of Responsibility). These elements are seldom done well outside of very mature and well capitalized organizations and nonetheless work gets done. There is huge waste and very high rates of failure for immature actors entering the Software Development arena. Trynna address that in the way that Capitalism provides. | Of course the lack of adequate requirements analysis and design is a major penultimate root cause of failure in software development projects (the ultimate root being the universal antipattern Failure of Responsibility). These elements are seldom done well outside of very mature and well capitalized organizations and nonetheless work gets done. There is huge waste and very high rates of failure for immature actors entering the Software Development arena. Trynna address that in the way that Capitalism provides. |
Revision as of 04:23, 8 September 2020
See Also: UnitXP
. |