Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Requirements Gathering Help!
Previous Previous
 
Next Next
New Post 8/17/2008 8:47 PM
Unresolved
User is offline Andrew Analyst
1 posts
No Ranking


Requirements Gathering Help! 

Hi,

      I’m new to this board, and I need help!

I’m starting a new contract job and I have little info. about it.

The manager told me that the project I will be working on current time estimate’s and budget are way over what they had hoped for. My job will be to revise the estimates by talking to the technical people, who will be producing the software. The problem is they know far more about the technologies, and the project, than I do; so I’m not sure how I could contradict any of their estimates. In the past, I’ve pretty much relied on what the developers told me when setting estimates.

Any suggestions?

 

Thanks in advance!

 

Andrew

 
New Post 8/18/2008 12:15 AM
User is offline Guy Beauchamp
257 posts
www.smart-ba.com
5th Level Poster




Re: Requirements Gathering Help! 

Hi Andrew,

First off welcome to the forum!

With regards to the issue you have raised - the first observation is this: who is best placed to revise time and cost estimates for a project: someone new to the organisation who as a BA shouldn't be doing that anyway, or the established manager of that project? You have to wonder just why the decision has been taken to get you an outsider to do this...assuming the decision HAS been taken (has it been taken? Will you be presenting your estimates back to the steering group or will the manager?). Of course, as an outsider, if you do the estimates and they don't like them it is easier to shoot the messenger...

But you are where you are so what to do? If in doubt I would suggest you fall back on logic and honesty.

Follow the logic of determining what you need to do in order to be able to do the estimates sensibly (if you are acting as a BA and if you accept that as part of your BA role which it isn't normally). That means if you need to consult with the technicians and take their estimates then document that and communicate it. Please bear in mind that the technical aspects of the project are not the only factors to estimated: there is the whole business side of the implementation as well to plan in.

Be honest about what you can and can't do in terms of what skills you have, your role and resources. Analyse any issues from any shortfalls in any of that and also analyse any risks that arise - there are a load of templates for doing risk and issue anlaysis (can send you some if needed) but the key thing here is not the templates but the content: make the issues and risks relevant to the project. Example: a 'good' project risk is not something like "we may not have sufficient appropriate business resources to accurately estimate project implementation tasks" - in this case the risk is "the project may fail to meet cost and effort deadlines". Make it meaningful to the project and that means that just about all risks will be threats to any combinations of project cost, timescales, quality or scope.

Risk and issue analysis will be key in communicating to your audiences the adverse factors you face in approaching this assignment. From the information you have given it suggests that the project is not being managed effectively and there will only be so much you can do in an established off-target project, so help the project at least understand what state it is in by doing some rigourous risk and issue analysis with the added benefit that this should protect your position as well!

I hope this helps, let me know if you want the templates and likewise let me know if you wud like any help constructing a task list to revise the estimates and documenting the risks and issues.

Guy

 
New Post 8/18/2008 5:39 AM
User is offline Tony Markos
493 posts
5th Level Poster


Re: Requirements Gathering Help! 

Hi:

Your management asking you (a newbie) to estimate is an excellent indicator that any existing estimates are very questionable.  What models have the developers created upon which to base their estimates?   Have they created a model of system scope?      If there are any models, are the readable to an outsider (yourself)?  Readablity by a newbie BA an excellent indicator of value of existing models. 

The tech people know you are a newbie.  Can they talk to you on newbie terms?  If not chances are they lack the skill of being able to postone tech detail, and abstract out core essential functionality - the backbone of what needs to be done to estimate. 

Think about what deliverable you need to create to base your estimate.  First: a scope model.   One needs to know the extent of a system in order to start modeling.   The standard  system scoping tool is a special kind of data flow diagram called a Context diagram.   Problem:   It is very top down, and since, typically, nobody has a top down understanding of what needs to be done, you need to proceed kind of from the middle upwards.   Therefore, the need for creating lower level data flow diagrams, which you then summarize upwards into a Context diagram.

Tony

 

 

 
New Post 8/19/2008 5:13 AM
User is offline Craig Brown
560 posts
www.betterprojects.net
4th Level Poster




Re: Requirements Gathering Help! 

Andrew

I think you misunderstand the request.  You must have...

You see projects often go over budget and out of control when bad requirements are defined up front.

Having someone come along later and estimate the work to adres bad requirements ends up in the same place you are today, so what you have to do is go and rework the requirements gathring and defining activity.

One thing you should take a look at is incremental delivery of the solution - how can you stage a series of releases so your customer gets something early and can layer on the extra features later.

Another thing to look at is the product's quality requirements - the higher they are the higher the cost.  Is 27*365 availability really needed.

Last point for this post - go speak with the sponsor and the SENIOR stakeholders and find out what they wanted - and then read through the old requirements spec and see all the bloat that has been added.

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Requirements Gathering Help!

Community Blog - Latest Posts

Fabricio Laguna talks Business Analysis and AI
I recently connected with Fabricio Laguna, aka The Brazilian BA. Fabricio is a passionate and pioneering business analyst from Brazil. During our conversation, we had a thought-provoking discussion on how artificial intelligence stands to shape the field of business analysis in the years ahead. While AI promises to transform many aspects of busines...
Business Architecture, Ontology and More with Terry Roach
It's been a privilege meeting Terry Roach, a visionary in the field of enterprise architecture and business architecture. Terry's insights into the evolution of business models, the importance of ontology in architecture, and the potential of AI to shape our future were not only thought-provoking but also a reflection of his extensive exper...
Today I had the pleasure of chatting to Jignesh Jamnadas, Chief Operations Officer at Mosaic, about his Blueprints for Success. As a Senior Finance and Operations Executive, Jigs (as he is known to many) has a holistic understanding of all facets of business and a flair for managing both people and processes. Having worked with Jigs, I was struc...

 



Upcoming Live Webinars




 

Copyright 2006-2024 by Modern Analyst Media LLC