Monday, 02 March 2009 19:00

Managing Large Groups of Stakeholders

Written by  Jonathan Malkin
Rate this item
(0 votes)

You've just been assigned a new project.  You're excited to get started but then find out the customer wants to have 18 stakeholders instead of the usual six to eight.  Reaching consensus with 18 people is a little more difficult than with six people.  Try getting 18 people to agree on lunch and see what I'm talking about!

How do you handle a large group of vested stakeholders? 

  1. Push back on constraints
    Part of your job as a business analyst is to ask the tough and uncomfortable questions. Why does each of the 18 people need to be at this meeting?  Is each person a decision-maker or a provider of information?  Six providers of information were asked to provide their data in advance.  By providing information ahead of time they were no longer required at the meeting. Why are they there?
  2. Double the estimates for all work
    Reaching consensus in a meeting is one thing.  Reaching consensus on document reviews once everyone has gone back to their regular work schedule is another.  Make sure to double the expected turn-around time for all document reviews or other work requiring participation of all stakeholders.
  3. Organize the team
    Make sure each person on your team knows his/her roles and responsibilities.
    In our meetings typically I present, facilitate, and generally do the "song and dance".  The project manager documents decisions, action items, why decisions were made, and anything else that may help.  The subsequent work of managing the project schedule, conducting analysis, and other key tasks is also clearly divided. 
  4. Expect additional work
    Additional tasks will "spring up".  The project sponsor may request reviews, demonstrations, or other key meetings to keep abreast of all decisions and changes.  Make sure to do whatever it takes to make this person happy.  After all it's the project sponsor who ultimately calls the shots and signs your check.

In my recent experience, a project sponsor wanted to see the "user experience".  I created a document including a flow chart and screen shots walking through a simple purchase scenario.  We reviewed the document, demonstrated a live system and answered all of her questions.  The project sponsor was given a clear picture of the system she purchased and was able to assign additional tasks to her staff.

In summary, with a little planning and preparation, working with a large group of stakeholders can be a rewarding experience that asks you to work in new ways, to be patient and flexible,  and to improve your skills.  


Jonathan Malkin is a Business Analyst at Plateau Systems.  Jonathan provides configuration, integration, documentation, and deployment support services for a leader in Talent Management Systems.  Jonathan's areas of support include 21 CFR Part 11 Validation, SF-182's, EHRI compliance and customizations to COTS software for which he has won multiple awards.  His experience includes work in the federal government, telecommunications, mortgage and banking, and custom software development industries.  Plateau Systems is a leading global provider of adaptable, unified web-based talent management software, content and services to onboard, develop, manage and reward talent.

Jonathan may be reached by email at This email address is being protected from spambots. You need JavaScript enabled to view it. or by visiting his LinkedIn page at http://www.linkedin.com/in/jmalkin

Read 1372 times Last modified on Tuesday, 27 March 2012 13:46

Comments  

 
0 # Utkarsh 2009-03-08 21:44
Hi my name is utkarsdh & I have a question - As a BA while you have gathered all the requirements from the client, how do you make sure that these are understood by the development team - is there a any kind of template on which a BA documents what he has learnt from the client & then pass it on to the development team ?? any kind of views, ideas, suggestion will be much appriciated- thanks
Reply | Reply with quote | Quote
 
 
0 # Jonathan Malkin 2009-03-10 10:29
Yes, it is important to have a repeatable process that includes templates or systems for organizing information. That's a really long way to say yes you should have templates. Beg in by organizing BA's at your company into a luncheon. Casually discuss common tasks and issues to see how you can standardize. Do you gather similar information? Do you typically have the same meetings? What do you all have in common? If it's just yourself then consider the things you do repeatedly, write down the steps, and standardize. W e have standard templates for capturing customer decisions and we follow that template in facilitating decision-making workshops.
Reply | Reply with quote | Quote
 
 
0 # Utkarsh 2009-03-11 03:19
thanks Malkin, for the reply that was very prompt.. your last lines are making me a bit greedy:) can the templates u are takin about be shareable & if so request u to please forward the same. Thanks Again
Reply | Reply with quote | Quote
 
 
0 # Jonathan Malkin 2009-03-11 05:37
So sorry. My employer would likely frown on forwarding those documents. They are specific to our process and the information we gather so they would not be directly useful to you anyway. I'd be glad to entertain some of your ideas and give you some direction on creating your own. Just send an email to
Reply | Reply with quote | Quote
 
 
0 # Utkarsh 2009-03-11 21:41
well, I guessed that. but that would be lovely if you can guide me with these docs, will get in touch with you again..appricia te your prompt reply . cheers Utkars h
Reply | Reply with quote | Quote
 

Add comment