• Seilevel Team

    Here’s the Team

    Welcome to our Seilevel Photo Op.

software requirements gathering

Foundational Business Analysis Training

“There are no shortcuts to any place worth going.” – Beverly Sills It should come as no surprise that if you change your requirements after you deploy, it costs A LOT more. Here’s a fun (read scary) fact: 65% of features stakeholders define for a product are rarely, if ever, …

Read More

First, break all the requirements

What? In 1999, Buckingham and Coffman authored First, Break All the Rules. They used Gallop data from manager interviews to identify how good managers drive employee satisfaction. Internally at Seilevel, we use the methodology described in the book for gauging employee satisfaction. People who join us are sometimes surprised by our …

Read More

Perfectionism—Use it Like a Tool

On  an  episode of Well Read, Elizabeth Gilbert makes the interesting case that perfectionism is really fear (starting at 6 minutes, 58 seconds).  She also addresses this in her blog post about avoiding the perfectionism trap, where she states “…I think perfectionism is just a high-end, haute couture version of …

Read More

Telling a Story Through Your Requirements, Part II

In my previous post, I talked about how business analysts and product managers who are putting together requirements documentation can and should think of themselves as storytellers. By thinking of a Business Requirements Document (BRD) or a System Requirements Specification (SRS) as a narrative, with a beginning, middle and end, …

Read More

Gesture Mapping for Mobile Interfaces

Look around you. Many of the tasks we once relied on a desktop or laptop to perform are now done on our phones and tablets. While that’s great news for our airplane carry-ons, it isn’t necessarily the best news in terms of usability. Anyone who has attempted to view or …

Read More

Shakespeare Would Suck at Gathering Requirements

In William Shakespeare’s famous play, Romeo and Juliet, Juliet tells her sweet Romeo: “What’s in a name? that which we call a rose By any other name would smell as sweet” Short answer in the requirements world: No. If you have ever been tasked with writing software requirements, you may be …

Read More