Forums for the Business Analyst

  Modern Analyst Forums  Business and Sy...  Requirements  Should we produce only what PM wants ?
Previous Previous
Next Next
New Post 11/10/2019 3:51 PM
User is offline pramodh555
8 posts
10th Level Poster

Should we produce only what PM wants ? 

Hi All,

I recently joined a company as a BA. One of their business units requires a Ticketing solution to manage their incidents / requests. Already there is a high level requirements document related to it. 

My PM wanted to me to provide an excel document which explains the types of requests / incidents that needs to be handled, who approves, fulfillment levels, severity, status and SLA, and the information that should get captured.

As a BA should i limit to what the PM asked from me or should  produce requirements documentation ?

I would love to here all your feedback on this.


New Post 11/15/2019 1:54 AM
User is offline Stewart F
114 posts
7th Level Poster

Re: Should we produce only what PM wants ? 
Modified By Stewart F  on 11/18/2019 10:51:51 AM)

HI pramodh555

First of all - good question !

This is a an age old problem for BAs - do you do what's right or do you do what your told?

As a Manager of Projects and the Project Teams, I am responsible for both the BAs and the Project Managers, so I can probably see this from both sides of the fence. 

First of all, a question. You say that there is already a high level Business Requirements Document? How long ago was it written and do you know the person who wrote it? Do they still work for the company?

If it Is fairly recent (in the last year lets say) then I would use that as your bible. It should have much of what your PM wants. I suspect that the PM may be looing to take that BRD and take up another level to get things to a state whereby they can actually be built. In which case, his request seems a sensible step. 

However, if he is looking for things that go against that original BRD, then beware. If you can, speak to the person who wrote the BRD. Ask them what challenges they faced and why the project seemed to stall (assuming it did).

If the PM is trying to move things on, which is perfectly sensible, then make them aware of the BRD and ask them if they (the PM) believes any of the stakeholders have changed. There are two reasons for asking this. First, the PM may not realise that there is a BRD, so you are subtlety reminding them, and second, you will need to speak to the stakeholders to get the extra information that you require.

As a side issue, I wouldn't have thought Excel was the best choice of software to write what he has requested. It doesn't lend itself very well to lots of text. I'd do this in Word personally. A small point I know, but it will save you trouble later on.

To answer your question directly "Should I do what the PM want or produce a new BRD?" I would do both! I think the PM is asking for the next level of detail for the project, so I would take the original BRD, save a copy of it, and working on that copy (so you still have an original version available) add the greater detail as you go. This way you do what the PM wants AND you produce some meaningful documentation.   

New Post 11/17/2019 4:05 PM
User is offline pramodh555
8 posts
10th Level Poster

Re: Should we produce only what PM wants ? 

Hi Stewart F,

Thank you very much for your valuable input. That was really helpful.

New Post 8/9/2020 9:46 PM
User is offline sureshbrady
10 posts
10th Level Poster

Re: Should we produce only what PM wants ? 

Just doing what the PM says means they play the role of lead BA. Best to determine what is needed yourself and present this back to the team. 

New Post 10/7/2021 2:13 AM
User is offline TimNickson
1 posts
No Ranking

Re: Should we produce only what PM wants ? 


Previous Previous
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Should we produce only what PM wants ?

Community Blog - Latest Posts

A business analysis checklist helps you stay organized while you work through projects. It includes questions that will help you identify problems in your current processes, and suggest improvements for future projects. Understand the Problem Before you start writing code, you need to understand what problem you're solving. This means u...
I’ve heard “The End is Near!” for Business Analysts for almost 20 years.  Waterfall project management, with its need for formal requirements, is dead…a dinosaur…so 1990’s.  To be honest, that’s mostly true.  With the publishing of the Agile Manifesto in 2001 there was no need for a 2-inch-...
Business analysis is used to identify and articulate the need for change in how organizations work, and to facilitate that change. As business analysts, we identify and define the solutions that will maximize the value delivered by an organization to its stakeholders. We look for opportunities for new business models and new ways to work together. ...



Copyright 2006-2022 by Modern Analyst Media LLC