Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan


Guidelines and tips
Guidelines and tips

User Stories for project management, Study Guides, Projects, Research of Software Project Management

User Stories for project management

Typology: Study Guides, Projects, Research

2016/2017

Uploaded on 10/11/2017

bharath-kumar-1
bharath-kumar-1 🇮🇳

1 document

1 / 17

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Christoph)Mathis
Life%Cycle%of%a%User%Story
Combining%a%Lean%and%an%Agile%Perspec9ve
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff

Partial preview of the text

Download User Stories for project management and more Study Guides, Projects, Research Software Project Management in PDF only on Docsity!

Christoph Mathis Life Cycle of a User Story Combining a Lean and an Agile Perspec9ve

Why Agile Planning

Planning by Tasks Planning by Features Business Logic GUI Persistence Business Logic GUI Persistence

Agile Planning breaks down Features, not Ac9vi9es

  1. Re-­‐Planning becomes easier (possible?)
  2. Customer gets regular values from the value chain
  3. Teams gain autonomy on pieces of work

User Stories slice requirements into valueable pieces

Why User Stories My purpose is to maintain a balance of poli,cal power between business and development. Use cases as I have seen them used are complex and formal enough that business doesn't want to touch them. This leads to development asking all the ques,ons and wri,ng down all the answers and taking responsibility for the resul9ng corpus. Business is reduced to siRng on the other side of the table and poin9ng. I want a very different dynamic. I want business to feel ownership of and take responsibility for the care and maintenance of "the requirements". I want business to feel comfortable making priority decisions about the requirements. I want business to feel free to add new requirements , and add new detail to exis9ng requirements, as development progresses Kent Beck

Wish List Entry User Story Acceptance Tests Implemented Discarded Ready Done

Linear Backlog User Story Complex Product Conceptual integrity

User StoryUser Story User StoryUser Story User StoryUser Story

Strategy Epic Feature User Story Ready

... It is not a proper product specifica>on ... It is not a proper documenta>on ... It is not a delivery item

A beXer context to value the INVEST Criteria I ndependent N ego9able V aluable E s9mable S mall T estable shu-­‐ha-­‐ri

Thank You christoph.mathis@improuv.com New Book