Bad software requirements can jeopardize projects. There is a considerable literature on software requirements, but practice is far behind: what passes for requirements in industry usually consists of a few use cases or user stories, which are useful but not sufficient for a solution. Can we fix requirements engineering (known in other circles as business analysis) so that it is no longer the weak link in software engineering?
This video presents ongoing work intended to help industry produce more useful requirements. It includes precise definitions of software requirements concepts and a standard plan for requirements specifications, intended to replace the venerable but woefully obsolete IEEE standard from 1998. The plan contains four books covering the four “PEGS” of requirements engineering. The approach builds on existing knowledge to define a practical basis for software requirements engineering and provide projects with precise and helpful guidelines.
To make UX research and requirements gathering more efficient and effective, you have to get everyone in the software development team and the user representatives involved. When the teams understand user concerns and usability issues, they become better at preventing problems.
This talk shares product management best practices and experiences with you in hopes they will help you in your product development journey to build highly effective teams. It covers key topics including (a) working together, (b) managing and prioritizing the work, (c) customer discovery and readying stories, (d) measuring what and how we work, and […]
Visualizations are a key tool that help organizations change their perspective. Though no silver bullet, mapping experiences diagrams seek to align customers’ experiences with how businesses operate. You are surely familiarly with things like customer journey maps, service blueprint, experience maps, and more.