Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Managing & Lead...  Lead BA being tossed into an ongoing project that a previous BA screwed up.
Previous Previous
 
Next Next
New Post 1/14/2008 7:29 AM
Resolved
User is offline Requirements Czar
6 posts
10th Level Poster


Lead BA being tossed into an ongoing project that a previous BA screwed up. 

I've been tasked with taking over a project that has run into some troubles and needs saving.  Project is ready to start some testing, but still have various outstanding issues.  I will be meeting with the business owners tomorrow to discuss my new role and where we go from here. 

Does anyone have some thoughts as to where to begin this crusade??  Thanks.....any help would be appreciated.

 
New Post 1/14/2008 11:01 AM
Online now... Adrian M.
739 posts
3rd Level Poster




Re: Lead BA being tossed into an ongoing project that a previous BA screwed up. 

Since the project "needs saving", the first thing that  I would do is begin by trying to figure out what is wrong and what went wrong.  There could be many different types of issues which might require different approaches.

Some of the common problems found in projects that "need saving" are: discrepancy between business need and documented requirements, discrepancy between documented requirements and the implemented solution, large number of defects (bugs) in the system, wrong/inappropriate technology decisions, etc.

Do you have any more info on what went wrong?

- Adrian


Adrian Marchis
Business Analyst Community Blog - Post your thoughts!
 
New Post 1/14/2008 11:24 AM
User is offline Craig Brown
560 posts
www.betterprojects.net
4th Level Poster




Re: Lead BA being tossed into an ongoing project that a previous BA screwed up. 

I would start with an audit of the Requirements Traceability Matrix.  If there isn't one then I would get one organisaed. The next thing I would do is check ff with the stakeholders which requirements are most important and which can be dropped.  Lastly I'd apply my own judgement to what can go and what must stay.

My experience makes me guess the solution has been over engineered, probably, ut not neccessarily, based on poor requirements.

Risk areas include;

  • System integration; are you asking for more than you need in context of the business process
  • Non functional specs; availability and response times drive hardware costs up quite high when you are looking for 99.7%^ uptime.
  • Non strategic requirements; which requirements support the project objective and which ones are there for stakeholder comfort and convenience.

When cutting back requirements and solution design you often have to "sell the benefits" back to stakeholders. 

 
New Post 1/14/2008 12:53 PM
User is offline Requirements Czar
6 posts
10th Level Poster


Re: Lead BA being tossed into an ongoing project that a previous BA screwed up. 

Some of what went wrong include the following:

Missed requirements, deadline approaching, analyst being too 'passive', no project plan/task list, etc.  It appears that there were many factors involved which have led to an unhappy stakeholder.  Thanks for your replies!

 
New Post 1/14/2008 10:06 PM
Accepted Answer 
Online now... Adrian M.
739 posts
3rd Level Poster




Re: Lead BA being tossed into an ongoing project that a previous BA screwed up. 

It's not an easy thing having to come in to a project which is already heading in the wrong direction.  It's very important that you make a reality check upfront - that is, baseline the project where it's at right now and ensure everybody understands the state and trouble the project is in.  A few months from now most people will forget that you are the new business analyst and that you did not create this mess - they will expect you to still deliver as if you've started with a clean slate (things just work that way).

So make sure to:

  • convey to the business and management that "miracles" just don't happen: if the project is late with the deadline approaching it would not be reasonable for them to expect for you to make up the loss time,
  • understand and document where all the problems and risk are with the current requirements, specifications, etc. - and estimate what would it take for these problems to get fixed; as a new guy you'll be eager to make a good impression, so beware of underestimating,
  • identify the root causes of why the project is in bad shape and fix them: if project failed from lack of planning then create a planning process and plan, if the project failed because of missed requirements then institute a requirements gathering and management process, etc.
  • again, let the management know that you're not a hero and that it will require significant resources to fix what's broken before the normal process of adding new features resumes.

- Adrian


Adrian Marchis
Business Analyst Community Blog - Post your thoughts!
 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Managing & Lead...  Lead BA being tossed into an ongoing project that a previous BA screwed up.

Community Blog - Latest Posts

So you’ve found the perfect time and place to study and you’re ready to finally get some work done. You’ve pulled out your laptop, your textbook, and your notes, and four different highlighters. After five minutes of reading your textbook, you start zoning out and thinking about puppies. Then, you go on Tumblr and look at cut...
Elicitation involves bringing out or drawing out information. Elicitation is a key task in business analysis as without proper elicitation the requirements for the solution to the business needs cannot be identified. 1. Not understanding underlying business need Organization’s business environment keeps changing with respect to Customer...
TOGAF is a certification that is handed over by The Open Group. It is an open corporate architecture means used to improvise upon the business effectiveness across the world’s leading business set-ups. Aspirants wishing for a successful career in corporate architecture must go for the TOGAF certification in order to explain the...

 



 

Copyright 2006-2021 by Modern Analyst Media LLC