Although nearly everyone acknowledges the importance of user experience, usability often ends up pushed to the back of the queue. How then can we know whether what we are delivering makes sense and will work for our users? This presentation shows an approach to usability, focusing on activities in which users engage offers the potential for delivering dramatic improvements with much less effort.
The wider adoption of Agile software development has raised questions about how an approach that shuns up-front design and analysis can coexist with the emerging practice of user-centered design, which has a detailed user research and modeling phase before development begins. In this article Dave Churchville explores how the disciplines can be used together for an effective development process.
Who ever has wondered what kind of software is used by Santa Claus & Co, got a hint recently in youtube. This might irritate some software engineers who have assumed, Santa Claus would only use Open Source Software.
Problems with the new iPhone4G antenna again raise questions about interface design for small devices. This article briefly recaps some of the problems posed by phones and similar devices and points to some potential alternative interface solutions.
Mostly usability of a system is ascertained on gut feel rather than being based on some statistical analysis. In a recent discussion on the Agile Usability group, members discuss various ways to evaluate system usability in an objective manner.
Introduced with the rollout of the Windows Presentation Foundation, the concept of Differentiated UX (Differentiated User Experience) was intended to help promote a new capability associated with this technology for delivering enhanced user experiences. Recently, Brian Noyes and Dax Pandhi provided a more concrete explanation of the term and described its relevance to UI designers and developers.
Many software project management and architecture approaches tend to parcel out work on a project in a way to create hierarchical layers. This helps simplify both developers’ work and management. However, the underlying information shielding among layers can potentially create a gap between developers and the software they are building, if their tasks are totally taken out of functional context.
James O. Coplien has recently argued that today’s industry is based on buzzwords and checklists. The use of some techniques and methodologies, TDD for instance, has become “a religious issue”. This prevents from inspecting possible tradeoffs and focusing on finding solutions that would be the most appropriate and the most cost-effective for a given project.
Can the bonding that takes place when a developer picks a story card off the task board and takes it over to her desk ever be replicated in a system? InfoQ delves into social informatics, and addresses the effects it has on the Agile way.
