A couple weeks ago we wrote about Outside-in Software Development, by Carl Kessler and John Sweitzer. One of their ideas about stakeholders and goals has got us thinking about traceability.
Agile / Agile Project: Ratings / Interaction design / Software development / UX
Posted on:
Nexus – Drag and Drop
Implementation continues on nexus, and we’ve re-factored the way that items in a bundle are ordered, as mentioned in our earlier post. We talk a little about affordance, and show a couple screen shots.
Agile / Agile Project: Ratings / Interaction design / Software development / UX
Posted on:
APR: Persona Development
The last step in our agile software development project was documenting our understanding of our users. In this article, we will define the personas that we will use to guide our design and requirement development. This definition of personas is built by combining our experiences in consulting, product and program […]
Agile / Agile Project: Ratings / Interaction design / Product Management / Software development / UX
Posted on:
APR: Understanding Our Users
Continuing the articles in our agile project case study. The next step in our agile requirements management process is to develop an understanding of our target users. We believe a user-centric design approach is important. The user interface should conform to the way our users think about what they are […]
Interaction design / UX
Posted on:
Overdoing Personas
Its easy for us to overdo almost anything. Kim Goodwin offers some good advice about how not to overdo it when using personas as part of our software development process.
Interaction design / Requirements / Requirements Models / Use Cases
Posted on:
Actor Hierarchies And Then Some
Actor Hierarchies give us an overview of the people who will interact with the system. We can extend this model to provide a visual indication of how use cases are distributed through the organization. Further, we can leverage a hierarchy to show how use cases are rolled out to the users – a targeted communication for our stakeholders.
Design / Interaction design / Prioritization / Requirements / Software development / Software requirements specification / UX
Posted on:
Fifteen Ways to Shut Down
There are 15 ways for someone to shutdown a laptop running Windows Vista. This adds unwarranted complexity to our software. How can we avoid the same problem in our software?
Interaction design / Product Management / Requirements / Requirements gathering / ROI / UX
Posted on:
Gathering Implicit Requirements
Johanna Rothman just wrote an article titled Implicit Requirements are Still Requirements. She points out that her expectations were not met, even though her needs might have been. Johanna also implicitly begs the question – how do we gather implicit requirement?
Interaction design / Prioritization / Product Management / Requirements / UX
Posted on:
How To Not Suck At Design
Michael Shrivathsan just wrote an article presenting five tips for creating products with great design. Michael’s List Start with the user interface. [Roger Cauvin adds, start with a working first iteration] Work closely with UI designers. Pay attention to details. Simpler is better. Be brave. Our Thoughts User centric design […]