Hi
This is probably my first post, so let me introduce myself. I recently joined a Public Sector body in the UK and this is my first BA role. As I am still in the process of learning more about this discipline and learning about the organization's CRM system I have found myself at a slight disadvantage when it has come to involve me on a project which essentially involves the re-write of the said system.
I have been asked to attend a series of workshops where the Business Analysis (i.e; the Requirements Engineering and Modelling) will be carried out by the supplier that have been entrusted in managing the infrastructure along with maintenance and ongoing developments over the last 5 years. This supplier will also be asked to tender a Statement of Requirements which essentially is part of my overall remit.
I have been told that my role is one of an mediator to ensure that the supplier understands the end-user's requirements, which is fine but the fact is that a number of experienced key users will also be at the workshop. I also know that a number of these users have a good working relationship with the supplier (and their consultants), therefore my question is what sort of value if any can I add to this process?
Obviously on a personal level it will be a good way for me to learn more about the CRM. However, this project is not about making sure the BA is comfortable with Oracle CRM, it's about ensuring that the business needs can be met by the development. I just feel from that perspective I will not be able to contribute much to the process. I would appreciate any advice that the more experienced BAs amongst you can provide.
Thanks
Sham
Sham,
You can add a lot of value! It's great that your company is getting key users involved with the vendors consultants. But not all consultant or business analysts are equal. There are several big risks that seems to occur in the majority of projects. These risks are what you should focus on avoiding. I will start with one of them here. Others can jump in for some of the other risks.
One of the biggest risks to a project has to do with how users communicate requirements to analysts, consultants, or developers. The users start giving a bunch of so called requirements. They should be stating the business needs (what), but what they are really communicating is how they think the system will work. If the analyst or consultant is not paying attention, they will document this how as the business requirement. This is NOT the business requirement. Projects that go down the path of developing a system that the user thinks they want, instead of solutioning and designing a system based on basic business needs end up developing a working system that the user is unsatisfied with at best. The developers say, "but that's what you asked for". The users say, "No, what I meant was this other thing. This system isn't doing this or that which I need". At this point the business requirements start to come out. And now the cost to implement that feature will be as much as 100 times more than if it was done right the first time.
To avoid this, everytime the user mentions what they think they need ask youself "WHY". If their initial statement doesn't answer "WHY", then they didn't give you the business requirement.
If you ask them "WHY"and they give you a different answer, you now need to ask "WHY" again. You still may not have the business requirements. The rule of thumb is ask "WHY" 3-5 times for each perceived requirement. By then you have probably undercovered the true need.
In addition to what the previous posters came up with, your position as a newby gives you the advantage to look at things with a independent, fresh look. For you it will be easier to 'think outside the box' whereas the experienced users with good relationships with the supplier may have lost their objectivity along the way. This is exactly why your role in this will be of great value. Apart from that, since most of the people will know you are new to this, no-one will be bothered if you keep on asking questions so you will develop your knowledge in no-time :-)
Good luck on your project.
Frank
brought to you by enabling practitioners & organizations to achieve their goals using: