Content in the Videos category
This session talks about how to understand your customers – how they’re behaving, how capable they are of learning and changing, how they make decisions, what they care enough about to pay money or attention to fix. It’s not easy.
Sharing low fidelity user-interface prototypes with project stakeholders is a great way to transfer knowledge and get buy-in early from them. A low-fidelity prototype is a prototype that is sketchy and incomplete, that has some characteristics of the target product but is otherwise simple, usually in order to quickly produce the prototype and test broad concepts.
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.
This video discusses the perfectly-formed requirement, which should be unambiguous and testable. It presents the Snow Card, focusing on the requirement, rationale, fit criterion, and supporting materials.
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.
Working with stakeholders (customer, business and technology perspectives) to effectively and efficiently deliver high-value products begins and ends with value. “Value” is the beacon, watchword, end game, justification and mantra for Agile. It is the basis of the big “why”.
This presentation discusses “designing and documenting user interactions.” It emphasizes the importance of writing good documentation, the value of style guides, while never losing site of the end goal of creating good user experiences.
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).
You are part of a modern development team delivering new features like clockwork. But are you sure you’re delivering the right features? Are you relying on up-front product research practices that don’t fit with your development process?