• Seilevel Team

    Here’s the Team

    Welcome to our Seilevel Photo Op.

requirements management

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 work of 3 or 4 full time developers working on a project. For Waterfall projects, this ratio is higher and …

Read More

“A Poor Craftsman blames the (requirements) tool”

The decision to use a requirements tool is dependent on a number of factors: size of project, number of system interlocks, global teams, specific business objectives tied to real dollar figures, just to name a few.  In this post I will describe the key benefits of using a requirements management …

Read More

Setting boundaries in Agile Requirements Management

I was once part of a team at a consumer-facing technology company, who described themselves as incredibly fast-paced, operating within a rapidly changing environment. This team was smaller (4 developers in a 10-person business unit), so I expected the ability to get things done quickly to be one of our strengths. Upon joining, …

Read More

“A Poor Craftsman blames the (requirements) tool”

The decision to use a requirements tool is dependent on a number of factors: size of project, number of system interlocks, global teams, specific business objectives tied to real dollar figures, just to name a few.  In this post I will describe the key benefits of using a requirements management …

Read More

When Features Attack!

As the saying goes, “necessity is the mother of invention”, Seilevel’s 10+ year mission to “redefine the way software requirements are created,” was no accident either. While vague, incomplete or incorrect requirements are issues we face every day, the more vexing, expensive, and ever-expanding problem we face is how to …

Read More

Shovel Ready Requirements

I’ve seen a number of projects that follow a path something like this — gather requirements (there are a bunch of steps in here), do some pruning, flesh out requirements, do some more pruning, mark the requirements importance in some fashion (such as low/medium/high), get the document approved, and say …

Read More

Requirements Deliverables: Target Your Audience

At Seilevel, we consistently tout the invaluable benefit of using models in your requirements process.  In many cases, models are more than enough to communicate the intended functionality to all stakeholders.  This is especially true if you have been using models in your process for some time and stakeholders know …

Read More

Find Missing Requirements with the Feature Tree

I provided some business analysis training a while ago, and recently caught up with one of the attendees of the training; a lovely lady whom, for the purposes of this post, we’ll call Pat. I was inquiring how things were going and whether or not she was able to incorporate …

Read More