OOPSLA 2008 Workshop on:
Challenges: Agile Values Meet Different Value Systems
October 19-23, 2008
Nashville, Tenessee, USA
Submission date elapsed - walk in participants are welcome!
Submissions
Contents and Objectives
One might think object oriented Software Development and Agile Methods being mainstream by now in industrial practice. Especially the handling of method mixtures, as we face it, when different organizations and disciplines have to work together, being addressed by now. In fact, exactly here we are facing conflicts, which in worst cases lead to failed software projects.
Our assumption: The choice of methods and tools is an expression of the value systems of the individual, team, organization, etc. This applies to software development as well as to any other discipline. Different value systems are accountable for structural conflicts, which might not be obvious nor have a solution. This means we have to take underlying value systems into account, when working in larger contexts.
How do we, as software developers who value agile methods and object oriented approaches, handle structural conflicts, coming from differing value systems, in detail:
-
What are typical conflicts and how do we recognize them?
-
How do we approach these structural conflicts? When are we confined to work on symptoms only, and when can we tackle the cause?
-
If there is no solution within reach, how to mitigate?
For this workshop we are aiming at a discussion between research and industry. The following (not exclusive) list of possible goals, can be used to set a context to discuss afore mentioned questions in detail:
-
Initiate a discussion about value systems and there impact on our choice of tools and methods in state of the art software development
-
Identify typical categories of value system based conflicts
-
Discuss approaches to tackle or mitigate conflicts coming from differing value systems
-
Find ideas how to improve software development methods and tools
-
Discuss ideas to improve software development education
-
Looking for examples to create a lively discussion
-
Form a community to continue the workshop’s discussions
At the beginning workshop attendees will decide if they want to add additional goals to the workshop.
How to participate
Every practitioner, researcher, or otherwise interested is invited to issue a position statement of 1 (max. 2) pages relevant to the workshop topic until August 18, 2008, either via email to “ jpechau at acm.org ” or “ becker at informatik.uni-hamburg.de ” or via workshop blog . We are looking for submissions from people having researched on these subjects or who can provide practical experience with this regards. Upon acceptance, submissions will be posted on the workshops blog if not allready done, and will be open for discussion. The authors will be notifed by September 2, 2008, to be able to benefit from the reduced early registration rate for OOPSLA ( early registration deadline: September 11, 2008 ). The number of participants will be limited to 20.
Preliminary Workshop Format
We aim of having a highly interactive workshop, therefore the workshops format will be an issue of all participants. Take this list as a suggestion:
• Introduction, agree on workshop format
• Introductory statements, max. 3 minutes each (“Elevator pitch”)
• Identify key topics and form focus groups
• Presentation and discussion of focus group work
• Closing discussion on subsequent actions, e.g. format of a final report, like blog, issue experience report to (online) journal, poster for OOPSLA poster session, etc.
Organizers
Joerg Pechau ( jpechau at acm.org ):
Petra Becker-Pechau ( becker at informatik.uni-hamburg.de )