Developing complex software for enterprises using Agile development methodologies has presented some unique challenges, especially in the area of regression testing. This is particularly true in the Financial Services sector […]
Tag: Requirements engineering
Ratio of Developers to Analysts in Agile
Conventional wisdom generally holds that the ratio of developers to analysts in an Agile framework is about 4:1 or 3:1. In essence, it says that 1 analyst can support the […]
Seeing the Forest through all of the Trees
I recently had a conversation with a fellow business analyst, Susan, regarding process flows. At ArgonDigital, we like to keep process flows focused on what people are attempting to accomplish. […]
The Most Important Part of A User Story
The last couple of years has seen a wholesale shift in development methodologies among the Fortune 1000 companies from Waterfall to Agile. It is not an exaggeration to say that […]
Agile Requirements Document
At ArgonDigital, on our Agile projects we have introduced a project artifact called the Agile Requirements Document or ARD that we create during the planning phase of a project. We […]
Finding Hidden Assumptions
I was recently lucky enough to attend ProductCamp Austin. If you are not familiar with ProductCamp, it is a free, collaborative “unconference” for product managers and other similar roles. I […]
What Models Should be Used to Create Requirements in an Agile Project?
This is a question that came up repeatedly in the classes I have taught these past few months. My answer is always the same: “Any and all models that are […]
Long Distance Agile – How Good Requirements Documentation Overcomes the Problems of Distance and Disconnected Agile Teams
In the last three months or so, I have been approached by a number of analysts and developers struggling with the problems of working on geographically dispersed Agile teams. In […]
An Exercise in Documenting Current State: Reddit and the Decision Tree
An exercise in documenting current state: reddit and the decision tree In an earlier post I detailed how you can use RML models to document the current state of your […]
Arsonists in a Field of Straw Men: Elicitation from a Blank Slate
On a recent project, I was sitting in a room full of subject matter experts (SMEs), trying to document a business process using the trusty Process Flow model, when trouble […]
Welcoming Changing Requirements
The Agile Manifesto is based on twelve principles (I’ve highlighted a couple – 2 and 12 – that are of the most interest for this post): Customer satisfaction by rapid […]
Requirements Elicitation Technique – Tools of the Trade
As a BA, I’m always looking for tools that can help me with my job…anything to make my life just a bit easier! I’m always curious about the latest requirement […]