Importance of Prototyping and Proof of Concept

Many people think that Prototyping and Proof of Concepts are new techniques invented by modern countries. This is not true. In modern Software industry by using Agile Methodology, people are abusing these concepts. Not giving enough time and by not allocating enough resources. Also they have fancy word that POC code should be re-used as much as possible into main project. Please take a moment and read about Ramappa Temple, Warangal, Telangana, India. This temple was funded by Kakatiya Dynasty and constructed by Architect Ramappa. This is the only temple in world which is called by its architect’s name. It took enormous efforts and 40 years time. This was constructed during 1213 year and still stand firm today. Hats off to you Mr. Ramappa for all your vision, architecture, skill, execution, discipline, maintaining tempo for 40 years until completion. Modern capitalists invest less money and expect more at the cost of peanuts.

Model Temple:

1200px-Ramappa2

Real Temple:

1200px-Ramappa_Temple_Warangal

Above Two Photos:
Ramappa Temple Warangal” by Jayadeep RajanOwn work. Licensed under CC BY-SA 3.0 via Wikimedia Commons.

—————-

ramappa_temple2

https://en.wikipedia.org/wiki/Ramappa_Temple

Square Wheels – Different Views

View 1: Many times we run on square wheels, by keeping circular wheels in our dispose.

square_wheels
Reference: http://www.squarewheels.com/

View 2: We don’t have time to do introspect or listen to others

Square_wheels_help

View 3: Square wheels solves some problems in the world

square-wheel-PMapr70-x640
Reference: Patents and Info

View 4: When we can’t fix the wheel, we can fix the track.

Rolling-Square
Reference: http://en.wikipedia.org/wiki/Square_wheel

View 5: Feel the Square Wheels…: )

-o-

How to fail Software?

Oregon health exchange technology troubles run deep due to mismanagement, early decisions
http://www.oregonlive.com/health/index.ssf/2013/12/oregon_health_exchange_technol.html

Cover Oregon: Health exchange mired in unexpected delays; what went wrong?
http://www.oregonlive.com/health/index.ssf/2013/10/cover_oregon_health_exchange_m.html

IBM Software Blamed for Troubled State Health Exchanges
http://blogs.wsj.com/cio/2014/01/21/ibm-software-blamed-for-troubled-state-health-exchanges/

Massachusetts healthcare exchange fails; state seeks more Obamacare funds
http://www.examiner.com/article/massachusetts-healthcare-exchange-fails-state-seeks-more-obamacare-funds

Inside the Failure of Healthcare.gov
http://www.newsweek.com/inside-healthcaregovs-failure-1449

6 Software Development Lessons From Healthcare.gov’s Failed Launch
http://www.computerworld.com/s/article/9244123/6_Software_Development_Lessons_From_Healthcare.gov_39_s_Failed_Launch

Fix For Mass. Health Exchange Website Will Cost More Than $120 Million
http://boston.cbslocal.com/2014/05/08/fix-for-mass-health-exchange-website-will-cost-more-than-120-million/

Health Exchange Delays Tied to Software Crash in Early Rush
http://www.nytimes.com/2013/10/08/us/health-exchange-delays-tied-to-software-crash-in-early-rush.html?_r=0

Reasons I observed.
Corruption in Organizations. (Lot of money go back in kick backs, It never reach developers who work 24 x 7)
Arrogance, Lack of Knowledge, Power of Key People who make important decisions
Practicing Blame Game
Irresponsibility of Decision Makers

To make project successful along with good technical skills, good character too required.
—————————————————————–
kynect: Kentucky’s Healthcare Connection
http://kyyouth.org/congrats-to-kentuckys-health-benefit-exchange-kynect-viewed-as-success/
-o-

E2HDC means Ear to Hand Development Cycle

During discussions with teams I observed following

E2HDC means Ear to Hand Development Cycle
Few Product Managers / Business Analysts prefer to follow E2HDC. This is similar to SDLC (Software Development Life Cycle). E2HDC means Ear to Hand Development Cycle. Product Manager tells requirements in the ear of developer and developer do coding with Hand, without any thoughts. PM’s argument is that writing requirements, design and architecture is time killer. This notion builds many times when process becoming bottleneck and Architects are not contributing to project and just dragging. Also PMs favor this because they come from non-computer background. Irrespective of reasons E2HDC is disaster.

Missing Test Plans / Test Strategies: QA leads argument that test plan / test strategies are not required. They told that test cases will evolve once tester starts doing testing. This is another disaster.

Many people come to Software Industry for money without any interest to learn. These people are causing trouble and bringing bad name to Software Industry. A doctor/lawyer/cook need to have license to practice. Why not for software engineers (Product Managers / Testers / Developers)?

With lack of government monitoring colleges are mushrooming. Even syllabus in many US universities are not good. When interviewed few people, I was surprised to know that they don’t know “Software Engineering by Pressman” book.

Knowledge and Humbleness brings peace and success.
Power and arrogance are causes to failure.
-o-

Software Samurai

The Book of Five Rings
The Classic Masterpiece by Miyamoto Musashi

http://www.bookoffiverings.com/

http://www.dvdtalk.com/reviews/11524/first-samurai-book-of-five-rings-collection-the/

Mark Dacascos…and the legend of Samurai warrior Miyamoto Musashi

Audio Book

The greatness is not cutting the apple…it is controlling the self.

 

In modern world…the fight is to save the self from external world.
We need to apply strategy to win with minimal resources.
Applying all concepts of Samurai, Chess, Games…to complete given task.
Deep understanding comes through meditation and practice.
Success comes and goes…peace remains same forever.