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?
Will Anyone Read an Article About Documentation?
On reflection, I probably shouldn't be too surprised at the lack of interest. Including the word documentation in the title of an article almost guarantees that no will read it! Or maybe it's because my reference to comprehensive documentation is too subtle?
Scrum and Agile Practices
Had great feedback for my Scrum and Agile Practices course, delivered for an organisation in Bangkok planning to adopt agile. The course takes participants on a no nonsense tour of agile, designed for late adopters.
The Three ’E’s of Agile Business Analysis
The three 'E's of Agile Business Analysis are Elicit, Elaborate and Emerge.
The 6+1 Essential Questions that define a Requirements Approach
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.
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.
Describing Software Features
In this post, I am going to focus once again 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.
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.
The Feature Funnel: More On Ambiguity
I ended my post on qualifying the wishlist by promoting the benefits of a glossary of terms. This post will continue to explore the problems of ambiguity associated with natural language.
The Feature Funnel: The Big Picture
A full visualisation of the Feature Funnel.
The Feature Funnel: Qualifying the Wishlist
In this post I will introduce a series of questions that can be used to refine and filter the wishlist.
The Feature Funnel: A Tool for Managing User Wishlists
The feature funnel represents the systematic process by which an unqualified wishlist of software requirements are gradually refined into a consistent set of product features.