Product Design, System Design and User Interface Design

It's well known that most software projects fail.  It's also well known that a major cause of failure is "unclear or incomplete requirements" and "lack of user input."  Why is this the case?  Quite simply... requirements gathering is hard:

  • Confused UserOn one side of the fence, you're trying to elicit input from overworked business folks who are often pulled by day-to-day operational and business needs.  They are often good at describing what they want in broad terms but have difficulty fleshing out the details and describing what should happen when things don't work as expected.
  • On the other side, most engineers need specificity in order to be provide their best solutions.  While they can be very creative in designing elegant technical solutions, it may be more challenging for them to "negotiate" options for how the functionality can work to meet business needs in the least development time as possible.

A Business Analyst to Bridge the Collaboration Chasm

Practical Strategies' business analyst resources have the skill set to ensure that your project will NOT be a failure due to unclear or incomplete requirements.  We benefit from a unqiue combination of experience and skills:

  • Significant experience on both the business and technical sides, allowing us to not just communicate with business and technical resources, but rather connect with them.  A connection significantly improves your ability to elicit information and brainstorm creative solutions, leading to results that deliver the most value with the least effort.
  • Attention to detail.  Is the list complete?  Is our list of scenarios collectively exhaustive and mutually exclusive?  For all of our IF suppositions, did we worry about the ELSE part?
  • Helping users figure out what they want.  It's a lot easier to react to something rather than describe it from scratch.  We seek opportunities to have users react to mock-ups, prototypes, rough first versions as early as possible.  In reality, you should expect to hear "well it seemed like a good idea at the time" or "it sounded good on paper" everyone once in a while, so why not adjust your approach to embrace it.
  • Effective documentation.  Use cases?  Scenarios?  Stories?   We can use the approach that works best for your organization and dovetails with your cultural approach.

Contact us today to determine how our resources can help ensure the success of your project.