Senex Rex
  • Team
  • Blog
  • Resources
  • Contact

Call for Papers: Agile/Lean at HICSS
(due June 15, 2016)

We invite you to submit manuscripts for the Agile and Lean: Discovery and Development mini-track, to be held at HICSS-50 on January 4-7, 2017 on the Big Island of Hawaii. We welcome papers from academics, practitioners and (even better) academic-practitioner collaborators. Co-chairs are Daniel R Greening (Senex Rex, LeadingAgile), John Tripp (Baylor University) and Jeff Sutherland (Scrum, Inc.).

HICSS logo The Hawaii International Conference on System Sciences (HICSS) provides a great mix of academics, industrialists and consultants studying many applications and aspects of system science. Now in its 50th year, HICSS is one of the longest-standing continuously running scientific conferences. HICSS is an IEEE Computer Society sponsored conference. HICSS papers are in the top 2% of conference papers downloaded from IEEE.

Topics

We seek research papers and experience reports that explore agile development, lean product management and agile/lean organizations. What evidence-based guidance can we provide to product leaders, managers and developers to help motivate, create and sustain better agile/lean behaviors and more profitable outcomes? How can we incorporate product design, architecture, engineering, risk reduction, budgeting and offshoring into agile/lean while preserving experimentation and adaptation? What common behaviors do we see in agile (including Scrum, Kanban, Extreme Programming/XP, etc.) teams and lean product management (including Lean Startup, Customer Development, etc.) and how do those behaviors affect outcomes? How do organizations and cultures restructure to support these philosophies and when they do not restructure, what happens? Which metrics help enterprises, teams and individuals adapt and improve?

In conjunction with, and in celebration of, the 50th HICSS conference, selected submissions from this mini-track may be selected for fast-track consideration in the Journal of Information Technology Theory and Application (JITTA) and the AIS Transactions on Human-Computer Interaction.

Deadlines

Submit now

Follow author instructions found on https://precisionconference.com/~hicss select “Software Technology” track and “Agile and Lean” mini-track. You are welcome to submit and update drafts over time in the submission system: iterate and improve. On request, conference chairs may be able to provide early suggestions once a draft is loaded.

May 15, 2016. Early review (optional) deadline

Abstract and manuscript submissions received before May 15, 2015 will receive early guidance to improve the likelihood of acceptance.

June 15, 2016. Submission deadline

Submit full manuscripts for review. Review is double blind; your submission must omit author names, credentials and affiliation. Follow author instructions found on https://precisionconference.com/~hicss select “Software Technology” track and “Agile and Lean” mini-track.

Background

Agile product development iteratively experiments with development behavior to improve production. Agile is most often applied to software development, and we expect some papers in this mini-track to discuss software organizations and software engineering practices. However, we also welcome papers that describe other types of organizational “production”, such as business intelligence, management initiatives, manufacturing, marketing, sales and finance.

Lean product management experiments with markets to improve revenue, continually seeks to reduce waste, including waste due to producing unprofitable products (recently popularized as “Lean Startup” or “Lean Entrepreneurship”). Characteristics include: set-based design, A-B testing, unmoderated user-experience testing, direct market experimentation, customer validation and pivoting. Advocates claim lean product management produces greater market satisfaction and customer engagement, earlier discovery of hidden market opportunities, higher revenues and more efficient use of development staff.

Experimentation characterizes both approaches: they identify leading indicators of progress (velocity, reach, engagement, loyalty, revenue, etc.), consider changes to process or product, construct hypotheses, and incorporate feedback loops to confirm or invalidate the hypotheses, perform production or market experiments, and rapidly adapt to discoveries.

These approaches claim superiority in new product development over traditional approaches (such as “waterfall management”) that fail to test development and market assumptions in long-range plans.

Agile and lean approaches challenge organizations large and small. People typically conflate small failures (learning) with large failures (organizational threats), assume that innovation means taking long-range untested risk, and establish and protect budgets with many baked-in production and market assumptions. These cultural realities interfere with agility and real innovation.

As a result, companies often invest enormous amounts of money in incomplete or abandoned agile transformations. What can organizations do to improve agile uptake? How do we know that the organization is improving? How can organizations diagnose problems without motivating gaming? What types of people are more likely to thrive in agile and lean organizations, and what roles should they take? What hiring practices result in better candidates? What training programs produce better results? What coaching structures work? How do we measure these activities?

Possible topics for the minitrack include but are not limited to:

  • Empirical outcome comparisons in industrial settings: agile and non-agile, remote and collocated, impact of different agile methods, etc.
  • New frontiers in agile management – going beyond software development
  • Forecasting, risk reduction, planning
  • Agile organizations as rhythmic and recursive experimention
  • Exploring the fit between agile organizations and their environmental context.
  • Agile and Lean requirements engineering, dependency management and risk management
  • Conflict in agile organizations and agile development teams: what cultures work and don’t work?
  • What cultures and leadership characteristics lead to sustained agility?
  • Evolution of agile organizations
  • Case studies on agile management and experimentation, in atypical situations
  • New approaches to teams and teaming
  • Impact of tool use on agile management
  • New approaches to teaching and coaching agile organizations
  • Lessons learned in agile management
  • How do agile management and traditional management complement or conflict?

We’re looking forward to your submission, and seeing you at HICSS-50 January 5–7, 2017 on the Big Island of Hawaii!

Share this:

  • Click to print (Opens in new window)
  • Click to share on Twitter (Opens in new window)
  • Click to share on Facebook (Opens in new window)
  • Click to share on LinkedIn (Opens in new window)
  • Click to share on Reddit (Opens in new window)
  • Click to email this to a friend (Opens in new window)
  • More
  • Click to share on Tumblr (Opens in new window)
  • Click to share on Pinterest (Opens in new window)
  • Click to share on Pocket (Opens in new window)

Leave a comment Cancel reply

You must be logged in to post a comment.

Continue with Facebook
Continue with LinkedIn

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Newsletter




Recent Posts

  • Align to a Driving Purpose
  • Scrum
  • Agility
  • Agile Living
  • Is Agile a Subset of Lean Manufacturing?

Contact Us

Senex Rex
1037 NE 65th St # 80358
Seattle WA 98115 USA
+1 (415) 810-3693

Courses

  • Certified Scrum at Scale Practitioner
  • Certified Scrum Product Owner
  • Certified Scrum Master
  • Agile Capitalization Workshop
  • Short Course: Agile Manager

Key Posts

Scrum

  • What is an Agile Methodology? How does it beat Waterfall?
  • How can I transform my corporation to agile?
  • Strategy Scrum Teams Enterprise Scrum: Scaling Scrum to the Executive Level
  • Release Duration and Enterprise Agility

Agile Base Patterns

  • Measure Economic Progress
  • Adaptively Experiment for Improvement
  • Limit Work in Process
  • Embrace Collective Responsibility

 

Advocacy

  • Develop Agile Managers, or Agile Dies
  • Are We Agile? Answer 5 Questions to Find Out
  • Agile Cancer: Does team-only agile cause developers to quit?
  • Agile Cancer: Stop Whining and Cure It

Advanced Techniques

  • Bulk Estimation
Copyright ©2013-2015 Senex Rex LLC. All Rights Reserved.
loading Cancel
Post was not sent - check your email addresses!
Email check failed, please try again
Sorry, your blog cannot share posts by email.
We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.Ok