By shahid iqbal.  Requirements Negotiation is another name for conflict resolution.  process addresses problems with requirements where conflicts occur.

Slides:



Advertisements
Similar presentations
4th Module: Information Systems Development and Implementation:
Advertisements

Develop an Information Strategy Plan
Notes by Ben Boerkoel, Kent ISD, based on a training by Beth Steenwyk –
Introduction to Entrepreneurship and New Venture Creation Rui Baptista
1 Requirements and the Software Lifecycle The traditional software process models Waterfall model Spiral model The iterative approach Chapter 3.
In Europe, When you ask the VET stakeholders : What does Quality Assurance mean for VET system? You can get the following answer: Quality is not an absolute.
Project management Project manager must;
Interpersonal skills & Communication Edina Nagy Lajos Kiss Szabolcs Hornyák.
COMMUNITY RESOURCE MAPPING Train the Trainer MAST - NH December 15, 2006 Facilitated by: Kelli Crane.
IFRC Shelter Technical Training Yverdon-Les-Bains, Switzerland | 3 rd – 7 th March 2008 This session describes the benefits of developing a strategic plan.
International negotiation
Action Logic Modelling Logic Models communicate a vision for an intervention as a solution to a public health nutrition (PHN) problem to:  funding agencies,
Presentation By: Chris Wade, P Eng. Finally … a best practice for selecting an engineering firm.
Recall The Team Skills 1. Analyzing the Problem 2. Understanding User and Stakeholder Needs 3. Defining the System 4. Managing Scope 5. Refining the System.
Putting It all Together Facilitating Learning and Project Groups.
4 4 By: A. Shukr, M. Alnouri. Many new project managers have trouble looking at the “big picture” and want to focus on too many details. Project managers.
Copyright c 2006 Oxford University Press 1 Chapter 7 Solving Problems and Making Decisions Problem solving is the communication that analyzes the problem.
Developing a customer service strategy to support the new regulatory model An introductory paper for the Providers Advisory Group.
Pre-Project Planning Lessons from the Construction Industry Institute Construction Industry Institute Michael Davis, P. Eng, PMP Ontario Power Generation.
Connections to Independence
Enterprise Architecture
1 Interdisciplinary Collaboration for Elder Care.
QUALITY ASSURANCE PROJECT Conflict Management The purpose of this module is to develop participants’ facilitation and training skills to enable them to.
Develop your Leadership skills
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
Software Development *Life-Cycle Phases* Compiled by: Dharya Dharya Daisy Daisy
Chapter 2 The process Process, Methods, and Tools
Software Project Management Introduction to Project Management.
Shelter Training 08b – Belgium, 16 th –18 th November, 2008 based on content developed by p This session describes the benefits of developing a strategic.
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
 Learning Objectives:  Understand the meaning, levels and sources of Conflict  Discuss various ways and styles to deal with conflict  Recognize the.
© 2012 NTT DATA, Inc. NTT DATA Corporation Requirements Prioritization.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
TEAMWORK Training the Programme Developers. Teamwork: why do we need it? Responsibility, potential and delegation Your optimal potential Resposibility.
Management & Development of Complex Projects Course Code MS Project Management Perform Qualitative Risk Analysis Lecture # 25.
June 4,  Why are we spending time discussing elements of effective group work ?  Effective and collaborative group work requires an intentional.
QUALITY ASSURANCE PROJECT Change Management The purpose of this module is to develop participants’ facilitation and training skills to enable them to enhance.
Software Engineering Saeed Akhtar The University of Lahore Lecture 7 Originally shared for: mashhoood.webs.com.
IS Methodologies. Systems Development Life Cycle - SDLC Planning Planning define the system to be developed define the system to be developed Set the.
Assessing the influence on processes when evolving the software architecture By Larsson S, Wall A, Wallin P Parul Patel.
Dr. Jana Jagodick Polytechnic of Namibia, 2012 Project Management Chapter 2 Project Management Cycle.
Fifth Lecture Hour 9:30 – 10:20 am, September 9, 2001 Framework for a Software Management Process – Life Cycle Phases (Part II, Chapter 5 of Royce’ book)
Project Management Workshop James Small. Goals Understand the nature of projects Understand why Project Management is important Get an idea of the key.
Facilitating Collaborative Decision Making Anne Wright.
FINAL PRESENTATION OF ORGANIZATIONAL BEHAVIOUR AND ANALYSIS Prepared for : Dr. S. Kumar Group : Dollar 2 A. R. S. BANDARA - PGIA / 06 / 6317 B. A. G. K.
LECTURE 6 A Conflict Management.
Requirements Engineering Processes. Syllabus l Definition of Requirement engineering process (REP) l Phases of Requirements Engineering Process: Requirements.
DEVELOPING THE WORK PLAN
Interest-Based Bargaining.  Interest-based bargaining involves parties in a collaborative effort to jointly meet each other’s needs and satisfy mutual.
Requirement Engineering
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
Fundamental of International Business Negotiation
DGS Town Hall with Director Fred Klass October 3, 2011.
Conflict Management RAJKUMAR MANDA Dy.Mgr (Mining)-HRD RAJKUMAR MANDA14/25/2011.
44222: Information Systems Development
Lecture “6” Manage Project Team
CHANGE READINESS ASSESSMENT Measuring stakeholder engagement and attitude to change.
AGRO PARKS “The Policy Cycle” Alex Page Baku November 2014.
©SHRM SHRM Speaker Title Bhavna Dave, PHR Director of Talent SHRM member since 2005 Session 2: Relationship Management Competencies for Early-Career.
Kate Perkins for the Ithaca Group. Setting the scene  Where has the CSfW come from?  What is it for? Who is it for? The framework  Skill Areas  Developmental.
European Agency for Development in Special Needs Education Project updates Marcella Turner-Cmuchal.
Requirement Elicitation Nisa’ul Hafidhoh Teknik Informatika
Security Development Lifecycle (SDL) Overview
Process 4 Hours.
Change Request Management
The Project Management Framework
Conflict defined: Numerous definitions exist! For our purposes “conflict” is: 1) An expressed struggle- The conflict turns from intra-personal to interpersonal.
Portfolio, Programme and Project
Presentation transcript:

By shahid iqbal

 Requirements Negotiation is another name for conflict resolution.  process addresses problems with requirements where conflicts occur between stakeholders wanting incompatible features, or conflicts between requirements and resources, or between capabilities.  This process is sometimes viewed as a sub process of requirements analysis.

CONSENSUS MAKING IN REQUIREMENTS NEGOTIATION: THE COMMUNICATION PERSPECTIVE  Requirements Engineering (RE) is a cooperative learning process where stakeholders from different backgrounds with different experiences and objectives have to communicate to elicit and validate requirement (Bustard 2002).  Stakeholder interaction as a group provides an opportunity for the emergence of misunderstanding and conflict.  The catalyst being that even when common objectives are set, agreed to and acknowledged by others, the participants often misinterpret objectives due to the influence of their bias, personality and environment.

Consensus  consensus making process has been defined as a group process where stakeholder input is carefully considered so an outcome that best meets the needs of the group can be crafted

Negotiation Process  Consensus outcomes not achieved through negotiation can lead to stakeholder dissatisfaction and non-acceptance of information systems  Consensus doesn’t occur without some active intervention and bargaining of the participating parties; instead it is commonly negotiated  Negotiation is consider as having a direct affect on the consensus process.

Requirement Negotiation  Requirements Negotiation (RN) is a practice implemented early in the planning stages for each project, or phase of an incremental or evolutionary development approach (and whenever requirements change).  Negotiating in conflict situations is considered one of the main tools to facilitate satisfactory conclusion to the entire cycle of RE

continued  Lewicki et al (1999) examined various aspects of negotiation concluding that it consists of at least four typical elements. I. *Conflict is recognized as the first and the foremost element in negotiation. conflict situations may, influence stakeholder expectations of possible negotiation outcomes and fairness in settlement. *Settlements are commonly achieved through negotiating parties sacrificing their objectives and the expected outcomes.

2 nd Negoation element  The second negotiation element recognised by Lewicki (1999) is a degree of interdependence between the counterparts.  They believe that all parties involved and in negotiation must be reliant on the other party to some extent or negotiation of an accepted outcome would not be necessary.

3 rd Element  The third element is an opportunistic interaction that provides the counterparts the access to influence each other (Lewicki 1999).  Opportunistic interaction cannot occur without the counterparts communicating in some way.  Clearly acknowledge communication to facilitate cooperation in mixed motive conflicts.  They have also demonstrated that the type of communication media used to facilitate negotiation influences the outcomes.

4 th element  Lewicki et al. (1999) discuss the fourth and final negotiation ingredient being the possibility of agreement.  They argue that parties would not even sit at a negotiation table unless they could see the very possibility for reaching and acceptable outcome.

Benefits of RN Some key benefits are:  More complete requirements in the early stages of a project  Fewer requirements changes during development  Enabling a shared vision throughout the life cycle  Negotiation methods preserve/retain the rationale of decision making  Control of “Scope ”

Effective practices for requirements negotiation 1. Get the right stakeholders 2. Establish a teamwork mentality 3. Plan team interaction 4. Use a Group Support System (GSS) 5. Establish a shared vocabulary 6. Maintain a list of requirements 7. Manage by probabilities of completion rather than absolutes 8. Select an operational approach coupled with risk assessment

9. Select an operational approach coupled with risk assessment 10. Plan more than one release at a time 11. Re-plan before every new release 12. Find a workable solution 13. Provide training in the negotiation process continued

Refrences CONSENSUS MAKING IN REQUIREMENTS NEGOTIATION: THE COMMUNICATION PERSPECTIVE