Джеф Паттон проектирует и разрабатывает ПО во множестве проектов, от интернет заказа деталей самолетов до электронных медицинских записей. Джеф нацелен на Agile подходы со времен работы в XP команде в 2000 году. Джеф специализируется на применении ориентированных на пользователя методик проектирования, чтобы улучшить Agile требования, планирование и продукт. Его статьи на эту тему можно найти на сайте www.AgileProductDesign.com и в Crystal Clear Алистара Коберна.
Сейчас Джеф - независимый консультант, создатель и модератор Yahoo группы по agile-usability, обозреватель StickyMinds.com и IEEE Software и победитель премии Agile Alliance’s 2007 Gordon Pask Award за вклад в Agile разработку.
“Mediocrity guaranteed.” This sad tagline describes most of the processes we use today including typical agile process. It’s easy to see why: software development is an expensive, risky business. To deal with the risk, we clearly separate responsibilities, creating a client-vendor model so that we know who’s accountable when things go wrong. Although we know things rarely go as planned, and innovative ideas rarely spring from such a relationship, we continue to work in processes where treating our coworkers as outsourced vendors is considered “best practice” and risking everything on the ideas of a select few isn’t regarded as risky.
This talk is about an alternative way of working.
In this talk, Jeff explores companies beginning to adopt a style of working where everyone in the organization gets involved with identifying and solving problems. You’ll hear examples from real companies describing their practices for learning first-hand about customers and users. You’ll learn about practices for collaboratively designing solutions for the problems found in the real world, and approaches for learning if what we created really benefited anyone. This new style of work is a process cocktail combining the best of agile development, lean software development and lean startup, user-centered design, and collaborative design thinking.
This style of work isn’t the traditional client-vendor model where knowing who’s to blame is the primary concern. It’s a co-making style of work where everyone brings their skills and experience to the table and together takes ownership for making great products.
Machine Learning Model Validation (Aijun Zhang 2024).pdf
Co-making Great Products
1. Co-Making
Great Products
How whole teams work together to find problems,
invent solutions, and deliver great products
Jeff Patton
jeff@comakewith.us
twitter: @jeffpatton
30. Process ≠ Skill
knowing how doesn’t make you good
Roles ≠ Positions
You might primarily do one thing, but you can’t
win by doing only one thing
Finishing On Time ≠ Winning
Keep score, don’t just keep time
30
32. 32
It seems like common sense
There
is nothing
more uncommon
than common
sense.
Understand the
problem you’re solving
& focus on specific
problems
Consider lots
of possible
solutions Sco$sh'Mathema-cian'
Thomas'Chalmers
Make sure it’ll
work before
investing big
46. GameStorming is a good
manual for effective
collaborative work
46
Having a business meeting without
artifacts and meaningful space is like
meeting blindfolded with your hands
behind your back. Yes, you can do it, but
why would you want to?
101. “There were plenty of weak
spots that led to Microsoft's
disastrous December quarter,
but one that didn't get much
attention Thursday was how
badly the Zune did.”
--Ina Fried, CNet News,
January 2009
opportunity:#
integrated#music#
management#and#
portable#music#
player
www.comakewith.us,/Jeff/Pa3on,/jeff@comakewith.us/
It’s/only/a?er/delivery/that/we/really/
understand/value
101
102. If you think writing code is
hard, try making product
decisions
102
105. Snagajob’s been trying to crack the
same tough problem for close to a
year now
Most of Nordstrom’s weekly
experiments don’t result in rolling
out a new product
Edmunds.com has built, tried, and
thrown away dozens of ideas
105
106. What team members
say is telling
106
What#we’re#doing#
really#maIers
Everyone’s#
working#directly#with#our#
clients#now
We’ve#found#
simple#ideas#that#now#
generate#millions#in#
revenue#every#year
When#there’s#
problems,#teams#dig#in,#and#
figure#out#a#schedule#to#stay#and#
solve#problems.##No#one#asks#
them#to.
The#new#site#
generates#the#same#revenue#
with#a#frac0on#of#the#features#
and#code#[#and#our#customers#
like#it#beIer
People#are#just#
happier
107. “It’s not easy. We’ve got lots
of problems.
But there’s no going back.”
107
108. Co-Making
Great Products
How whole teams work together to find problems,
invent solutions, and deliver great products
Jeff Patton
jeff@comakewith.us
twitter: @jeffpatton
Questions?