Posts Tagged ‘Notes’

Incorporating UCD & Agile software development

Friday, February 25th, 2011

Scott Rismiller Monsanto
Christine Jenkins
Kathy Marshall
Jim Marsh

Kathy: history of agile – basic info
Ms. No name: ux design up front then iterative design during development
UX Long Sprint: up front contextual inquiry, focus groups, personas, etc
Jim: best practices. Having the UX process done up front allows developers to hit the ground running. Focus on the areas that you don’t do well so they don’t block you. Use the right amount of documentation. Product owner is critical.

Q&A
UX is important throughout the entire lifecycle to validate the requestors requirements.
Customers like seeing low-fidelity prototypes.

What if there are no or weak product owners?
Scott: if you see a risk to your project, the company is at risk. Make management aware of the risk.
Jim: as a team, they rejected the product owner and replaced her with someone else.
Kathy: current client delayed their project until a strong product owner became available
Christine: reduced a room of 12 decision makers to one product owner who could make decisions

Are the designers and UX people dedicated resources?
Kathy: It depends on how much work is required in the user experience side. Full time is ideal. This assumes you are working on one scrum team. Multiple scrum teams means more design resources.

Where does non-value add refactoring playing into short iterative cycles?
Jim: the technical leaders have to watch it. Sometimes you have to take a full sprint off to pay technical debt. Decided by senior leaders. If too much builds up too often, there is a problem. The sooner you pay off technical debt, the cheaper it will be to pay.

What’s the smallest manageable agile team size?
Jim: 3 product owner and two folks. Two people are agile by default. Kathy: Think about it as number of roles more than the number of bodies.

How much prototyping is done during sprints? How much ahead of time?
Christine: navigation, main page, high risk use cases – before hand. During sprint, prototyping the whole time. Many times the designs two sprints ahead.
Jim: spike – drive a spike to start generating the other requirements – in the middle of a sprint

How can I help my company adopt agile?
Scott: educating the decision makers. Back it up with case studies and the financial aspect. Show the financial value. Propose a case study on a non-essential product
Kathy: have them think of the way a project runs right before a release and imagine running the whole project like that
Jim: most people have heard of it so don’t be left out!
Christine: waterfall plus agile to meet govt regulations. Don’t use the term agile, call it “iterative”
Kathy: be adaptable to the current culture

What kind of things have to work well in a low-fidelity prototype?
It depends on what your trying to show. Whatever you are seeking feedback on needs to work well enough to get feedback.

How is ux testing done when ux resources are low?
Christine: Testing has to happen according to available resources – at least at first. Then build in ux lab testing to your schedule.

The next decade of web design

Friday, February 25th, 2011

Micah Herstand
Linked data and the web

People want the information or data that is hidden behind our computers
The semantic web allows us to connect to linked data
Web pages are interfaces to allow us to combine and use the data

How are the connections represented? What is the context?

Links are unknown and take you away from where you currently are. How do we build trust and context into links?

Constraints are valuable in building context

1 uris for everything
2 uris respond with useful information
3 relationships between data

How do we design in the linked data environment

1990s
Behaviour
Style, structure, content

2000s
Style | behavior
Structure
APIs (content)
Data (content)

2010s
Style | behavior
Structure
Linked data (content)

A new kind of link
Facebook likes – you know what this is because of context
Google rich snippets

Using micro formats
Ogp.me
Linkeddata.org

Tangible constraints of distance are lost on the web

A model for how process and staffing decisions impact utility and usability

Friday, February 25th, 2011

Mike Coble
Value
Help target users do target work
X users * amount of work supported * amount of cost to support each user per year = value in dollars

10 users * 10% * $4000 = $4000

Relative utility = supported work/ targeted work
User adoption = used work/ supported work
= f(usability)
Just requiring people to use something does not increase value
UX drives customer value

- Utility = how much work is supported
– % of targeted work actually happens
- Usability = how well that work is supported
– Quality of use metric
Realized customer value
I hope he publishes a version of this model!

DEFGHI’s of creating technology that works for people

Friday, February 25th, 2011

Mike Coble

ABC is the basics
-paper prototyping,
-usability testing
-contextual inquiry

DEFGHI is the rest

HF – human factor
- HF is the basis for UX
- Building affinity models
- Team immersion in the user data so they can interact with it – people only retain 10% of what you tell them or they read but 90% of what they interact with [citation needed].
- rough is good. Things that are rough are malleable
- create don’t debate. Don’t present ideas, just make them
- Parkinson’s Law: work expands to fill the time available for it’s completion
- first, schedule the first test
- deal with real people, not abstract cogs

EG
Exampli gratia – for example (e.g.)
- UCD (user centered design) guided design with task examples
- personas
- stories and story boards

DI
Design Idea
A way to tag design ideas. Bits and pieces of designs that may or may not be used.
Capture but don’t venerate design ideas
- contextual inquiry
- team ideas
- paper prototyping

STL UX Notes 1

Friday, February 25th, 2011

Medical inertia
Keep doing more of the same, oftentimes doing nothing other than making sure what we were doing worked.

The current system does not accommodate narratives – you can’t record a life style change. It’s not recordable. No proof that doctors are doing anything. It’s easy to prescribe drugs – or at least it’s easier to record that something was prescribed

Medicalization – if there is a drug for it, why would you offer other things?

Medical Home
Patient focused: focused on the whole person. Patient preferences guide the care provided
Team-based:
Efficient: receive the right care at the right time
Comprehensive: pcp is first contact but is tied to everything else to deliver fully integrated care
Continuous
Communication

What is health/wellness?
Proscriptive health – do this to be “healthy” instead of “do this when you get sick”
Lots of varying definitions
Health is a measure
Wellness is a process