'

The Design Fortress: Boosting Design Productivity and Creativity in an Agile World

Понравилась презентация – покажи это...





Слайд 0

THE DESIGN FORTRESS Boosting Design Productivity & Creativity in an Agile World David Randall • @davidkrandall • davidkrandall.com


Слайд 1


Слайд 2

ABOUT YOU


Слайд 3

PHILOSOPHY TOOLS PROCESS AND TACTICS


Слайд 4

THE BACK STORY


Слайд 5


Слайд 6


Слайд 7


Слайд 8

WHY IS ENTERPRISE SOFTWARE SO HARD?


Слайд 9


Слайд 10


Слайд 11


Слайд 12


Слайд 13

AT PIVOTAL EVERYTHING CHANGED FOR ME, BECAUSE I SAW THIS AMAZING DEVELOPER PROCESS


Слайд 14


Слайд 15

PAIR PROGRAMMING TEST DRIVEN DEVELOPMENT ITERATION PLANNING PIVOTAL TRACKER WEEKLY RETROS


Слайд 16

I GOT JEALOUS


Слайд 17

I STARTED TO UNDERSTAND THE CHALLENGES OF DESIGN + AGILE


Слайд 18


Слайд 19

I STARTED SEEING THE BOUNDARY OF THE CRAFTSMAN MODEL


Слайд 20


Слайд 21

“ To be competitive we need institutionalization. We need a process driven approach. Because at the end of the day, none of us is as smart as all of us.


Слайд 22

•  Keep Teams Consistent •  Be Proactive Not Reactive •  Have a Dedicated Scrum Master, Especially at the Beginning •  UX Must Work at Least One Step Ahead of the Sprint


Слайд 23

•  Keep Teams Consistent •  Be Proactive Not Reactive •  Have a Dedicated Scrum Master, Especially at the Beginning •  UX Must Work at Least One Step Ahead of the Sprint


Слайд 24

THE DESIGN FORTRESS: 5 KEY PRINCIPLES FOR AGILE DESIGN


Слайд 25


Слайд 26

DESIGNERS WHO WORK ON LOTS OF PROJECTS DESIGNERS WHO WORK WITH DEVELOPERS


Слайд 27

1. START DESIGN AHEAD OF DEVELOPMENT


Слайд 28

1. START DESIGN AHEAD OF DEVELOPMENT •  •  •  •  Discovery + Framing 2-4 Weeks Insights and early prototypes Not a finished design


Слайд 29


Слайд 30

1. START DESIGN AHEAD OF DEVELOPMENT •  Keys to Success –  Keep it agile –  Stakeholders and Product Owners Involved –  Flexibility at the end


Слайд 31

2. CREATE A INDEPENDENT, ELECTRONIC DESIGN BACKLOG


Слайд 32


Слайд 33


Слайд 34


Слайд 35

2. CREATE AN INDEPENDENT, ELECTRONIC DESIGN BACKLOG •  Helps design float above lumpy dev and PM needs •  Enables prioritization of research and nonmockup related tasks •  Allow the problem and the solution to be documented, saved and linked


Слайд 36


Слайд 37


Слайд 38


Слайд 39


Слайд 40

3. USE SMALL, DELIVERABLE BASED DESIGN TASKS


Слайд 41

3. USE SMALL, DELIVERABLE BASED DESIGN TASKS •  •  •  •  •  Project > Epic > Story > Task Not true user stories Eliminate the muddy middle Finish line No (bad) surprises


Слайд 42

3. USE SMALL, DELIVERABLE BASED DESIGN TASKS Review   the  front   page   Finish   Se3ngs   Screen  


Слайд 43

3. USE SMALL, DELIVERABLE BASED DESIGN TASKS


Слайд 44


Слайд 45

3. USE SMALL, DELIVERABLE BASED DESIGN TASKS •  Bonus: Pointing


Слайд 46

4. DELIVER DESIGN TO A PRODUCT OWNER


Слайд 47

WE DON’T MAKE PRODUCTS, WE MAKE PLANS


Слайд 48

4. DELIVER DESIGN TO A PRODUCT OWNER •  Keeps development and business constraints in view •  Avoids fuzzy acceptance and rework


Слайд 49


Слайд 50


Слайд 51

5. CREATE A DESIGN ACCEPTANCE ENVIRONMENT


Слайд 52

FEW THINGS ARE MORE TRAGIC THAN A PERFECTLY IMPLEMENTED, OUT OF DATE DESIGN


Слайд 53

5. CREATE A DESIGN ACCEPTANCE ENVIRONMENT •  Share all of your work all the time –  Sketch > Invision •  Only share links, never attach images •  Make every flow as complete as possible –  Symbols, Styles, Libraries •  Buy a URL


Слайд 54


Слайд 55


Слайд 56


Слайд 57

THE DESIGN FORTRESS: 5 KEY PRINCIPLES 1.  Start Design Ahead of Development 2.  Create a Independent, Electronic Design Backlog 3.  Use Small, Deliverable Based Design Tasks 4.  Deliver Design to a Product Owner 5.  Create a Design Acceptance Environment David Randall • @davidkrandall • davidkrandall.com


Слайд 58


×

HTML:





Ссылка: