i have to reply for two person’s post. just need to give your opinion based on their post.

Person 1(metta) post:

Ethics are principles that guide how people make decisions. Nevertheless, it is not easy to define what is ethical and what is not ethical; everybody has different beliefs, culture, circumstances, and so on. Thus, what is right or ethical according to me, might not be the same for others. Resnik (2015) states that ethics is a “norm of conduct” and some defined it as common sense. However, people will justify that their belief is correct and thus, actions will be justified.

The PMI (2017) Code of Professional Conduct has four core values: responsibilities, respect, fairness, and honesty. The document explains the definition of each core value, a list of aspirational and mandatory standards, and in some sections have comments as a piece of guiding information. The aspirational standards list suggested items to follow for project managers. The code of ethics cannot give an exact answer to every ethical dilemma that people have when they are working on a project. There are too many variables. What the project managers can do is to gain knowledge about how to make good decisions and they can search the PMI’s website (https://www.pmi.org/) on ethical decision-making workshop, ethics in project management toolkit, ethics articles, and webinars.

The agile framework has a set of values and the main focus of the agile framework is to “achieve greater customer satisfaction, creating a better product with shorter product delivery and continuous delivery of valuable software” (Judy, 2009, p.3 and Cobb, 2011). Slinger (2009) argues that the agile manifesto’ principles have values that have to be followed by agile practitioners. Indeed, the framework does not offer any code of ethics for implementation and there are codes of ethics that can be used to guide people when they have dilemmas while working on projects (Judy, 2009).

The people involved in a given project are not going to be more or less ethical simply by using the agile mindset. It depends on the stakeholders who work on the projects whether they are going to be ethical or non-ethical, it does not matter which framework that they are using; an agile framework or a traditional framework. People should also be thinking about the products and the consequences of the products that they created. Those are values that must be brought to the table by the project stakeholders and not just the project managers.

As discusses above, there is no way that both the PMI Code of Ethics and Professional Conduct and/or The Agile Manifesto can cover all the issues that may arise in project implementations. There are different avenues for project managers (either traditional or agile) can gain knowledge and learn about what is the best decision to make when working on a project such as learning more about project outcomes and consequences of the project outcomes. Frey and Huff (nd), St Olaf University professors, create a website with contains tests that can help with making an ethical decision.

I believe that ethics is about right and wrong, but everybody has their own opinion about right and wrong and somebody’s reality most likely is the reality in his/her mind, which directs his/her act. Most of the time, we just need to stop and think about what will be the consequences of the products (products can be software, policies, and so on) that we are created. I do not believe that we need additional ethical codes or ethics how-to guides for either an agile mindset or traditional project management. What we need is the willingness and opportunities to learn more about products we created and the effect (either positive or negative) on the creation in people’s lives and continue discussion about ethical practice using both models.

Person 2 (Gregory) post:

In this discussion, the Agile Manifesto consist of four foundational values and 12 supporting principles which lead the Agile approach to software development. However, each Agile methodology applies the four values in different ways, but all of them rely on the principle to guide the development and delivery of high-quality, working software. However, these values and principles are;

Individuals and Interactions Over Processes and Tools: this is the first value in the Agile Manifesto which focus on “Individuals and interactions over processes and tools.” Which implies the idea of valuing people more highly than processes or tools which is a straight forward principle and easy to understand because it is the people who respond to business needs and drive the development process so the value interact closely that both must be properly applied and values in other to get better output.

In the same vein, If the process or the tools drive development, the team is less responsive to change and less likely to meet customer needs. Communication is an example of the difference between valuing individuals versus process. In the case of individuals, communication is fluid and, it happens when a need arises so both situations require each other for a positive productivity. Also, In the case of process, communication is scheduled and requires specific content. The agile manifesto bridges the gap with PMI in the sense that satisfy the fundamental principle of responsibility, respect, dignity and honesty.

Working Software Over Comprehensive Documentation: concisely, experience reveals that enormous amounts of time were spent on documenting the product for development and ultimate delivery which creates so much waste concern. However, technical specifications, technical requirements, technical prospectus, interface design documents, test plans, documentation plans, and approvals required for each process must be synchronize in other to reduce time. Therefore, extensive list of processes causes long delays in development than the software itself.

However, Agile does not eliminate documentation, but it streamlines it in a form that gives the developer what is needed to do the work without getting bogged down in minutiae so it can eliminate unnecessary late time process. Additionally, Agile documents requirements are used as user stories, which are sufficient for a software developer to begin the task of building a new function. The gap analysis that exist is that Agile Manifesto values documentation, but it also pays greater attention in working software more while taking note of value documentation. This Agile manifesto helps to close the gap with PMI code of ethics practice which concentrate on responsibility, respect, dignity, and honesty.

Customer Collaboration Over Contract Negotiation: Agile value collaboration while observing negotiation which is the period when the customer and the product manager work out the details of a delivery, with points along the way where the details may be renegotiated. However, collaboration is a different creature entirely which is very vital to agile principle and values. During product development models customers negotiate the requirements for the product, often in detail, prior to any work starting. This meant the customer was involved in the process of development before development began and after it was completed, but not during the process.

However, the Agile Manifesto describes a customer who is engaged and collaborates throughout the development process, making. However, this makes it far easier for development to meet their needs of the customer and, this helps to bridge the gap between error replications . Agile methods may include the customer at intervals for periodic demos, but a project could just as easily have an end-user as a daily part of the team and attending all meetings, ensuring the product meets the business needs of the customer. This Agile manifesto helps to close the gap with PMI code of ethics practice which concentrate on responsibility, respect, dignity, and honesty.

Responding to Change Over Following a Plan : Agile have a value and principle that a traditional software development must respond to change as an expense regulator, so it is a requirement to be avoided so customer will not be overburden with costly software process or outcome. Technically, the intention was to develop detailed, elaborate plans, with a defined set of features and with everything. Generally, having as high a priority as everything else, and with many dependencies on delivering in a certain order so that the team can work on the next piece of the desire.

However, shortness of an iteration which means priorities can be shifted from iteration to iteration and new features can be added into the next iteration which help to respond to necessary change that satisfy the customer. Moreover, Agile’s view is that changes always improve a project and, changes provide additional value which also helps to close the gap of responsibility as required by PMI code of conduct.

Concisely, both Agile manifesto and PMI code of ethics share the same values and principle in the sense that both are committed to doing what is right. Technically, they can be classify to share the same vision and honorable the principles and values which describes the expectations. However, both have the same believe that they can advance their profession if all active individual in the body collectively embracing the Code of Ethics and Professional Conduct that they will achieve their purpose and vision. In addition, they also believe that this Code will assist in making wise decisions, particularly when faced with difficult situations where they may be asked to compromise the integrity or their values. Both Agile manifestos and PMI Code of Ethics and Professional Conduct will serve as a catalyst for others to study, deliberate, and write about ethics and values.

Furthermore, the Code did not ultimately cover everything in practice concerning the future because the dynamic nature of technological innovation emerges in high pace but what is as of today is that it covered every possible issue that might lead to fatality to minimal or negligible factor if the principle and values are fully practice with reasonable experience. The reason why I put this forward is that the principles and values focus on customer satisfaction and expectation which is the main point that derive the success of every project and, it is also the starting point of all kinds of conflict any one can imagine so customer is the enabler that drive the success of the entire system.

.doc file