successful agile/ux

Download Successful Agile/UX

Post on 27-Jan-2015

102 views

Category:

Technology

0 download

Embed Size (px)

DESCRIPTION

 

TRANSCRIPT

  • 1. SuccessfulAgile/UX
    Jeremy Kriegel
    UX Manager, CIDC

2. Agile
UX
3. Culture is not about what is absolute, real, or true. its about what a group of people get together and agree to believe.
Culture can be healthy or toxic, nurturing or murderous. Culture is made of stories...
Thom Hartmann, author
4. 5. 6. 7. Agenda
Agile & Scrum Basics
Project Initiation
Design in Sprints
8. Your Goals
workflow in relation to web design/visual design
a list (or "toolbox") of UX design methods adjusted for Agile, that can be used based on specific project needs (e.g., RITE testing, paired design/development, Design Studio, Story Mapping, etc.)
More detail on Design Studio (a la Jim Ungar) and Story Mapping (a la Jeff Patton), and when they should take place?
I attended the Bentley Usability Bootcamp in 2006. How out of date am I in my UCD approach?
How can Agile work with 3 types of projects: Design from scratch, open source and implement commercial, off-the-shelf products?
staggering design and code tasks
architecture and design done piecemeal
adding to a legacy application
design controls artifacts for the fda and agile
9. 10. 11. 12. 13. 18 minutes
14. Any Questions?
15. 16. Marshmallow Challenge Lessons
17. Who does well?
18. Who does well?
19. 20. 21. Learn more marshmallowchallenge.com
22. 23. http://www.enagility.com/
24. Agile 101
25. Agile is coming!
26. 27. 28. 29. 30. A minute to learn, a lifetime to master
31. 32. Why agile?
Faster value to market
More responsive to change
More collaboration
More control
33. 34. 35. Define
Discover
Design
Develop
Decide
Deploy
Defend
Deliver
36. 37. 38. Agile gives you the
FREEDOM
to define a process that exactly meets your needs
39. Agile gives you the
RESPONSIBILITY
to define a process that exactly meets your needs
40. DSDM
Extreme Programming
SCRUM
Crystal
Origin of Agile
Adaptive Software Development
Feature-Driven Development
Pragmatic Programming
41. Agile Manifesto
4 Values
12 Principles
42. Agile Manifesto
We are uncovering better ways of developing software by doing it and helping others do it.
Through this work we have come to value:
Individuals & interactions
Working software
Customer collaboration
Responding to change
Processes & tools
Comprehensive doc
Contract negotiation
Following a plan
over
That is, while there is value in the items on the right, we value the items on the left more.
43. Agile Manifesto
4 Values
12 Principles
44. Principles Behind Agile
Our highest priority is to satisfy the customer through early and continuous deliveryof valuable software.
Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
45. Principles Behind Agile
Deliverworking software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
Business people and developers must work together daily throughout the project.
46. Principles Behind Agile
Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
47. Principles Behind Agile
Working software is the primary measure of progress.
Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
48. Principles Behind Agile
Continuous attention to technical excellence and good design enhances agility.
Simplicity--the art of maximizing the amount of work not done--is essential.
49. Principles Behind Agile
The best architectures, requirements, and designs emerge from self-organizing teams.
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
50. agilemanifesto.org
51. Agile
52. What
Why
53. SCRUM
54. 55. 56. 57. SCRUM
3 Roles
4 Rituals
3 Artifacts
58. Roles
Product Owner
Team
Scrum Master
Stakeholder
59. Pigs & Chickens
60. Product Backlog
Value
Outcome
Feature
Work
Bug
61. Iteration Planning
Iteration Backlog
Product Backlog
62. WARNING
NO SCOPE CHANGES
except
63. Daily Scrum
64. The 3 Questions
What have you done since the last meeting?
What will you be working on until the next meeting?
Are you blocked?
65. Burndown
66. Demo
67. Retrospective
68. Insanity
69. Iteration Planning
New Iteration
Backlog
Undone
Work
Product
Backlog
70. Overview
Scrum
Iteration
Planning
Iteration
Backlog
Iteration
Product
Backlog
Working Software
Demo & Retro
71. Snowman
Scrum
Iteration
Release
72. Caveats
73. J Curve
Productivity
Time
74. Any cooks?
75. 76. 77. Other negatives
Rework
Missed edge cases
Overemphasis on deadlines & engineering
78. A lot of potential
Real feedback faster
Closer ties to stakeholders and developers
Faster, less effort on low importance features
Pervasive understanding of UX
Real User focus
Less waste, decide as late as responsible
79. 80. Process design is what we do
81. The Project
82. Patients
Dr. & Staff
Pharmacists
83. Getting Started
84. Sprint 0
85. Sample Goals
Define problem/benefit
Prioritized and measurable goals
Contractual obligations
Target users and their goals
Key assumptions that need to be validated by research
Relationship of users to business goals
User tasks or scenarios
Refined, estimated, and prioritized stories
Release roadmap
86. Done?
87. SpecificMeasurableAchievableRelevantTimely
http://www.projectsmart.co.uk/smart-goals.html
88. Who?
89. User Stories
90. User Stories
As a(persona) ,
I would like to(action) ,
so that(value) .
91. 92. Photo by David Paul Ohmer
http://www.flickr.com/photos/the-o/
93. 94. example
As a gardener, I want a shovel so that I can dig a hole
As a gardener, I want to dig a hole so that I can plant a tree
As a gardener, I want to plant a tree so I can have some shade.
95. 96. Images via ifixit.com
97. 98. INVEST in Stories
Independent
Negotiable
Valuable
Estimable
Small
Testable
99. Write Stories
100. Story Map
101. 102. 103. Demo
104. Retro
105. Planning
106. Go!
107. Demo
108. Retro
109. Planning
110. Go!
111. Demo
112. Retro
113. Vision
http://agileproductdesign.com/blog/the_new_backlog.html
114. Final thoughts
115. One last thing
http://speakerrate.com/jkriegel