InfoQ

News

Are Automated Agile Tools Tactile Enough?

Posted by Ben Hughes on Sep 07, 2007 05:25 AM

Community
Agile
Topics
Artifacts & Tools ,
Agile Techniques
Tags
Useability

Picture the scene, an image of all that is Agile. A developer picking a card from a task board and taking it to her desk. The tactile feedback of the card in her hand, the sense of ownership, when writing her name on the card, and the sensory feedback of placing it back on the board in the ‘In Progress’ column.

Take the other scenario, of the developer opening a browser, logging into the PM system, selecting a task, reading the story, changing the status with a deft click of the mouse et voilà, ownership is hers. As too is tactile deprivation.

Enter the science of Social Informatics:

Social Informatics (SI) refers to the body of research and study that examines social aspects of computerization, including the roles of information technology in social and organizational change, the uses of information technologies in social contexts, and the ways that the social organization of information technologies is influenced by social forces and social practices. - Rob Kling - Center for Social Informatics

While there are some tools that try to address this problem, through more tactile interfaces (such as drag and drop of story cards in Mingle) there remains a sensory barrier between the user and the system, which in some cases (for example accessibility) can have an alienating effect on the user. More fundamentally however, does the sytemisation of processes (including agile methdologies such as Scrum) actually make the team more productive, or does it simply distract the team from (literally) the task in hand?

Many believed that technological innovation was a major factor in productivity and assumed that investments in information technology would be reflected in national statistics when the cumulative capital stock of computer systems was large enough, they would result in improved productivity statistics. Some economists coined the term “productivity paradox”, after Nobel laureate economist Robert Solow (1987) wrote, “You can see the computer age everywhere but in the productivity statistics.” Solow’s assertion counters the common assumption that computerization would directly and dramatically improve productivity.

In Agile teams the focus is on people and the needs of the team, with the primary mechanism being through social feedback, however should we stop there? The popularity of nintendo’s latest games console has introduced a new form of human computer interaction to a wide, diverse and wanting audience. Should agile software developers and tool makers heed the lessons learned in the games console industry (as some have)? What balance should we have between reporting and traceability against fulfilling the basic tactile needs of human beings?

Related Sponsor

VersionOne is recognized by Agile practitioners as the leader in Agile project management tools. Companies such as Adobe, BBC, CNN, Dow, HP, IBM, Sony and 3M have turned to VersionOne to help deliver greater value to their customers.

3 comments

Reply

On being kinesthetic by Deborah Hartmann Posted Sep 7, 2007 7:46 AM
Kinesthetic and agile by Sebastien Plisson Posted Sep 8, 2007 1:16 AM
With the help of the University of Calgary, Ral has taken a different turn by Ryan Martens Posted Sep 13, 2007 8:46 AM
  1. Back to top

    On being kinesthetic

    Sep 7, 2007 7:46 AM by Deborah Hartmann

    I've discovered that I absorb info better when I'm moving. Pacing in front of a whiteboard with a marker is enough for me, or scribbling with a stylus on my tablet computer. In fact, I rarely go back to most of my notes - it's the act of capturing them that does it for me.

    So, whether the information is on a wall or in a computer doesn't seem to affect my learning. BUT does it affect how I perceive and execute teamwork? I must admit, I really do like seeing team info on a wall, and some of the teams I've talked to have a wall display even if they are also capturing in a tool for a distributed team member.

    I've not had occasion to use any of the Agile project tools that simulate a taskboard - there are now several out there. Folks: what do you think of them? Is the simulation adequate? Does it accomplish what is needed?

  2. Back to top

    Kinesthetic and agile

    Sep 8, 2007 1:16 AM by Sebastien Plisson

    I completely agree that we, human, need to move to learn and work better. The whiteboard remains a very good way to achieve team work more efficiently. In my perception, the fact to draw/write common facts and goals on a common whniteboard is very important and pleasant, I feel more involved and more target oriented.
    In french, "agile" is directly linked to the meaning : "moving easily" related to body movements, thus, in my opinion, agile process and tools should include this "semantic origin" of "moving during the learning/working process". The body helps the mind to learn.

  3. Ben, I would love to replicate the physical world of a large whiteboard in our product, but the hardware is really getting in the way of that usability. I enjoyed the novelty of the wii demo's but in the end, there are no wii's on software practitioner desktops. As an agile project management solution provider, we are more worried about breaking developer flow than pushing the cutting the edge on tactile world in computers. (though we love our wii tennis and bowling:) For this reason, we make Rally's task management a seamless part of the Eclipse Mylyn and Visual Studio task management systems. This helps developers stay in their tools and in the flow. When it comes to planning versus task management at Rally, we teach people to plan on whiteboards and our product makes it easy to round-trip off the whiteboards for cross-team roll-up, dependant and delegated work management. This is the true compelling reason to buy an Agile Project Management solution.

    On the other hand, we have been working with Frank Mauer's team at the University of Calgary on an open source product called Agile Planner. This software uses drag-n-drop cards as a metaphor too. However, Agile Planner has a very unique capability that it allows for multiple mouse inputs from networked computers. As a result, Agile Planner lets distributed teams plan on a distributed whiteboard with multiple people standing and working at the board.

    To me, round-tripping from whiteboards, keeping practitioners in the flow and enabling distributed whiteboard planning are the problems of the day. For the future, 2nd Life might be the place to replicate the physical gesturing world and I hold some promise for RFID cards too.

Exclusive Content

Book Except and Interview : Aptana RadRails, An IDE for Rails Development

Aptana RadRails: An IDE for Rails Development by Javier Ramírez discusses the latest Aptana RadRails IDE, a development environment for creating Ruby on Rails applications.

Fast Bytecodes for Funny Languages

Cliff Click discusses how to optimize generated bytecode for running on the JVM. Click analyzes and reports on several JVM languages and shows several places where they could increase performance.

Scott Ambler On Agile’s Present and Future

Scott Ambler, Practice Lead for Agile Development at IBM, speaks on the current status of the Agile community and practices having a look at the perspective of the Agile’s future.

Manager's Introduction to Test-Driven Development

Dave Nicolette and Karl Scotland try to introduce non-technical managers to one of the most popular Agile development techniques: Test-Driven Development (TDD).

Structured Event Streaming with Smooks

Smooks is best known for its transformation capabilities, but in this article Tom Fennelly describes how you can also use it for structured event streaming.

How to Work With Business Leaders to Manage Architectural Change

Successful architectures evolve over time to meet changing business requirements. Luke Hohmann presents how to collaborate with key members of your business to manage architectural changes.

Colors and the UI

In this article, Dr. Tobias Komischke explains how colors used in a GUI can influence our interaction with a computer and offers advice on using the appropriate colors for the interface.

Building your next service with the Atom Publishing Protocol

In his presentation, recorded at QCon San Francisco, MuleSource architect Dan Diephouse explores ways to use the Atom Publishing Protocol (AtomPub) when building services in a RESTful way.