21. Story Mapping: Example (fictional new user workflow)
User Registration
Enter
Registration
Flow
Landing Page
Render
Landing Page
Call To Action
Step 1: Name
and Email
Render Step 1
blank page
User enters
name + email
Submit
Step2:
Address &
Phone
Render Step 2
page w/fields
User enters
name + email
User Submits
Address
validation
User reviews
info &
submits
User reviews
info entered
Submit
User edits
info prior to
submit
User enters
edit mode
User changes
info
User returns
to review
User granted
access
Back end data
validation
Info committed
to DB
Confirmation
email sent
User sees
confirmation
screen
Render success
message
Login CTA
User logs in
First login
welcome promo
User Logs In
for the First
Time
Registration CompleteReview Registration Information
User Enters Demographic
Information
MVPVersion2
Targeted
messaging
User entered in
rewards system
Deferred
Front end
validation
Time
Priority
22. Story Mapping: Example (fictional user story)
User Registration – Step 1 – Enter Name & Email
As a new member I would like to become a registered user so that I can login to systems, get access to services, be addressed
by name and receive email communications from WeWork.
Acceptance Criteria
● User is presented with clearly labeled fields for email address, first name and last name
● Tool tips and error messages are provided to the user as needed
● Front end validations will be limited to ensuring that data is in all fields and the email address is properly formatted
● Wireframes will be delivered based on the specification above
● A copy deck, including all labels, tooltips, error messages...etc. will be provided
● Working code will be deployed to staging environment
Tasks
● Wireframes
● Visual Design
● Copy Deck
● Business Review
● Development Review
● Stakeholder review
● Development
● UX Review
● QA
● Final Acceptance
Notes
● OKR: Growth of user base by decreasing friction in registration process and increasing user satisfaction.
● Link to user flows: http:xxx.xxx.xxxxxx
● We will not be checking the database to see if the email address already exists at this step in the process for xyz reasons.
Entered in the
description field
Entered in the
story name field
23. Story Writing: Splitting a Story Pt 1 (fictional)
User Registration – Step 1 – Enter Name & Email – Design
As a new member I would like to become a registered user so that I can login to systems, get access to services, be addressed
by name and receive email communications from WeWork.
Acceptance Criteria
● User is presented with clearly labeled fields for email address, first name and last name
● Tool tips and error messages are provided to the user as needed
● Front end validations will be limited to ensuring that data is in all fields and the email address is properly formatted
● Wireframes will be delivered based on the specification above
● A copy deck, including all labels, tooltips, error messages...etc. will be provided
● Working code will be deployed to staging environment
Tasks
● Wireframes
● Visual Design
● Copy Deck
● Business Review
● Development Review
● Stakeholder review
● Development
● UX Review
● QA
● Final Acceptance
Notes
● OKR: Growth of user base by decreasing friction in registration process and increasing user satisfaction.
● Link to user flows: http:xxx.xxx.xxxxxx
● We will not be checking the database to see if the email address already exists at this step in the process for xyz reasons.
Entered in the
description field
Entered in the
story name field
24. Story Writing: Splitting a Story Pt 2 (fictional)
User Registration – Step 1 – Enter Name & Email – Development
As a new member I would like to become a registered user so that I can login to systems, get access to services, be addressed
by name and receive email communications from WeWork.
Notes
● OKR: Growth of user base by decreasing friction in registration process and increasing user satisfaction.
● Link to user flows: http:xxx.xxx.xxxxxx
● Added: Link to wireframes & copy deck: http:xxx.xxx.xxxxxx
● We will not be checking the database to see if the email address already exists at this step in the process for xyz reasons.
Acceptance Criteria
● User is presented with clearly labeled fields for email address, first name and last name
● Tool tips and error messages are provided to the user as needed
● Front end validations will be limited to ensuring that data is in all fields and the email address is properly formatted
● Wireframes will be delivered based on the specification above
● A copy deck, including all labels, tooltips, error messages...etc. will be provided
● Working code will be deployed to staging environment
Tasks
● Wireframes
● Visual Design
● Copy Deck
● Business Review
● Development Review
● Stakeholder review
● Development
● UX Review
● QA
● Final Acceptance
Entered in the
description field
Entered in the
story name field
27. _ Take turns.
_ Resist interrupting.
_ If you’re worried about forgetting what you have to say, write it down.
_ Practice active listening.
_ Make sure that everyone has a chance to be heard.
_ Respect other people’s perspectives and experience.
_ No multitasking.
_ Remember the engineering ground rules. (facts, not opinions)
_ Resist going off topic.
Conversation Ground Rules
28. 1. What went well?
2. What didn’t go well?
3. What started off poorly but
improved over the quarter?
Three Questions