Showing all posts tagged #agile-business-analysis:


The Six Essential Questions That Define a Requirements Approach

Posted on October 28th, 2018

Also published on LinkedIn October 24th, 2018 Karl Wiegers' post Agile Requirements: What's the Big Deal? has triggered an interesting debate in the comments section. Since I have just finished presenting an Agile Business Analysis course, it seemed a good time to wade into the debate. Sadly Link...

Agile BA in KL

Posted on October 23rd, 2018

Just completed my 'Agile Business Analysis' course in Kuala Lumpur with a great group of participants who asked some challenging questions. In response to some of their questions, I drew this diagram on the whiteboard in an attempt to summarise the major themes of the course. As the title sug...

Will Anyone Read an Article About Documentation?

Posted on October 6th, 2018

I am pleased with the response to the articles I have published on LinkedIn, but a total lack of interest in one article surprised me. The rhetorical question How can agile teams produce comprehensive documentation? seemed like a great title to me because it was echoing one of the values in the ...

Rebooting the Use Case Diagram

Posted on September 28th, 2018

Use cases have fallen out of favour in recent times with user stories becoming the preferred way for teams to manage requirements. For a good discussion of the differences, see Gustav Bergman's older (but still relevant post) A Use Case is to a User Story as a Gazelle is to a Gazebo. In the rush ...

Agile Non-Functional Requirements

Posted on September 12th, 2018

I've just updated my post How Can Agile Teams Capture Non-Functional Requirements? to add a few clarifying diagrams from one of my courses. The post is now better aligned with the new post How Can Agile Teams Deliver Comprehensive Documentation? Read together, the two posts present a workable...

How Can Agile Teams Deliver Comprehensive Documentation?

Posted on September 11th, 2018

I remember one of my students getting quite angry as I explained how Scrum worked. He was a Business Analyst from a bank and he insisted that his management would never accept the total lack of documentation he thought I was proposing. His anger was quite reasonable as Elisabeth Kubler-Ross' chan...

What Happens to Sprint Backlog Items at the End of a Sprint?

Posted on September 11th, 2018

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 Manifesto for Agile Software Development recommends that agile teams should: value working software over comprehensive documentation [1]...

How Can Agile Teams Capture Non-Functional Requirements?

Posted on February 1st, 2018

According to Ian Alexander and Richard Stevens in their book "Writing Better Requirements" [1], user requirements consist of capabilities (functional requirements) and constraints (non-functional requirements). Some constraints relate to individual capabilities and some relate to groups of capab...

Test Driving the Requirements Discovery Canvas

Posted on June 8th, 2016

The Requirements Discovery Canvas is a visual tool that helps teams discover and organise software requirements. Inspired by the Business Model Canvas, it provides a framework for collaboration, that can be used by both agile and traditional software development teams. Its been over a year since...

The Requirements Discovery Canvas in a Nutshell

Posted on March 25th, 2015

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. The Requirements Discovery Canvas is a visual tool that helps teams discover and...