InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Are Automated Agile Tools Tactile Enough?

Posted by Ben Hughes on Sep 07, 2007

Sections
Process & Practices,
Development
Topics
Artifacts & Tools ,
Agile ,
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

In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!

On being kinesthetic by Deborah Hartmann Posted
Kinesthetic and agile by Sebastien Plisson Posted
With the help of the University of Calgary, Ral has taken a different turn by Ryan Martens Posted
  1. Back to top

    On being kinesthetic

    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

    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. Back to top

    With the help of the University of Calgary, Ral has taken a different turn

    by Ryan Martens

    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.

Educational Content

Jesper Boeg on Priming Kanban

In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches.

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.