background preloader

What’s in a Story? « DanNorth.net

What’s in a Story? « DanNorth.net
[This article has been translated into Korean by HongJoo Lee, French by Philippe Poumaroux, Spanish by Adrian Moya, Russian by Denis Oleynik, and German by Julia Kadauke.] Behaviour-driven development is an “outside-in” methodology. It starts at the outside by identifying business outcomes, and then drills down into the feature set that will achieve those outcomes. Each feature is captured as a “story”, which defines the scope of the feature along with its acceptance criteria. This article introduces the BDD approach to defining and identifying stories and their acceptance criteria. Introduction Software delivery is about writing software to achieve business outcomes. Usually, the business outcomes are too coarse-grained to be used to directly write software (where do you start coding when the outcome is “save 5% of my operating costs”?) This, then, is the role of a Story. The structure of a story BDD provides a structure for a story. Telling the story The characteristics of a good story 1.

https://dannorth.net/whats-in-a-story/

Related:  RequirementsTest Driven DevelopmentOther ResourcesEstimating

Use Cases, User Stories and Scenarios - what are they - and how do they relate to TFS 2010 All these three terms are used to describe the behavior of an application. They come from different process methodologies, and have different meanings, characteristics and are intended to be used differently. Larry Guger also discuss these aspects and several others in his blog entries and The Use Case is the term used in UML and in the different Unified Process based methodologies. See for a good overall description. 10 Reasons Why BDD Changes Everything - Larry Apke Recently I have been working with my two scrum teams to implement a BDD approach to our development. I’d have to say that the early results are astounding! While I have always known and believed in BDD in theory, I continue to be amazed by its simple power in practice.

17 Theses on Software Estimation-10x Software Development (with apologies to Martin Luther for the title) Arriving late to the #NoEstimates discussion, I’m amazed at some of the assumptions that have gone unchallenged, and I’m also amazed at the absence of some fundamental points that no one seems to have made so far. The point of this article is to state unambiguously what I see as the arguments in favor of estimation in software and put #NoEstimates in context. 1. Estimation is often done badly and ineffectively and in an overly time-consuming way.

Create Scenarios Project Management (4) A project plan takes into account the approach the team will take and helps the team and stakeholders document decisions made regarding the objective, scope, schedule, resources, and... Creating an interdisciplinary team with the right mix of skills is vital to the smooth and successful execution of any project. Team members may be able to cover multiple roles or there may... Use your kick-off meeting to discuss the business case related to the site, the vision and mission based on user and organizational goals, and the vision for the site moving forward. Watching People Code Could Be The Next Big Thing Twitch made streaming video games into a hugely popular phenomenon, so what could be next big livestreaming thing? Perhaps it’s watching other people code. You might also like: Boston Dynamics Shows Off Amazing New Robot Dog

How To Implement Scrum in 10 Easy Steps When I first encountered agile development, I found it hard to understand. Okay, I might not be the brightest person you’ve ever met! But I’m not stupid either, I think :-) There’s a myriad of different approaches, principles, methods and terms, all of which are characterised as ‘Agile’. And from my perspective, all this ‘noise’ makes agile software development sound far harder, far more scientific, and far more confusing than it really needs to be. For this reason, I favour the Scrum agile methodology.

User Stories:Lack of Big Picture Leads to Blind Man Product One of the Scrum values is “Focus”. It can make or mar a product. It brings direction to the development of a product – from start to finish; and is the back-bone of an effective business strategy. Having said that, overdo it and the tables are turned. Fret too much over ‘focus’ and what could have been a blessing may become your curse. Here’s why:

How to become an expert in Linux Command Line Linux is a Unix-like and most powerful operating system in the world. It was assembled under the FOSS (Free and Open Source Software) development and distribution. First Linux kernel was released on 5 Oct 1991 by Linus Torvalds. In 2014 Linux Torvalds continuously updates the kernel, so the Linux operating system goes more powerful day by day. So learning Linux command lines are much better than learning some programming languages. Negotiating Estimates In my previous post dealing with Ron Jeffries (since revised) “Summing up the discussion”, I focused strictly on the customer-focused aspects. I did, however, note some language regarding negotiating estimates that I wanted to touch on: “Negotiating” estimates is deeply embedded into most cultures. It probably started in the marketplace in the village in ancient Greece, where the carrot guy tried to get three hemitetartemorions for his carrots, and your great-to-the-nth grandmother talked him down to one. We assume that a contractor’s estimate has fat in it and we assume that we need tough negotiation to squeeze it out. The better the contractor is at estimating, the more this process hurts him, because he has nothing left to squeeze.

Related: