Thursday, June 11, 2009

HICSS 43 Call for Papers - submissions due 15 June 2009

It's time for you to get your most scintillating Agile theories
together, write a kick-ass paper that could get published in the IEEE
library and spend a week in beautiful Hawaii next January. Sound good?
Then get writing!

HICSS-43 CALL FOR PAPERS - submissions due 15 June 2009
January 5-8, 2010
The Grand Hyatt Kauai Resort & Spa
Kaloa, Kauai, Hawaii

HICSS-43 offers a unique, highly interactive and professionally
challenging environment that attendees find "very helpful -- lots of
different perspectives and ideas as a result of discussion." HICSS
sessions are comprised primarily of refereed paper presentations; the
conference does not host vendor presentations. All papers are peer
reviewed and accepted papers are published in the IEEE Digital Library.

Track: Software Technology
Minitrack: Agile Software Development: Lean, Distributed, and Scalable
Co-Chairs: Jeff Sutherland and Gabrielle Benefield

Agile software development processes have been influenced by best practices in Japanese industry, particularly by lean product development principles implemented at companies like Honda and Toyota, and knowledge management strategies developed by Takeuchi and Nonaka, now at the Hitotsubashi Business School in Japan, and Peter Senge at MIT.

This minitrack will focus on advancing the state of the art or presenting innovative ideas related to agile methods, individual practices and tools. Accepted papers will potentially enrich the body of knowledge and influence the framework of thought in the field by investigating Agile methods in a rigorous fashion.

The track is open to research papers on multiple aspects of agile methods, particularly those that bring best practices in knowledge management and lean development to scalable, distributed, and outsourced Scrum, eXtreme Programming (XP), and other agile practices. Topic areas identified as most needing further research by participants in HICSS 2009 were:

* The Product owner
* UX design
* Distributed teams
* How to effectively do self management
* Example driven development

Papers of interest include these topics:

* Research on existing or new methodologies and approaches: informal modeling techniques and practices, adapting/trimming existing methods, and new product/project planning techniques.

*Research on existing or new techniques or practices: pairing, war-rooms, test-first design, paper-based prototyping, early acceptance test driven development, exploratory testing, refactoring, or others.

*Research on special topics or tools: configuration and resource management, testing, project steering, user involvement, design for agility, virtual teams or others.

*Research on integrating ideas from other fields, e.g. interaction design, requirements engineering, cognitive science, organizational psychology, usability testing, software security, into agile processes.

*Research studies of development teams using ethnographic or social research techniques.

*Research on agile software engineering economics.

*Quantitative and qualitative studies of agile methods, practices, and tools.

*Research on agile compliance and cost benefits within CMMI, ISO 9000, and FDA certified development projects.

Papers are particularly relevant when agile processes are shown to produce quantitative and qualitative benefits across multiple implementations.

To submit papers and read more about the conference please go to the Agile Software Development HICSS43 web page.

Jeff Sutherland
Scrum, Inc. powered by OpenView Labs
332 Congress St., 3rd Floor
Boston, MA 02210
+1 617 606-3652

Gabrielle Benefield
Scrum Training Institute
London, UK


Annie Green said...

Hi Jeff,

Do you know if there is a stipend or reduced/waived registration fee for accepted papers?

Jeff Sutherland said...

HICSS is a research conference funded by registrations of people giving papers. For students there may be special rates. Please contact HICSS.

Ted M. Young said...

Could you say more about the topics that 2009 attendees thought were needed, e.g., what about the Product Owner needs attention, or what is meant by effective "self-management"? Thanks.