developing user stories - beyond the basics

@Kubair www.sh i razee.com

User Stories – Beyond Basics


User Stories – more than an introduction

This deck takes a deep dive into components of a user story and provides guidance on developing individual components that make up a ‘Ready for Dev’ user story.

You will not need to define all the components detailed here for all your User Stories – use the common sense principle to determine the level of detail you drill down to for each User Story’s completeness


User Stories – the JEDI principle

User Stories represent the ‘Just Enough Documented Information’ (JEDi) required for a cross functional agile team to understand, analyse, size, estimate, design, develop and test an independent piece of functionality that holds value for the user(s).

Simplicity, independence, completeness and user value make for a good user story


User Stories – the C-Gaffsal principle

Completeness

Is complete at that point in time and open to negotiation and refinements

Goal Is to start a conversation with a real userAltitude Can vary (Mountain summit to grain of sand)

i.e. Epic to taskFormat A single sentenceFlexibility Is flexible to adaptation.Scope Is to create JEDI for a single activity/functionAdd-ons Feel free to scribble wireframe components to

add visuals to the storyLanguage Simple comprehensible


User Story – a refresher…le’format

As a < role >I want < activity >

so that < business value >Role - represents who is performing the action. It should be a single person, not a department. Activity – represents the action to be performed.Business Value – represents the value to the business. Why is this story important?

If you are struggling to find the business value of a User Story question its purpose! It may be a task that sits within a Story!


User Story – beyond basics

As a < role >I want < activity >

so that < business value >

Role - represents who is performing the action. It should be a single person, not a department. Activity – represents the action to be performed.Business Value – represents the value to the business. Why is this story important?But…there is More

to a User Story


User Stories – additional components


User Stories – additional components contd.


Thank you.If you got value from what I have shared please consider giving back by contributing to @BringPTP, you can follow, broadcast or donate: http://gofundme.com/bringptp

Peace Through Prosperity (PTP) improves the local/domestic environment for peace by nurturing prosperity. PTP alleviates poverty through empowering micro-entrepreneurs with knowledge, skills, ability and increasing their access to income and opportunities. PTP supports small businesses, owned/managed by vulnerable and marginalized individuals/groups in society.

PTP is innovating program design and delivery by using Agile design and delivery frameworks to create and deliver low cost, immediate and lasting

impact programs in ‘at risk’ communities. www.bringptp.com

http://gofundme.com/bringptp

http://gofundme.com/bringptp

http://www.bringptp.om/

developing user stories - beyond the basics

Software