As we come across a new product in our daily life, we always take time to learn it properly before we use it. Ain’t the same analogy hold true in a fresh development which we don’t have ever experienced. However generally in software management about a new product development, we generally tries to do bring in all sort of techniques and methodologies which might be of some use but to an extent. But as the arena is completely new and there are all sort of adventures which are never being imagined by anybody part of the project in their wildest of dreams. Moreover despite having proper risk mitigation team in place we feel glitches and huge fiasco’s. Despite everybody from top management to a management trainee who is freshly joined knows that obstacles will come, everybody meet with so much surprise on their face when things start to go wrong that manager is entirely to be blamed.
Although things are not bad as they might look, in fact they are worst. Since whenever somebody put its hand in entirely new pot, you might-never know what is inside the vessel. But when every body tries to pretend about their knowledge that they knew from beginning, it shows their immaturity towards software development process. Incidental nobody and none of the existing models or methodologies claims to entirely fool proof. They are always open for some customization. Not only sometimes models and methodologies fails disastrously but they are not meant to be used everywhere and anywhere.
Hence pessimistic approach comes in handy. Whenever thing are fresh and new, try to be realistic. Make amendments in models and try to take note of all possible risks and need to pad every risk with contingency plan. Be real and keep everybody in loop. Always try not to hide anything from anybody, be a strong but realistic manager with pessimistic approach.
