• Seilevel Team

    Here’s the Team

    Welcome to our Seilevel Photo Op.

Planning, Tracking and Metrics

Executive Buy In and Feedback

Business Analysis and Successful Outcomes

In a previous post, I talked about the need for executive buy-in on business analysis activities and some ideas on how to facilitate it. As I mentioned, they are not our target audience for PMI’s foundational standard on business analysis, so we need to find other ways to win their …

Read More
BDD

Using the BDD: Bounding your Requirements Objects

The Business Data Diagram is a powerful, high-level RML model that can help bound the scope of data for your project. It can also be used to visually convey a sophisticated strategy for bounding your requirements objects and their traceability. I was recently working on a project where we had …

Read More

Knowing How to Use Your (Requirements) Tools

When it comes to any project, the right tool makes all the difference.Whether in woodworking, engineering, or fashion design, having the proper tools makes things easier and more efficient. The same can be said in the world of requirements. The need for requirements tools in the world of IT product development is …

Read More

A Tale of Two Consultings

Before I joined Seilevel and became a Requirements/Software Development Consultant, I worked as an Engineering Consultant for an oil field services company that specialized in heavy lift systems.  Of course there are a lot of similar functions as expected, but I have noticed some differences.  The main difference that I want …

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

Ignore tasks, focus on decisions.

We all have our reasons for using a piece of software. Maybe it makes staying in touch easier, maybe it helps organize, or for that matter, make us money, maybe it’s just fun to interact with…whatever those reasons may be, the drive to get things done is not, and cannot …

Read More

Skipping Sprint 0 – The Consequences of Sprinting Without a Backlog

A common misconception about Agile Product Development is around “just-in-time” planning. It’s important to not have all of your requirements for the next six months fully defined (because even the smallest changes will definitely require rework), but it’s equally as important for a Product Owner to be working 1-2 sprints …

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