How do you handle writing user stories for system that contain numerous roles that have different permissions? It seem that when adding roles to system, the number of user stories is multiplied by the number of roles to address differences in every interaction.
What methods are people using to include remote project team members in brainstorming or whiteboarding sessions? Has anyone succesfully found a way to do this using MS Live Meeting or some other screen-sharing tool?
After reading through Zaki Warfel's Prototyping, I hoped it would shed light on the most effective techniques. It was a very good read and included some invaluable insights on progressively iterating from paper models to high fidelity designs. It's led me to make some assertions about prototyping tools...
Traditionally, creating and maintaining a pattern library has been a daunting task requiring extensive resources and, sometimes, dedicated full-time employees. At Salesforce.com our first attempt at producing a comprehensive library was bogged down by a waterfall-based creation and review process that yielded only two patterns in a six-month period. At this rate we would never approach completion.
My company releases software after each iteration. The result is a
constantly changing platform. I suspect this is really bad for the
user experience. Anyone have usage data, case studies, etc on this
Director of User Experience | Acquia
978.296.5237 | @jeffnoyes
(Apologies if you receive more than one of these.)
We have several courses coming up in May: - 10 May, Agile UCD (London) http://www.syntagm.co.uk/design/agileucd.shtml - 24 May, Ajax Design and Usability (UPA Conference, Munich - evening) - 25 May, Web Design for Usability (UPA Conference, Munich - full day)
This has been on my mind a lot lately. I feel like our process is
very fast and accomplishes the right things, but I don't have much
to compare it to. It'd really mean a lot to me to know your
company's design process and to gather any feedback you have on the
process I outline below. I'm looking for ways to improve what we
So here's how we do design at onegreatfamily.com:
We are a small company, we have 8 developers. We consider ourselves
an "Agile/Scrum" shop. We have 2 designers, one assigned to the
windows app and one assigned to the website.