Co-making Great Products
Джеф Паттон проектирует и разрабатывает ПО во множестве проектов, от интернет заказа деталей самолетов до электронных медицинских записей. Джеф нацелен на 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.
Recommended
Recommended
More Related Content
Viewers also liked
Viewers also liked (20)
Similar to Co-making Great Products
Similar to Co-making Great Products (20)
More from Magneta AI
More from Magneta AI (20)
Recently uploaded
Recently uploaded (20)
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
- 3. This team thinks about success differently 3
- 4. s 1. Safety isn’t success 2. Velocity isn’t value 3. The invention game 4. Deliberate discovery drives delivery 5. Reality bites 4
- 5. These three companies are focused on winning the software development game 5
- 8. Traditional sequential development process is safe for individuals 8
- 9. 9
- 10. 10
- 11. 11
- 12. 12
- 13. Separation of concerns is problematic for process 13
- 14. 14
- 15. 15
- 18. We’re not here to build software we’re here to change the world 18
- 20. R & D [requirements & design] 20
- 21. www.comakewith.us,/Jeff/Pa3on,/jeff@comakewith.us/ Deciding/what/to/build/is/difficult Fred#Brooks,#author#of#The#Mythical#Man#Month 21 The hardest single part of building a software system is deciding precisely what to build.
- 22. www.comakewith.us,/Jeff/Pa3on,/jeff@comakewith.us/ Our/decisions/become/ requirements Alistair/Cockburn,/author/of/Agile/So?ware/Development:/The/CooperaVve/Game 22 If it’s your decision to make, it’s design. If not, it’s a requirement.
- 27. Process 27
- 28. 7 http://hbr.harvardbusiness.org/1986/01/the-new-new-product-development-game/ar/1 “Under the rugby approach, the product development process emerges from the constant interaction of a hand- picked, multidisciplinary team whose members work together from start to finish.” From the 1986 Harvard Business Review paper “The New New Product Development Game” by Takeuchi and Nonaka
- 29. Game 29
- 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
- 31. 31 “Design Thinking” is a learning and invention game
- 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
- 33. www.comakewith.us,/Jeff/Pa3on,/jeff@comakewith.us/ 33 Different ways of thinking - NOT process roles, hand-offs, sequence and phases
- 34. www.comakewith.us,/Jeff/Pa3on,/jeff@comakewith.us/ 34 Study the world now, imagine and test the a new future world Now Later
- 35. www.comakewith.us,/Jeff/Pa3on,/jeff@comakewith.us/ 35 Learning happens outside the building Now Later
- 36. www.comakewith.us,/Jeff/Pa3on,/jeff@comakewith.us/ UX/Designers/act/as/experts/and/guides 36 Leah#Buley www.adapVvepath.com/aboutus/leah.php “Design isn’t a product that designers produce, design is a process that designers facilitate.” -- Leah Buley
- 37. 37
- 38. 38
- 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?
- 51. www.comakewith.us,/Jeff/Pa3on,/jeff@comakewith.us/ Discovery/compliments/delivery 51 Discovery Delivery Use/discovery/to/answer/ big/quesVons • What#problems# are#we#solving? • What#solu0on#do# people#want? • Can#people# effec0vely#use# our#solu0on? • Can#we#build#it#in# the#0me#we#have? Use/delivery/ to/execute • Plan#the#details • Design,#develop,## and#test • Measure# development#speed • Evaluate#progress • Evaluate#quality
- 55. Discovery teams build shared understanding of: • the present problems • the future world • the solutions we think will get us there 55
- 56. www.comakewith.us,/Jeff/Pa3on,/jeff@comakewith.us/ Discuss/and/model/to/build/shared/ understanding/of/the/current/and/future/world Gary Levitt, owner & designer of Mad Mimi 56
- 57. www.comakewith.us,/Jeff/Pa3on,/jeff@comakewith.us/ Story/Maps/help/us/build/shared/ understanding/about/the/future/world Gary Levitt, owner & designer of Mad Mimi 57 details • smaller steps • alternative steps • UI details • technical details workflow (from the user’s perspective) backbone (gives structure to the map) product goals (why build the product) users (what are their goals)
- 62. www.comakewith.us,/Jeff/Pa3on,/jeff@comakewith.us/ You’ll/need/to/leave/your/office/and/visit/ theirs 62
- 74. www.comakewith.us,/Jeff/Pa3on,/jeff@comakewith.us/ Everyone/parVcipates/in/sketching/ soluVon/idea 74
- 75. www.comakewith.us,/Jeff/Pa3on,/jeff@comakewith.us/ Take/a/li3le/quiet/Vme/and/sketch/ independently 75
- 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?