DESIGNERS
DESIGNS
PRODUCT MANAGER
WRITE USER
STORIES
ENGINEERS
WHAT IS A USER STORY?
A USER STORY IS THE CORE OF AGILE SOFTWARE PHILOSOPHY.
IT'S A USER CENTERED WAY OF WRITING A FEATURE OR PART OF
A FEATURE THAT SERVES THE BEGINNING INTENTIONS AND
APPROACH TO BUILDING A SPECIFIC PIECE OF SOFTWARE
—
WHO WRITES THE STORY?
MOST OF THE TIME THIS IS THE
TASK OF THE PRODUCT MANAGER.
DESIGNERS WILL GIVE PM'S
VALIDATED DESIGNS AND THE
PM WILL BREAK DOWN THE
DESIGN AND WRITE STORIES
FOR ENGINEERS TO REVIEW.
DESIGNERS WILL INCLUDE THE
SPECIFIC DESIGN TO THE STORY.
AT PIVOTAL, WE TEND TO PAIR
WITH PM'S ON STORIES.
—
THE USER STORY FRAME WORK:
AS A
GIVEN
I WANT TO
USER OR PERSONA NAME HERE
CONTEXT
DESCRIBE GOAL
WHEN
DESCRIBE U.I. ACTION #1
AND
DESCRIBE ACTION #2 (IF NEEDED)
I SEE
DESCRIBE U.I. OUTCOME
WHEN BREAKING DOWN YOUR DESIGNS AND INCLUDING THEM TO STORIES IT'S BEST TO:
INCLUDE A LINK TO DESIGN (NOT ATTACHMENTS)
INCLUDE HEX COLORS
INCLUDE HEX COLORS FOR THE HOVER STATES (IF WEB)
INCLUDE THE ERROR/SUCCESS STATES IF YOU HAVE ANY
DESCRIBE ANY IMPLEMENTATION DETAILS (FIXED ELEMENTS)
DESCRIBE & SHOW TRANSITION DETAILS (SLIDE UP)
INCLUDE ICONS AS PNG OR SVG FORMAT
INCLUDE PHOTOS AS PNG OR JPEG FORMAT
