The word “myth” based from Wikipedia is a word that is often used colloquially to refer to a false story, however in terms of academic, the word generally means does not pass judgment on truth or falsity. Therefore in my opinion, the word “myth” simply means something that is assumed exists but there is no proof about its existence.
Software myths can be classified to 3 (THREE) which are:
1. Management myths
2. Customer myths
3. Practitioner myths
Some common managerial myths stated by Rogher Pressman are:
Myth: A good manager can manage any project.
Reality: In a high stake project especially a software project that costs a lot of money, an expert is needed to manage it carefully. To ensure a good project management, developer’s company will need a manager that can manage one thing that he can do adeptly, not a manager that can manage MANY things but he cannot do it adeptly.
Software myths can be classified to 3 (THREE) which are:
1. Management myths
2. Customer myths
3. Practitioner myths
Some common managerial myths stated by Rogher Pressman are:
Myth: A good manager can manage any project.
Reality: In a high stake project especially a software project that costs a lot of money, an expert is needed to manage it carefully. To ensure a good project management, developer’s company will need a manager that can manage one thing that he can do adeptly, not a manager that can manage MANY things but he cannot do it adeptly.
Myth: If I decide to outsource the software project to a third party, I can just relax and let that firm build it.
Reality: If an organization does not understand how to manage and control software project internally, it will invariably struggle when it out sources software project.
The second myth that I will tackled is the customer myth:
Myth: I know what my problem is; therefore I know how to solve it.
Reality: Customer may know how to solve it. However from developer’s point of view, the way customer wants to solve it may not be as same as the way the developer wants to solve it. Therefore by maintaining good communication between both parties can guarantee that the needs can be met.
Reality: Customer may know how to solve it. However from developer’s point of view, the way customer wants to solve it may not be as same as the way the developer wants to solve it. Therefore by maintaining good communication between both parties can guarantee that the needs can be met.
The third myth which is the last is practitioner myth :
Myth: If I miss something now, I can fix it later.
Reality: Whenever something is missed, especially in earlier development stage, we should immediately get it done because if one thing is missed and we only notice it in later stage, a very major modification needs to be done and it will consume much time and will become a big problem to the team.
Reality: Whenever something is missed, especially in earlier development stage, we should immediately get it done because if one thing is missed and we only notice it in later stage, a very major modification needs to be done and it will consume much time and will become a big problem to the team.
References:
* Wikipedia.
No comments:
Post a Comment