Given at Paris Web 2009.
Given at Paris Web 2009.
Uploaded via SlideShare as Apple Keynote
© All Rights Reserved
Orgil Urtnasan, Web Application Developer at Trimark Advertising
9 months ago
nstathatos
1 year ago
Dmitry Nekrasovski, User experience designer/manager at OpenText
2 years ago
Etienne Maujean, UX professional, iA, IxD at Axance
2 years ago
justkuldeep
2 years ago
Martial at Martial
3 years ago
ataupet
3 years ago
bryanespy
3 years ago
rbueker
3 years ago
Olivier G., Web developper at Novactive
3 years ago
Being Agile, Being Good
So, there’s a reason and inspiration for this talk. Last year at in London , I did a “conversation” with Ann McMeekin on practical ways to implement accessibility in a development process. And Gavin Bell from Nature Publishing Group asked me (not these exact words) “how do you ensure quality in a development process? how do you make sure things like copy is correct, and things behave according to spec?”
I gave some kind of answer about managing quality assurance (QA), but I wasn’t confident. It’s a fascinating question. It’s taken me the whole year to think about it.
And I thought I’d share my ideas with you today, here at Paris Web.
This is a fascinating question: is the problem with the process, or the team? Is it something else?
So, there’s a reason and inspiration for this talk. Last year at in London , I did a “conversation” with Ann McMeekin on practical ways to implement accessibility in a development process. And Gavin Bell from Nature Publishing Group asked me (not these exact words) “how do you ensure quality in a development process? how do you make sure things like copy is correct, and things behave according to spec?”
I gave some kind of answer about managing quality assurance (QA), but I wasn’t confident. It’s a fascinating question. It’s taken me the whole year to think about it.
And I thought I’d share my ideas with you today, here at Paris Web.
This is a fascinating question: is the problem with the process, or the team? Is it something else?
looking for a meeting point between quality and agility
I’m going to start with talking about agile, then we move on to quality, then we mash up the two and see where we end up.
Even if you’re not doing agile -- I think you will benefit from this discussion, as many things I say about quality apply in many circumstances.
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
product owner, customer roles, developer, project manager.
all work happens concurrently.
Iterations are timeboxed.
focus on user-valued features rather than completing isolated tasks.
Problem is, design leads to implementation. It’s interesting to speak about quality in a more general sense -- because a design alone doesn’t necessarily get implemented to spec the moment it leaves your photoshop file.
the process is what supports the vision.
the quality vision must exist.
how to do this as a team player
understand the motivation of your team members
look at how each of them need to succeed
people who do the best job are the ones who take pride in their work.
how do you give them pride?
by giving them room to creatively solve the problems they are experts in.
but making sure they have what they need to get their job done.
Yesterday we spoke about how hard it is to find people with skills.
But we tend to hire on skills, not aptitude. Skills can be acquired, personality -- not likely changed.
Trick: line up 2 seniors with one junior, train up the juniors. Hire them for their enthusiasm, energy, and their love of learning. Skills are easy - skills they can learn.
allow flexible interpretations, provided the requirement is met.
document all decisions/changes.
allow flexible interpretations, provided the requirement is met.
document all decisions/changes.
allow flexible interpretations, provided the requirement is met.
document all decisions/changes.
allow flexible interpretations, provided the requirement is met.
document all decisions/changes.
allow flexible interpretations, provided the requirement is met.
document all decisions/changes.