Development Methodology - ITC506 - Doing Ethics Technique
Added on 2020-03-07
6 Pages2126 Words105 Views
SCHOOL OF COMPUTING AND MATHS, CHARLES STURT UNIVERSITYDevelopment Methodology/Scenario2Assignment 1: Doing Ethics TechniqueYour NameStudent NumberWord Count:1000
Development Methodology/Scenario 2Q1. What's going on?The title of the scenario is ‘Development Methodology’. The video begins with a scenewhere the junior developer is having a telephonic conversation with the client. The projectmanager enters the scene and asks about the progress of the technical project that they aresupposed to deliver to the client company ("Scenario 2: Development Methodology", 2017).He gets to know from the junior developer that the client is asking to make some changes inthe software. The project manager enters the room and asks about the progress of theproject. After getting to know about the client’s demand, he asks the details of themodifications. The scenario explains that the junior developer agrees to make the changesin the software as per the requirement of the client.Q2. What are the facts?The scenario gives the description of a scene taking place in an IT based company. Thiscompany is responsible for delivering software projects as per the demand of the clients.The client does not seem to be satisfied with the way the software is being developed. Heasks the junior developer to make certain modifications based on his own idea (Weiss,2014). The junior developer happily agrees to do so. Now the question arises that being anemployee of the company, whether he should have agreed so easily and taken a decision onhis own or whether he should have asked his senior authorities before agreeing. Then theproject manager enters the scene and talks to him regarding the progress of the project.Q3. What are the issues (non-ethical)?There can be several non ethical issues in this scenario. The junior developer accepted therequest of the client without informing the project manager. This can be considered to benon ethical because being a subordinate who is working under a project manager; he shouldhave at least informed his senior before taking any decision. Another non ethical issue canbe that, the project manager shouts at the junior developer for not informing him beforetaking such decisions (Schwartz, 2017). Screaming and shouting is a non professionalbehavior that can also be considered to be non ethical. The project manager should explainthe developer in a polite and professional manner. Another non ethical event can takeplace, where the project manager will agree with the junior developer and proceed withoutYour Name
Development Methodology/Scenario 2informing the program director. Any decisions taken in an organization must follow thechain of order or authority. Taking independent decisions without informing the higherauthorities can be considered to be non ethical. Q4. Who is affected?The entire project team of the company including the program director, project managerand the junior, senior developers of the company will be affected. They will have to modifythe changes as required by the client. This will utilize even more and extra resources of thecompany. If they do not follow the client instruction properly then the client will be affectedas he will not be satisfied with the project delivered by the vendor company (Jahanshani etal., 2014). On the other hand if the program director shouts at the junior developer fortaking decision then the developer might feel bad and not come to work and plan to resign.This will affect the mind of the junior developer and demotivate him to work in theorganization.Q5. What are the ethical issues and their implications?The project manager can shout at the junior developer for taking his own decision andagreeing with the client. This will demotivate the developer and he might not feel likeworking in the organization (Shaw & Barry, 2015). This is one ethical issue. Another ethicalissue can be that the project manager encourages his junior developer to go forward withthe plan. Later on if the client is not satisfied then the program director can blame him fornot letting the higher authorities know. In an organization one must let the higherauthorities know before taking any steps. Taking independent decision does not belong toan organizational culture. The implications of taking self decision can lead to huge loss andclient dissatisfaction.Q6. What can be done about it?The project manager should have faith on the junior developer and appreciate him to takedecision on his own (Baker & Comer, 2012). At the same time the project manager shouldlet the developer know that in an organization one must take decision by discussing withothers. The project manager should inform his higher authority regarding this. A jointYour Name
End of preview
Want to access all the pages? Upload your documents or become a member.
Related Documents
Development Methodology Assignmentlg...
|7
|2076
|38
Doing ethics technique (DET): Assignmentlg...
|7
|1892
|33
A Client's Request for Some Changes in Softwarelg...
|7
|2242
|226
Doing Ethics Techniques : Doclg...
|6
|1296
|32
What's going on? A simple change implication requestlg...
|6
|1381
|407
Information Technology Ethics Assignment : DETlg...
|6
|1217
|53