Lonsdale Systems
Menu
Requirements-Discovery-Canvas
Courses
Resources
Blog
Portfolio
About
Contact
Search
Feed
All 10 posts
Blog
Blog
Agile-Business-Analysis
Agile-Business-Analysis
Courses
Courses
Requirements-Discovery-Canvas
Requirements-Discovery-Canvas
Essentials-of-Business-Analysis
Essentials-of-Business-Analysis
Software-Testing-Courses
Software-Testing-Courses
Business-Analysis-Courses
Business-Analysis-Courses
UML-Modelling
UML-Modelling
Software-Testing
Software-Testing
Agile-Courses
Agile-Courses
Requirements-Analysis
Requirements-Analysis
Business-Analysis
Business-Analysis
Extreme-Architecture-Framework
Extreme-Architecture-Framework
Lotus-Agenda
Lotus-Agenda
Elicitation
Elicitation
Essentials-of-Business-Analysis Software-Quality
Essentials-of-Business-Analysis Software-Quality
Risk-Based-Testing
Risk-Based-Testing
Test-Automation-Reference-Model
Test-Automation-Reference-Model
Information-Gathering-Techniques
Information-Gathering-Techniques
Change-Driven-Training
Change-Driven-Training
Software-Testing-Canvas
Software-Testing-Canvas
All categories →
Courses
Resources
Blog
Portfolio
About
Contact
Search
Feed
← PREVIOUS
NEXT PAGE →
What Happens to Sprint Backlog Items at the End of a Sprint?
What happens to a Sprint Backlog Item at the end of a sprint? Does it have no further use? Should the team just tear up the story card and throw it away?
The Requirements Discovery Canvas in Action
My workshop participants love the way they can review what we have covered in real time using Trello.
Rebooting the Use Case Diagram
Use cases have fallen out of favour in recent times with user stories becoming the preferred way for teams to manage requirements. In the rush away from use cases, everyone seems to have forgotten Use Case Diagrams.
How Can Agile Teams Capture Non-Functional Requirements?
Most agile teams are familiar with a Product Backlog. In this post, I propose teams should maintain "Constraint Backlog" of non-functional requirements alongside their Product Backlog.
Test Driving the Requirements Discovery Canvas
Its been over a year since I first published my "Requirements Discovery Canvas". Since then, I have learnt a lot from applying the canvas and sharing it with various groups in Australia and Asia.
The Requirements Discovery Canvas in a Nutshell
My original post describing the Requirements Discovery Canvas is quite lengthy and requires a fair investment of time to read. This post is for those wanting to get a quick overview of the canvas and how it is used.
Product Backlog or Wishlist?
In this post, I am going to focus on the "Features" column of the canvas which prompts a team to answer the question, "How could the stakeholders use software as a tool?". The other columns of the canvas provide the context for answering this question with the canvas as a whole providing a visual framework for organising what the team discovers.
BABOK Version 3 and the Requirements Discovery Canvas
Business Model Canvas and Collaborative Games are among the new business analysis techniques introduced in BABOK Version 3. This makes the Requirements Discovery Canvas an ideal companion for the latest version of BABOK.
Strategies For Requirements Discovery
The Requirements Discovery Canvas guides teams through the discovery process in two ways. First, it prompts the team to consider some fundamental requirements questions. Secondly, it serves as a visual framework for organising what the team discovers.
The Requirements Discovery Canvas
The Requirements Discovery Canvas is a visual tool that helps teams discover and organise software requirements.
Courses
Resources
Blog
Portfolio
About
Contact
Search
Feed
Lonsdale Systems