Content tagged with: agile
Why is it so hard to reconcile Agile approaches and long-term product planning? What causes the friction between product teams and stakeholders that prevents delivering desired outcomes as fast as possible? This presentation shares some research on the issue and gives a sneak-peak into ongoing experiments to solve this painful requirements problem.
This video provides an example of agile requirements traceability. We discuss an example user story and show how detailed requirements captured as test tables can be used to build executable specifications and aid the design process. Finally we wrap up by a brief example of how we would track the progress of multiple user stories across our scrum or kanban wall.
A lot has been said and written about user stories and their role in an agile context. But what are people actually writing as user stories? It doesn’t matter if you are agile or traditional in your approach, poorly written requirements are one of the major causes of project failure. This is where the Business Analyst comes to the fore.
User Stories, designed to keep teams laser-focused on customer needs, serve as THE driving force behind delivering valuable, high quality features, fast. This presentation discusses how to write great agile software user stories by defining customer value and keeping teams laser-focused on needs.
Current user stories used to manage Agile requirements can be improved by clearly identifying, linking, and tracking Actors, Action, Results, and Tests. (A.A.R.T).
Product design and development remains difficult, even when applying Lean or Agile principles. Why is developing a great product so hard? How come it takes so many iterations? Why don’t users know what they want? Why don’t I know what they want?
Creating requirements for your web or mobile application can be tedious and managing ideas even more. The larger the project, the more difficult it becomes. Add in the flexibility that Agile brings to projects, and things could quickly get out of hand.
User stories are a technique taken from the agile development playbook that can easily be applied in traditional systems development and maintenance. User stories help you document needs in a structured way, from the users’ perspective. They’re a good basis for test cases, so as to support integrated requirements management and testing. In this article, you’ll find concrete advice based on our own experiences developing the requirements and testing tool ReQtest for how you can make user stories the basis for requirements management and testing.
How do agile requirements work? Where does documentation fit in? For many of us, the transition from the security of upfront analysis and detailed specification documents to ‘doing Agile’ and embracing the process of discovery is a terrifying prospect. Agile theories don’t readily address the concern ‘how will we know where we’re going if we don’t start with a Business Requirement Specification?’
By now, we are all comfortable with the orthodoxy: the product owner discerns the needs of the customer and feeds them to developers in the form a prioritized backlog. Developers pull work from that backlog, always confident that they’re working on the highest-priority feature at the moment, and never having to worry about how those priorities are allocated. This system is simple, efficient, and has helped many teams function better than they used to. It’s also time for the system to die.