Some projects, both great and not so great, are launched based upon little more than a vague desire about reaching an idealized future state. The fact may be that leadership (or even just a single leader for that matter) has a vision of a future state and a whole bunch of assumptions. This project might be that vision, a component of that vision or just a stepping stone towards clarifying the vision. The thing is that leadership is moving forward because they have assumptions.
What the business analyst may need to focus upon (BEFORE ANY THING ELSE) is identifying those assumptions, understanding them, validating them, analyzing the results and then compiling them into a course of action. Not a course of action for the organization or even the project, the course of action for the downstream business analysis activities.
As an experiment, I decided to GOOGLE the word assumption and see what was returned. Wow, I was taken back by what appeared to be subtle results but applied to the narrative I've already shared with you thus far.
1. a thing that is accepted as true or as certain to happen, without proof.
2. the action of taking or beginning to take power or responsibility.
3. the reception of the Virgin Mary bodily into heaven.
or translated for my (potentially lame) effort to make a point
1. An idea supported by things (not yet proven to be true)
2. Turned into related actions (via the power to do so)
3. To reach an idealized future environment
© 2017 Dwayne Wright