Development Methodology Assignment
Added on 2021-04-21
7 Pages2076 Words38 Views
Development Methodology/Scenario2Assignment 1: Doing Ethics TechniqueYour NameStudent NumberSCHOOL OF COMPUTING AND MATHS, CHARLES STURT UNIVERSITYWord Count: 900Q1. What's going on?
Development Methodology/Scenario 2The case study of “Development Methodology” provides a brief description about certainalterations in a technical project in a particular organization. The client of the software hasdemanded the junior developer to make few changes and he also has promised to do the same(Scenario 2: Development Methodology, 2018). The junior software developer has not asked hissenior for approving the changes. His senior enters into the room and queries about the project.The overview of this scenario is the changes asked by client in the software. The juniordeveloper has said to complete the project within provided time with all the changes. Q2. What are the facts?The important facts of this case study of “Development Methodology” are as follows:i) The client has asked for some of the major changes in the software.ii) The junior developer has promised to make those changes (Ford & Richardson, 2013).iii) The junior software developer has promised to complete the project within theprovided time.iv) The junior software developer has not taken the permission of the project manager.These above mentioned facts clearly depict the entire scenario of the case study. Q3. What are the issues (non-ethical)?The scenario of “Development Methodology” has some of the most significant nonethical issues. These non ethical issues help to understand the wrong or the improper ideology ofthe case (Coghlan & Brannick, 2014). The first non ethical issue of this particular case study isthe query that the project manager is asking the junior developer. The project manager mayenquire to the junior software developer that why he has accepted such phone calls from clientwithout his permission. He may also ask that why he alone has taken the decision of makingthese changes. The project manager shouts at the junior developer and this is extremely nonethical. He should not behave impolitely with his junior. Due to his scolding, the juniordeveloper might feel de motivated and cannot complete his work properly. The next non ethicalissue in this scenario is that due to the rude behavior of the project manager, the junior developermight leave his job and never return to the company (Bell, 2014). Moreover, as the changes arenot done in the software, the client might be dissatisfied with the work and would never involvewith any other projects. This is another non ethical issue in this case study. Q4. Who is affected?Your Name
Development Methodology/Scenario 2There are many people, who are affected in this case study of “DevelopmentMethodology”. The first the most important person affected in this case study is the juniorsoftware developer (Slade & Prinsloo, 2013). He has promised to make all the changes in thesoftware, without taking the permission from his senior. Thus, he has got a severe scolding fromhis senior. Moreover, the project manager has talked with him rudely. This behavior has movedthe junior developer and he is extremely affected due to this. He might even leave theorganization after his scene. The second affected person in this case study is the company itself.Personnel are assets for any company and if the junior developer will leave the organization forthe project manager, the company will face loss and they would be affected (Ford & Richardson,2013). Furthermore, the organization is also losing its valuable time by giving extra time to theproject. Q5. What are the ethical issues and their implications?Although there are some non ethical issues in the case study of “DevelopmentMethodology”, few ethical issues are also present in here (Coghlan & Brannick, 2014). The firstethical issue that this scenario has is that the client would be extremely happy with the end result.The most important fact that any organization has is to satisfy their clients. When the client willnot be happy with the result or project, he would be dissatisfied and will never involve with anyother projects with the company. Thus, it is the core responsibility of the organization to fulfillall the demands of their clients. The second ethical issue in this scenario is that the juniordeveloper is agreeing to the fact of changing as per client’s demands (Mintz, 2016). It is the dutyof the junior developer to fulfill all the demands of the client and he is absolutely ethical in thiscase. Q6. What can be done about it?There are few ways to mitigate these issues. The first way is to ask for extra paymentfrom the client. Since, the changes were not mentioned in the requirement file, the client shouldpay extra money for those changes. Without extra payment, changes should not be made (Bell,2014). The second way for these issues, is to ask the junior developer for forwarding these typesof important calls to his senior and without his permission, no decision should be taken. Thethird way for mitigating these issues is to ask for extra man power for the project. If the timelimit is restricted, the changes could be made with the help of extra man power. Your Name
End of preview
Want to access all the pages? Upload your documents or become a member.
Related Documents
Doing ethics technique (DET): Assignmentlg...
|7
|1892
|33
Development Methodology - ITC506 - Doing Ethics Techniquelg...
|6
|2126
|105
A Client's Request for Some Changes in Softwarelg...
|7
|2242
|226
Doing Ethics Technique - Analysislg...
|7
|1366
|261
Doing Ethics Techniques : Doclg...
|6
|1296
|32
Information Technology Ethics Assignment (Solved)lg...
|5
|1266
|21