Being Agile, Being Good Stephanie Troeth Paris Web, 2009 - - PowerPoint PPT Presentation

▶
being agile being good
SMART_READER_LITE
LIVE PREVIEW

Being Agile, Being Good Stephanie Troeth Paris Web, 2009 - - PowerPoint PPT Presentation

Jul 17, 2023 174 likes •902 views

Being Agile, Being Good Stephanie Troeth Paris Web, 2009 Stephanie Troeth co-founder/CTO, Book Oven Previously: UX consultant and mercenary product manager for startups Director of Interactive Technology at an agency What I

slide-1
SLIDE 1

Being Agile, Being Good

Stephanie Troeth Paris Web, 2009

slide-2
SLIDE 2

Stephanie Troeth

co-founder/CTO, Book Oven

Previously:

✦

UX consultant and mercenary product manager for startups

✦

Director of Interactive Technology at an agency What I don’t get paid for:

✦

Web Standards Project (WaSP) member since 2002

✦

WaSP InterAct

✦

Open Web Education Alliance

slide-3
SLIDE 3

Meeting point: agile & quality

slide-4
SLIDE 4

“Agile” is not a single solution, but is a group of software development methodologies that share the same core principles.

slide-5
SLIDE 5

An Agile Approach — “Agile Estimating & Planning”, Mike Cohn

slide-6
SLIDE 6

Work as a team.

slide-7
SLIDE 7

Work in short iterations.

slide-8
SLIDE 8

Deliver something each iteration.

slide-9
SLIDE 9

Focus on business priorities.

slide-10
SLIDE 10

Inspect & adapt.

slide-11
SLIDE 11

Compared to the familiar waterfall:

less documentation less “fixed” process less (long term) planning = perceived chaos

slide-12
SLIDE 12

The philosophy behind agile is that you never start with a perfect plan.

slide-13
SLIDE 13

It is a method for dealing with the unknown, and to use new knowledge to guide

  • ngoing work.
slide-14
SLIDE 14

Quality: what is it?

slide-15
SLIDE 15

It is easy to think that quality results from a process.

slide-16
SLIDE 16

It is easy to think that quality results from a process.

people

slide-17
SLIDE 17

“The best teams didn’t have a methodology

  • r dogma they followed.

The struggling teams often tried following a methodology, without success. [...] The best teams all focused on increasing the techniques and tricks for each team member.”

— Jared Spool & User Interface Engineering

http://www.slideshare.net/jmspool/journey-to-the-center-of-design

slide-18
SLIDE 18

“But if Quality and excellence is seen as the ultimate reality then it becomes possible for more than one set of truths to exist.”

— “Lila”, Robert M. Pirsig.

slide-19
SLIDE 19

Quality is relative.

slide-20
SLIDE 20

what is valuable to me != what is valuable to you.

slide-21
SLIDE 21

Apply this to a team scenario:

what a designer deems as quality != what a developer deems as quality != what a project manager deems as quality ... etc.

slide-22
SLIDE 22

So how does a team define quality, if we all have different and often contradictory ideas of “what is good”?

slide-23
SLIDE 23
  • 1. The Stealth Method:

Foster a strong team culture that thirsts for quality.

slide-24
SLIDE 24

Understand what each other needs to succeed...

slide-25
SLIDE 25

... so each of us can take pride in what we do.

slide-26
SLIDE 26

Pride is a big motivator.

slide-27
SLIDE 27

2) The Measurable Method:

Instill a quality vision as a belief system.

slide-28
SLIDE 28

A belief system is stronger than any process.

slide-29
SLIDE 29

Empower members in your team. Enable them to decide what is the right thing to do.

slide-30
SLIDE 30

A quality vision definition:

✦ generic enough so that it can be

interpreted in each context

✦ specific enough so it contains a

clear vision

slide-31
SLIDE 31

An example of a quality vision

✦ accessible ✦ aesthetic ✦ usable ✦ measurable ✦ findable ✦ interoperable ✦ relevant ✦ robust ✦ secure ✦ cost-effective ✦ scalable ✦ refactorable ✦ valuable

90% of sites we produce should be

slide-32
SLIDE 32

An example of a quality vision

We want our product to be usable, easy and delightful to use for our target audience.

slide-33
SLIDE 33

Use a quality vision to decide:

✦ what level of training all team members need ✦ what level of work is globally expected from them ✦ enable them to decide the right thing to do.

slide-34
SLIDE 34

Hire wisely.

slide-35
SLIDE 35

Tips, tricks & (some) techniques

slide-36
SLIDE 36

Use user stories

As a user I would like to see the history of a page so I can work out who did what.

slide-37
SLIDE 37

“A user can pay for access with a credit card.”

✦ Test with Visa, MasterCard and American Express. ✦ Test with Diner’s Club. ✦ Test with good, bad and missing card ID numbers ✦ Test with expired cards. ✦ Test with different purchase amounts (including

  • ne over the card’s limit).

A user story with acceptance test cases: — “User Stories Applied”, Mike Cohn

slide-38
SLIDE 38

User stories:

✦ provide a user-oriented approach to defining

requirements

✦ break the task of building into estimable chunks ✦ facilitate a discussion about what we’re building ✦ make it easy to prioritize what’s important to

build

slide-39
SLIDE 39

User stories:

✦ allow team members to interpret requirements ✦ allow team individuals to take ownership of the

solution

✦ are testable ✦ means no more 200+ pages of specifications!

slide-40
SLIDE 40

Trick: Document only as needed, especially decisions.

slide-41
SLIDE 41

Estimation & planning

slide-42
SLIDE 42

Method #1: Relative story points

slide-43
SLIDE 43

Assign relative points to each story. As time progresses, you get a better idea of your burn rate based on your team’s velocity.

slide-44
SLIDE 44

Assign relative points to each story. As time progresses, you get a better idea of your burn rate based on your team’s velocity.

slide-45
SLIDE 45

Method #2: The 4-hour bucket model.

slide-46
SLIDE 46

Split your stories so that they fit in an approximate half-day slot. Some will be bigger, some smaller, but eventually they balance out.

slide-47
SLIDE 47

Trick: Let your team own the task of estimating.

slide-48
SLIDE 48

Evaluate: are we too optimistic

  • r too pessimistic?

Rinse & repeat.

slide-49
SLIDE 49

Design & User Experience

— “12 emerging best practices for adding UX to agile development”, Jeff Patton

http://agileproductdesign.com/blog/emerging_best_agile_ux_practice.html

slide-50
SLIDE 50

Agile methodology states: everything happens in the same iteration.

slide-51
SLIDE 51

But as a designer or a UX specialist, what do you need to succeed?

slide-52
SLIDE 52

Designers need time to research, and to synthesise product and visual design.

slide-53
SLIDE 53

Trick: “Work ahead & follow behind”

— #4, “12 emerging best practices for adding UX to agile development”, Jeff Patton

slide-54
SLIDE 54

Quality Assurance

slide-55
SLIDE 55

There’s no magic: Make time to care.

slide-56
SLIDE 56

Employ test-driven design and development.

slide-57
SLIDE 57

Method #1: Hire a QA person or team.

slide-58
SLIDE 58

Method #2: Set aside QA and refactoring days.

slide-59
SLIDE 59

Trick: Keep, reuse and add to a comprehensive list of all use cases

  • r user stories that must pass

before each release.

slide-60
SLIDE 60

Quality doesn’t need to be assured, it needs to be cultivated.

slide-61
SLIDE 61

Why do we insist on quantifying quality?

slide-62
SLIDE 62

Good work comes from good habits.

slide-63
SLIDE 63

A vision that allow your team members to judge critically is more powerful than any process.

slide-64
SLIDE 64

Identify accountability.

slide-65
SLIDE 65

Identify what each other need in

  • rder to succeed.
slide-66
SLIDE 66

The agile approach encourages good habits but it’s up to your team to decide what you collectively want to be.

slide-67
SLIDE 67

Empower your team.

slide-68
SLIDE 68

Give each other a sense of pride.

slide-69
SLIDE 69

What do monkeys, a banana, and a web team have in common?

slide-70
SLIDE 70

Quality should be the way that it has always been done.

slide-71
SLIDE 71

Thank you! Questions?

Stephanie Troeth

stephanietroeth.com hello@stephanietroeth.com http://www.slideshare.net/stephtroeth/presentations bookoven.com

slide-72
SLIDE 72

http://www.flickr.com/photos/dariuszka/264054626/ http://www.flickr.com/photos/johncarleton/16083172/ http://www.flickr.com/photos/32912172@N00/3369828460/ http://www.flickr.com/photos/cryztalvisions/343309195/ http://www.flickr.com/photos/mostudio/2384804297/ http://www.flickr.com/photos/mknott/3642179597/ http://www.flickr.com/photos/66164549@N00/2789668253/ http://www.flickr.com/photos/boojee/29777131/ http://www.flickr.com/photos/72213316@N00/3570803663/ http://www.flickr.com/photos/telstar/3174467026/ http://www.flickr.com/photos/76283671@N00/184612846/ http://www.flickr.com/photos/psd/3731275681/ http://www.flickr.com/photos/totalaldo/ http://www.flickr.com/photos/sfllaw/302647234/

With thanks