• Seilevel Team

    Here’s the Team

    Welcome to our Seilevel Photo Op.

business requirements document

Why We Should All Stop Creating Requirements Documents

I know what you’re thinking–you’re reading the title of this blog and wondering what’s wrong with me.  Did I have a stroke?  Have I been spending too much time around cowboy developers?  Am I disconnected from what business analysts are actually doing?  Not at all.  Let me assure you that I am …

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

Business Analyst Tip: Typography Resource

Perhaps I shouldn’t admit this, but I learned to type on a typewriter. One of the rules I learned in typing class was to put two spaces after the period ending each sentence. I still do it by habit, even though the standard seems to have changed to one space. …

Read More

New Articles for Business Analysts from Across the Web

Happy New Year! Seilevel blog writers Betsy Stockdale and Balaji Vijayan have new articles published – Betsy on BA Times, Balaji on Modern Analyst – and yours truly, Seilevel’s blog editor, has a post on IT Toolbox. For Betsy’s article on using business objectives to control scope, visit BA Times …

Read More

Requirements Documentation Standards

We use a set of requirements documentation standards to generate consistency in our writing styles. They should be applied to the documentation produced in the requirements phase of a project, including the requirements, use cases, diagrams and process flows. Instead of writing in individual preferred styles, the entire team writes …

Read More