Digital Mosaic Home Page The right mix of specialists.
Home About Us Clients Research Partners Join Our Team Contact Us
Aligning IT to business, sizing projects, business case building
-Determine Business Scope
-Optimize SME Participation

Accelerating the quality and speed of needs assessments, requirements elicitation and requirements documentation
-Scope & Feasibility Assessment
-Business Requirements Definition
-Audit requirements/Triage projects

Tools, templates and specialist practices for selecting and managing vendors
-Getting Solutions that Fit
-Issue and Evaluate RFPs

Business case building, research, market planning
-Get a Mosaic Analyst
-Research & Business Case Assist

Pragmatic training for improving business analyst productivity
-Course 1: Business Requirements
-Course 2: Lead & Facilitate
-All Our Courses



Take the next step . . .

ON AN ONGOING BASIS, would your IT organization be able to develop systems faster if the business requirements were better documented?

How do you know you have a requirements gap on a project?

Probably not until the project is late, over-budget, and the scope is creeping out of sight. No amount of project management can fix a project where requirements are poorly defined. A failing project will eventually die under the weight of user frustration and antipathy. However:

Sometimes it is not the project, but the corporation that has a requirements gap.

How can you recognize if your company has a requirements gap?
Score your company using this simple test on a scale of 1 to 5:
1 = never a problem on projects
3 = this problem sometimes impacts projects
5 = this always occurs in projects
 

  Your company cannot launch a requirements gathering stage and predict how long the requirements phase will take +/- a few days.
  Your users say they are “too busy” or unavailable to participate in defining requirements.
  Your projects struggle to gain early stage momentum.
  Your business analysts feel that the business stakeholders cannot tell them what they want.
  Business stakeholders see the technology department as the “owners” of requirements.
  Business stakeholders keep describing their needs in terms of what technology to use.
  The company has no formal methodology for eliciting and documenting requirements.
  You cannot “lock” the requirements specification at a particular point in time, having achieved consensus amongst your stakeholders on the specification.
  Your process is: they (the users) tell you what they want … you write it up … you propose solutions… you show them the write-up and the solutions … they claim those are not what they want… and the cycle begins over again.
  You are never entirely sure you have all the requirements

 

If you scored a perfect “10,” you are already heavily invested in a repeatable and predictable way of getting the requirements for new projects. If you feel the company is scoring above 25, there is room for improvement and we can help.

How can Digital Mosaic help you?

Show me the business impact of spending time fixing the way we do requirements.

We need to get our business requirements done professionally on a project.

We have analysts in place, but need training programs that build skills in extracting business requirements proactively and consistently across our businesses.

We think we need to transform our analyst function’s processes, the techniques used, and value delivered to the company.

 


White Paper

The HOW Not the WHAT of Defining Business Requirements



White Paper

THE ROI OF ROI: Converting business promise into business value



"Your team brought the project together and gave us excellent value ... You helped us get objective data to management so that our team could focus on making the key decisions... [We got] traction on an initiative that could possibly drop hundreds of thousands of dollars to our bottom line."
Tech Data Canada

Contact Us

Contact us today.