BA tips and tricks

Perils and Pitfalls of Conference Calls

One of the challenges of gathering requirements in a world of packed schedules and remote stakeholders is the ubiquitous conference call. What I find most challenging is the inability to read facial cues or body language. When discussing stakeholder needs over the phone, what they say may not be entirely …

Unspoken Assumptions

By Adam Guerra

Fundamentally, assumptions are facts that we tentatively decide to accept as true so we can continue to make progress, even though we know those assumptions might end up being wrong. Assume standard temperature and pressure, or assume a frictionless plane, or assume a spherical cow. Rather than measuring exact temperatures …

Going Agile: The Anatomy of a User Story

By Megan Jackson

User stories, a requirements format utilized in Agile software development, are typically formatted with the following template: As a (type of user), I want (some goal), so that (some reason). This template can be modified to suit a project’s need. In this post, we’ll show how user stories themselves can …

Requirements Tools: Excel (1 of Many)

By Adam Guerra

Last time, I went over a Sharepoint feature that’s saved me a lot of time and effort. At Seilevel,, as much as we use Sharepoint, we use Excel even more. Not as much for calculations, but for storing and sorting requirements and associated data, such as features. When we do …

Navigation

Here’s the Team

BA tips and tricks