Agile DC 2015: Be More Than a Proxy

Be more than a proxy Diane Zajac-Woodie AGILE DC 2015

green jeans consu l t i ng

Coke or Pepsi?


Cat or Dog?


Apple or Android?


Agenda •  Why requirements are not enough

•  What is a proxy?

•  How BAs/POs can help their agile teams

•  Story Maps

•  Requirements as acceptance tests

•  Wrap up and Q&A


Product: Origami Flower



Folding in Silos


1.  Assign a BA, rest of team are developers.

2.  BA comes up for a handout. DO NOT SHOW YOUR DEVELOPERS!

3.  Move chairs so BA can’t see developers working

4.  BA verbalizes requirements for Side #1 to the developers while the developers build.


How’s it going?


Folding w/ Feedback 1.  BA can see what the

devs are doing – DO NOT SHOW YOUR DEVELOPERS the handout!

2.  BA verbalizes the requirements while the developers build AND provides feedback

How did that go?


Definition

 noun: A person who is given power or authority to act on behalf of someone else, especially in voting


What do teams need?  1. Silently make two lists.

- BA/PO can help with these

 - BA/PO can’t help with these


BA/PO can help

with these

BA/PO can’t

help with these

 2. Write down all the things that teams need, placing the items on the appropriate list.

•  System Access

•  Proper equipment

•  Continuous Integration

•  TDD training

•  Configure automated regression test suite


BA/PO can help

with these

BA/PO can’t

help with these

•  Collaboration

•  Feedback

•  Requirements

•  Release planning

•  Team Space

•  Facilitation

•  Documentation

•  Info Radiators

•  SME’s

•  Testing

•  User stories

•  Stakeholder management

•  Continuous improvement

•  Management support

•  Team agreements

What Changes •  Meetings




•  Less formal documentation

•  Greater need for facilitation


 “The single biggest problem in communication is the illusion

that it has taken place.”  - George Bernard Shaw-



•  Less Formal Documentation

•  Greater need for facilitation

•  Requirements are “just-in-time”

•  Requirements as acceptance tests



Story Mapping


Sharing Posts 1. Create Post

a.  Write post b.  Add location c.  Add photo d.  Mention other users e.  Use hashtag

Sharing Posts

CreatePost

Write post

Add location

Add photo

Mention other users

Use hashtag

Story Mapping


Sharing Posts 1. Create Post

a.  Write post b.  Add location c.  Add photo d.  Mention other users e.  Use hashtag

Sharing Posts

CreatePost

Write post

Add location

Add photo

Mention other users

Use hashtag

Story Mapping

2. Share Posts a.  Share post

Share Posts

Share post


Story Map


Story Map – w/ releases

Requirements •  Ubiquitous language


•  Collaborative

•  Verifiable (Ideally “automate-able”)

•  Just in Time

Feature: As a conference attendee I want to search for AgileDC tweets So that I know what’s happening


Scenario: Find a conference tweet w/ a photo by hashtag Given I am signed in to Twitter

When I tweet a selfie with the #AgileDC conference hashtag Then my tweet is in the #AgileDC search results

Scenario: Find a conference tweet w/o using “#” symbol Given I am signed in to Twitter When I search for the AgileDC conference Then AgileDC conference tweets appear in search results

Scenario: Find a conference tweet by hashtag Given I am signed in to Twitter When I post with the #AgileDC conference hashtag Then my tweet is in the #AgileDC search results

Acceptance Tests •  Easy to understand?


•  Could you work on it together?

•  Easily testable?

•  Just in Time


Scenario: Find a conference tweet by hashtag

Scenario: brief description of desired behavior

Given is set up, what has to happen before the test

When is the action, the trigger

Then is the test, the expected behavior

Given I am signed in to Twitter When I post with the #AgileDC conference hashtag Then my tweet is in the #AgileDC search results

Feature: As a conference attendee I want to search for AgileDC tweets So that I know what’s happening

Feature: brief description of goal, user story clarified

Writing Acceptance Criteria


Scenario: brief description of desired behavior

Given is set up, what has to happen before the test

When is the action, the trigger

Then is the test, the expected behavior

Feature: brief description of goal, user story clarified As a… I want… So that…

1.  Select a User Story & write a Feature 2. Write 2-3 Scenario descriptions 3. Write the Given/When/Then’s for your scenarios


Writing (continued) 4. Swap tests with the pair next to you 5. Read their scenarios & provide some feedback

•  Is the goal of the user story clear (Feature)? •  Is there a set up (Given)? •  Is there an action (When)? •  Is there a clear test (Then)?

1.  One Validation: write down one thing that you heard that validated what you already knew

2.  One New Idea: write down one new idea that you learned

3.  One Next Step: Write down one next step that you will do because you came to this session.

4.  Share with your neighbor.


Session Feedback Please leave me a note with any feedback.

Any and all feedback is appreciated!

Thanks for being here!


Diane Zajac-Woodie @AgileSquirrel [email protected] www.greenjeansconsulting.com

Resources  Story Mapping: http://winnipegagilist.blogspot.com/

 http://www.agileproductdesign.com/blog/the_new_backlog.html

 Electronic Story Boards: https://cardboardit.com/ or

 https://www.featuremap.co/en

 Cucumber tool: https://cucumber.io/

 History of BDD: http://dannorth.net/introducing-bdd/

 More BDD: http://lizkeogh.com/behaviour-driven-development/


Image Attribution   Flower scribble:

http://www.swiss-miss.com/wp-content/uploads/legacy/photos/uncategorized/2008/10/08/isd004o_3.jpg

  Origami gone wrong: http://www.origamisources.com/origami_sightings_comedy.htm   Couple sitting back-to-back:

https://computing.ece.vt.edu/~santol/projects/zsl_via_visual_abstraction/interact/interact_stand-alone_dataset/imgs/2SMB2YU98JHSGUO94V6BP9ITU61NBC_09.jpg

  Story Map: http://winnipegagilist.blogspot.com/2012/03/how-to-create-user-story-map.html   Coke:

http://pizzaforcoins.com/media/catalog/product/cache/1/image/9df78eab33525d08d6e5fb8d27136e95/2/_/2_liter_coke.jpg

  Pepsi: http://b.fastcompany.net/multisite_files/fastcompany/slideshow/2013/12/3023648-slide-1-pepsi-can.jpg

  ATM: http://www.marshallstreetcheckcashing.com/wp-content/uploads/2015/02/atm.gif   Bank Teller: http://cliparts.co/cliparts/Lcd/orE/LcdorELxi.jpg


Technology

Agile DC 2015: Be More Than a Proxy