Showing all posts tagged #linkedin-article:


Planning Online Meetings

Posted on March 27th, 2020

We all know that to be productive, meetings should be planned. The ease of organising and launching an online meeting can make a little planning even more important. I have been using and teaching a planning model based on The Layered Systems Model for many years now. The model has six plannin...

Change Driven Training

Posted on March 6th, 2020

When staff need to improve their skills, organisations usually think in terms of training. Often, the new skills they need are described as training needs which are then used to identify suitable training courses. Once the 'right' course has been found, students are 'processed' through the cours...

More About Describing Software Features

Posted on January 29th, 2020

When a mechanical engineer specifies a length of 12 centimetres, it is perfectly clear what is required. When an electrical engineer specifies a current of 2 amps, once again is perfectly clear what is needed. But when a software engineer or business analyst specifies a feature, the underlying ne...

The 6+1 Essential Questions that define a Requirements Approach

Posted on October 28th, 2018

Also published in a revised form on LinkedIn October 24th, 2018 These days much our thinking seems to have been reduced to simple binary choices. In reality, most problems worth our attention are multi-dimensional by nature. The agile vs. traditional requirements debate is no exception. For me, ...

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 ...

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...