Skip to main content

Home/ BARE+IA Requirements Engineering Information&Business Analysis/ Group items tagged user story

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Peter Van der Straaten

BDD,Cucumber,Gherkin,User Stories,use cases,TDD - IT Jobs Watch Search - 0 views

www.itjobswatch.co.uk/default.aspx

specification development BDD TDD EPO Agile requirements engineering business analysis

shared by Peter Van der Straaten on 27 May 21 - No Cached
  • TDD34-8£60,000-6,064 (6.48%)1,470
  • BDD109-29£60,000+3.44%2,823 (3.02%)607
  • User Experience43+8£55,000-5,279 (5.65%)1,045
  • ...9 more annotations...
  • User Stories1730£55,000-1,814 (1.94%)335
  • DescriptionRank6 Months to27 May 2021RankYoY ChangeMedian SalaryMedian SalaryYoY ChangeHistoricalPermanentJob AdsLiveJobs
  • Cucumber279-20£60,000+14.28%1,051 (1.12%)143
  • User Acceptance Testing284-56£47,500-5.00%1,039 (1.11%)193
  • Business Cases311-71£56,878-5.20%932 (1.00%)210
  • Use Case3170£63,500+10.43%917 (0.98%)206
  • User Experience Designer443-30£52,500-4.54%581 (0.62%)101
  • Gherkin598-4£52,500-331 (0.35%)45
  • Epic User Stories616+64£57,542-7.93%304 (0.33%)50
Peter Van der Straaten

Alistair.Cockburn.us | A user story is the title of one scenario whereas a use case is ... - 0 views

alistair.cockburn.us/contents+of+multiple+scenarios

agile use case user story uml cockburn debate

shared by Peter Van der Straaten on 25 May 12 - Cached
  • As a … I want… so that…” is a new-fangled user story format. The original XP user story format had no rules, so you could simply highlight any phrase in a use case and call it a user story. Personally, I feel sorry for anyone who has to write “As a… I want… so that…” for 200 user stories. Kind of like being kept after school and having to write “I will not write silly user stories in class” 100 times
  • A use case pretty much by definition contains multiple stories. A use case is a collection of scenarios related to the primary actor’s goal – some scenarios show the actor interacting with the system and the system interacting with other systems so that they succeed with the goal, some show failure. That’s all in the nature of a use case. see Structuring use cases with goals (discussion: Re: Structuring use cases with goals) from 1995. A use case written for this will occupy between half a page for a shortish one to 2 pages for a long one. A user story is a nickname for a single scenario – it contains neither the information content of the scenario nor failure or alternate paths. A user story typically occupies 1/2 to one sentence no matter its size.
  • (p.s. Agile was supposed to reduce bureaucracy and overhead, not add to it. :) Alistair
Peter Van der Straaten

Alistair.Cockburn.us | Why I still use use cases - 1 views

alistair.cockburn.us/Why+I+still+use+use+cases

agile use case user story uml cockburn debate

shared by Peter Van der Straaten on 25 May 12 - Cached
  • XP pretty much banned use cases, replacing them with the similar sounding “user stories”
  • Scrum did similar, using the “product backlog” instead of user stories
  • Yet as I go around projects, I keep running across organizations suffering from three particular, real, painful, and expensive problems
  • ...15 more annotations...
  • User stories and backlog items don’t give the designers a context to work from
  • don’t give the project team any sense of “completeness
  • don’t provide a good-enough mechanism for looking ahead at the difficulty of upcoming work
  • Staring at the set of extension conditions in a use case lets the analysts suss out which ones will be easy and which will be difficult, and to stage their research accordingly
  • Here 5 reasons why I still write use cases
  • The list of goal names provides executives with the shortest summary of what the system will contribute to the business and the users
  • The main success scenario of each use case provides everyone involved with an agreement as to what the system will basically do, also, sometimes more importantly, what it will not do.
  • The extension conditions of each use case provide the requirements analysts a framework for investigating all the little, niggling things that somehow take up 80% of the development time and budget
  • The use case extension scenario fragments provide answers to the many detailed, often tricky business questions
  • The full use case set shows that the investigators have throught through every user’s needs, every goal they have with respect to the system, and every business variant involved
  • how much should be written up front to get the project estimate into a safe place
  • several sticky parts for people using use cases
  • iteration/sprint lengths are so short that it is not practical to implement an entire use case in just one of them.
  • Writing good use cases (or any other requirements) requires thinking, communicating, and thinking again. It is much easier just to write user-story tags on index cards and let the project blow up later
  • We have adopted many of the concepts of Agile development—such as daily build and test, build the smallest piece of functionality that delivers value, etc.—but have retained our up-front work. It’s worked extremely well
Peter Van der Straaten

Story Maps - AgileBok.org - 0 views

www.agilebok.org/index.php

agile Story maps product backlog user story requirements engineering business analysis

shared by Peter Van der Straaten on 27 Nov 12 - No Cached
  • indicating the priority of stories, as well as their relation to each other and the larger goals of the users
Peter Van der Straaten

User story - Wikipedia, the free encyclopedia - 0 views

en.wikipedia.org/User_story

use case debate user story

shared by Peter Van der Straaten on 05 Feb 15 - Cached
  • Comparing with use cases
  • Kent Beck, Alistair Cockburn, Martin Fowler and others discussed this topic further on the c2.com wiki (the home of extreme programming).[16]
  • "User Story And Use Case Comparison". c2.com.
Peter Van der Straaten

Use-Case 2.0: the Power of Use Cases with the Lightness of User Stories by Piermarco Bu... - 0 views

prezi.com/...-the-lightness-of-user-stories

Use case cockburn presentation Use case 2.0 jacobson prezi agile ++++ debate

shared by Peter Van der Straaten on 26 Sep 13 - No Cached
  • Peter Van der Straaten on 26 Sep 13
     
    Note: Nice presentation, but should check for content (it states that use cases are test cases, and that would at least need some additional instructions).
Peter Van der Straaten

DREAM event - 1 views

www.dreamevent.nl

dream event requirements engineering business analysis informatieanalyse ++++ Atos requirements community

shared by Peter Van der Straaten on 01 Mar 10 - Cached
  • Welkom bij het DREAM Event Atos Origin organiseert op dinsdag 9 maart 2010 voor de tweede keer het Dutch Requirements Engineering and Management event. Het event is open voor de gehele Requirements community; voor iedereen die werkt met specificaties.
  • Hartelijk welkom op de website van DREAM (Dutch Requirements Engineering And Management). In 2014 is al voor de 5de maal het DREAM event succesvol georganiseerd (zie hier een terugblik op de afgelopen events). We willen ook de komende jaren een bijdrage blijven leveren aan het verder verspreiden van de kennis en het begrip betreffende alles wat te maken heeft met requirements; van business rules tot en met user stories, van functioneel ontwerp tot en met modellen van bedrijfsprocessen.
1 - 14 of 14
Showing 20▼ items per page