Upload
jeremy-kriegel
View
115
Download
1
Tags:
Embed Size (px)
DESCRIPTION
Citation preview
SuccessfulAgile/UXJeremy Kriegel
UX Manager, CIDC
UXAgile
Culture is not about what is absolute, real, or true. it’s 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
Agenda
• Agile & Scrum Basics• Project Initiation• Design in Sprints
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
18 minutes
Any Questions?
Marshmallow Challenge Lessons
Who does well?
Who does well?
Learn more marshmallowchallenge.com
http
://w
ww
.ena
gilit
y.co
m/
Agile 101
Agile is coming!
A minute to learn, a lifetime to master
Why agile?• Faster value to market• More responsive to change• More collaboration• More control
Discover Define
DesignDevelop
Deliver
Deploy
Decide
Defen
d
Agile gives you the
to define a process that exactly meets your
needs
FREEDOM
Agile gives you the
to define a process that exactly meets your
needs
RESPONSIBILITY
Origin of Agile
Extreme
ProgrammingSCRUM
DSDM
Adaptive
Software
Development
Crystal
Feature-
Driven
DevelopmentPragmatic
Programming
Agile Manifesto
4 Values
12 Principles
Agile ManifestoWe 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
That is, while there is value in the items on the right, we value the items on the left more.
Processes & tools
Comprehensive doc
Contract negotiation
Following a plano
ver
Agile Manifesto
4 Values
12 Principles
Principles Behind Agile
Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
Principles Behind Agile
Deliver working 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.
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.
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.
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.
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.
agilemanifesto.org
Agile
Why
What
SCRUM
SCRUM
3 Roles
4 Rituals
3 Artifacts
Roles
• Product Owner• Team• Scrum Master• Stakeholder
Pigs & Chickens
Product Backlog
Value
Outcome
Feature
Work
Bug
Iteration Planning
Product Backlog Iteration Backlog
WARNINGNO SCOPE CHANGES
except…
Daily Scrum
The 3 Questions
• What have you done since the last meeting?
• What will you be working on until the next meeting?
• Are you blocked?
Burndown
Demo
Retrospective
Insanity
Iteration PlanningProduct Backlog
New Iteration Backlog
Undone Work
Overview
Product Backlog
Iteration Backlog
Iteration
Scrum
Working Software
IterationPlanning
Demo & Retro
Snowman
Release
Iteration
Scrum
Caveats
J CurveProductivity
Time
Any cooks?
Other negatives
• Rework• Missed edge cases• Overemphasis on deadlines &
engineering
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
Process design is what we do
The Project
Patients Dr. & Staff Pharmacists
Getting Started
Sprint 0
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
Done?
Specific
Measurable
Achievable
Relevant
Timelyhttp://www.projectsmart.co.uk/smart-goals.html
Who?
User Stories
User Stories
As a (persona) ,
I would like to (action) ,
so that (value) .
Photo by David Paul Ohmerhttp://www.flickr.com/photos/the-o/
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.
Images via ifixit.com
INVEST in Stories
Independent
Negotiable
Valuable
Estimable
Small
Testable
Write Stories
Story Map
Demo
Retro
Planning
Go!
Demo
Retro
Planning
Go!
Demo
Retro
http://agileproductdesign.com/blog/the_new_backlog.html
Vision
Final thoughts
One last thinghttp://speakerrate.com/jkriegel