These are the videos that we recommend for requirements, innovation and systemic thinking.
Introduction to Requirements the Masterclass Traditional, Agile, OutsourcingThis video is the introduction from Requirements: The Masterclass LiveLessons--Traditional, Agile, Outsourcing (Video Training). This 13+ Hours of Video Training - Requirements: The Masterclass LiveLessons--Agile, Traditional, Outsourcing is a video course covering requirements, whether they are the requirements for software, a service, or a product. This video teaches the requirements process from initiation and scoping, through investigating the work being done and then determining the optimal solution to improve that work. After this course, business analysts, agile team members, and others concerned with requirements will be able to discover the correct requirements and communicate them precisely and unambiguously to the product developers.
Mastering Requirements: An Interview with James and Suzanne RobertsonJames and Suzanne Robertson, co-authors of "Requirements: The Masterclass LiveLessons--Traditional, Agile, Outsourcing (Video Training)" and "Mastering the Requirements Process: Getting Requirements Right, 3rd Edition" answer questions about learning to solve the real business problem, the biggest mistake people make in the requirements process, and what makes their approach to requirements discovery unique.
Volere FlowSuzanne and James Robertson, co-authors of "Requirements: The Masterclass LiveLessons--Traditional, Agile, Outsourcing (Video Training)," discuss the Volere Flow, which is how you get from the business problem all the way to the atomic functional and non-functional requirements. The flow shows both agile and traditional ways to the requirements.
The Perfectly Formed RequirementJames Robertson, co-author with Suzanne Robertson of "Requirements: The Masterclass LiveLessons--Traditional, Agile, Outsourcing (Video Training)," discusses the perfectly-formed requirement. Perfectly formed requirements should be unambiguous and testable. James discusses the Snow Card, focusing on the requirement, rationale, fit criterion, and supporting materials.
The Brown Cow modelThe Brown Cow model is a way of reducing the complexity of systems modelling by dividing the model’s viewpoints. For example, the business analyst needs to separate the current view of the system from the future. Additionally, he or she must be able to demonstrate a technological view of the system, along with the technologically-agnostic essential view. Suzanne Robertson explains how this works.
Requirements: the Masterclass — Traditional, Agile, Outsourcing
The 13+ hours of instruction in this video course teaches you how to become a requirements wizard — it covers the gamut of the requirements activities. It begins with how to scope the problem using a context model and then how to use business events and business use cases to subdivide the problem space into manageable and convenient chunks. It looks at how to uncover the real problem--something not done on many projects--and then how to find its optimal solution. Then the video show how to write unambiguous and correct stories or requirements to ensure correct development.
The course is suitable for business analysts, agile team members, and others concerned with discovering, writing and communicating the correct requirements.
“Many recorded training sequences often seem to be either videos of live classes with not always the best editing, or talking heads with periodic slides of bullet points. The Robertson’s “Requirements: the Masterclass LiveLessons is not like that. It is a comprehensive review of requirements discovery and management which uses mostly diagrams and graphic illustrations to address their over 13 hours of material. Sure, there are some talking head and bullet point aspects, but they are quite in the minority compared to the more active elements. I think anyone seriously interested in requirements work, whether in traditional, agile, outsourced or off-the-shelf situations would find this series very instructive and thorough.” — Scott Duncan, editor “Software Quality Professional” journal.