Search This Blog

Showing posts with label Business Analysis. Show all posts
Showing posts with label Business Analysis. Show all posts

Saturday, May 28, 2016

Prioritization - What is That?

As I continue my posts about interpersonal skills, one area that I have used my interpersonal skills as of late, is in the area of prioritization.  You want to talk about having to be a strong communicator, negotiator, influencer and facilitator.  My goodness!  Prioritization is not black and white.  It's definitely not black and white if you are working with a lot of different partners, who also have processes in place, where they have a pipeline of work they have to prioritize.  Prioritization has always been an interesting topic to me because it is really based off of someone else's perspective.  Even if you have created a process of prioritization that is based on calculations, it is still someone's perspective on how that calculation should work.  As I work with clients a popular question that comes up is, "how do you get everyone to agree on work to be done?"  I will be totally honest, I don't have a direct answer to these question as I experience these challenges every day as well.  Everyone situation is different because the players are different.  Depending on the players may determine the approach you take.  However, I can provide some guidance on some things to keep in mind as you go through this process called prioritization.


  • Communication is Key - I don't care what type of methodology you use, or the environment you are in, if you cannot communicate you will not get anything accomplished.  What I find interesting is that most people thing they communicate well when in actually they don't and and there is opportunity for improvement.  It's not just what you say, but how you say it.  The tone you set to conduct this prioritization will determine the responses, and engagement, you will receive from the audience throughout the process.  I would recommend that you don't come off like a dictator.  I will give you an example of something I have experienced in my career, as I have sat in many meetings, where items needed to be prioritized.  I was in a situation where I worked in a matrixed environment.  For those who may not be familiar with a matrixes environment, I reported directly into one leadership chain in the organization, but was a dotted line to another one that I needed to work closely with.  The leadership chain I was reporting into had prioritized some process work that needed to be done.  However, in the matrix environment I was a dotted line into, they also had a huge initiative they were leading where my team was needed to conduct some work as well.  The approach that was taken by this other group was to come in, advise me that their initiative was the highest priority and advise that is where the focus should be.  That didn't work too well for me for a few reasons:
    • Issue #1 - This individual did not even take time to understand the current environment being new to the organization.  Nor did they take time to understand why the work was prioritized the way it currently was.
    • Issue #2 - The individual pretty much came in and told me what I needed to do (really this was a bully approach).  This never works.  It definitely doesn't work for me, especially if you want me to partner with you.
    • Issue #3 - This individual did not listen to my concerns on why these priorities could be not only conflicting, but impact how work would get done, because the same resources were being leveraged.
    • End result- The communication approach totally turned me off and it ended up becoming a battle of wills.  I have to admit I do like a challenge so I was not giving in very easily, and frankly, didn't give in at all.  Actually, if I must be totally honest, I still would not want to work with this person regardless of how much skill is present.   The entire situation and approach turned me off.  Unfortunately, this happens all the time and one of the reasons getting anything prioritized is an act of congress.  Be very deliberate, and thoughtful, in your tone and approach as that can make all the difference in the world.  The goal is that when you leave the meeting that everyone agrees on the priorities established.

  • Agreed Upon Prioritization Criteria -  It is imperative that everyone agrees on the ranking criteria.  As well as have clear definitions on what that criteria means.  Prioritization may not be just "high, medium and low".  There may be other reasons where you may need to use a numerical ranking system, or different levels of category.  The most important thing is to define the criteria and ensure everyone agrees with it. Try to be as specific as you can when you define the criteria as well.  
    • For example, what does "high" really mean? You may define the category of "high" as: 
      • Significant legal, operational and reputational risk to the company (i.e. will result in litigation if not remedied immediately, will cause significant operational risk and/or could potentially hit the media in a negative light).  
      • High volume of occurrence (95% of negatively impacted accounts).  
      • High negative customer experience (90% or more of customers are impacted).  
    • You need to get down to potentially quantifiable criteria to give everyone the same perspective. Then you need to determine how everyone will come to agreement on the correct priority (i.e. what type of voting system do you use or decision system).
  • Ensure All Needed Stakeholders Are At The Table - One mistake that is made is prioritization in a vacuum.  If you know that there are other areas of the business you will need to get the work done, engage them.  Other partners have a pipeline of work as well, so you may as well have that conversation upfront to get realistic time frames in place as you try to prioritize.  Also, you may need to incorporate their prioritization perspective in the criteria as well.  There may be other categories that need to be taken into consideration based on the work that is performed.  Don't get irritated or annoyed because business partners are introducing new criteria.  It's better to take that into consideration upfront than deal with the drama later.  Everyone needs to have a voice, whether you agree with that voice or not.  You just need to ensure you have a strong facilitator to keep everyone on task to reach the ultimate goal of prioritizing work that everyone feels comfortable with.
  • Take Emotions Out of It - To be frank it's not about how you feel so get over that, and yourself, before you walk into the room.  It's all about getting work prioritized so you and your team can focus.  Get rid of the ego and ulterior motives.  There is no room for that and it provides no value whatsoever.  Nobody really cares about them anyway and it's a total waste of energy.  Walk into this conversation knowing you may have to make some compromises.  Definitely give your perspective and share concerns, but don't be driven by emotions  This is truly not personal so don't make it that way.  If everything you want doesn't happen, get over it.  Trust me your stress level will go down and you will be a happier employee.  Plus everyone around you will be happier too.  :-).  
  • Revisit Your Prioritization - Once you have your prioritization list it doesn't stop there.  As you know, change is constant, therefore, priorities will change and shift.  Come up with a frequency on when you revisit your prioritization list. The priorities may have to change over time so this first blush doesn't mean the work is done.

Don't get me wrong, I'm by no means saying this work is easy.  It's not and it's been a constant challenge in my career.  It's hard to identify everyone who needs to be involved, let alone determining criteria.  However if you don't, it causes pain throughout the entire process.  It causes bottlenecks to where work cannot get done. The conversations are hard, but crucial and critical.  They need to happen.  We need to spend more time communicating upfront before we jump into doing all this work.  I'm still working through how to make this process less painful and I'm learning everyday.  I'm open to any other best practises out there as well so please share.

Happy prioritization!!! :-)

Regards,

Paula A Bell Consulting, LLC
Twitter: BAMartialArtist

Wednesday, May 2, 2012

The Prioritization Juggling Act

One of the hardest things to do is to get a group of individuals to prioritize tasks. This is hard because: 1. Decisions have to be made - which is a challenge in itself to get decision makers to make the decision 2. It's not all about you - you may have to give in on some things you really want 3. Uncertainty - if I prioritize something lower than something does that mean I won't get it all As business analyst and even in our personal lives, we deal with this prioritization juggling act through our projects and life. How do you prioritize you day? How do you prioritize your work? How do you prioritize getting from point A to point B if you kids involved in different activities? One thing I have learned, from a project perspective, is that a high, medium, low scale does not always work because most people will rate everything high. This results in wasting time and starting at the beginning. The rating is not as important as the way of thinking to clearly map out your goals. This is where the "Systems Thinking", which I love comes into play. Here are some new ways of thinking that an help you. 1. Before you start prioritizing truly understand WHY it's a task or item to be prioritized. You might say to me, "I already do that!", but do you really? How many times, as a business analyst, are you handed tasks to do and you just work them without asking questions because you were told they are needed? How many of us challenge the process to truly gain the understanding of how what we are doing is adding value to the organization and not just to meet a date? You may ask, "What does this have to do with prioritizing?" Well everything! Why even prioritize something that shouldn't be prioritized in the first place. Understand the VALUE. Systems thinking can be leveraged here and throughout this post as a way to understand the whole and not just the parts. 2. Once you have the items that need to be prioritized, bundle like items together and understand any interdependencies. How do these items relate and what are the impacts if they have different priorities? This is some analysis that gets missed upfront and then is paid for when the system is being designed or tested. This means more analysis should be done upfront. Context diagrams can be used to understand data flow, functional decomposition diagrams can be used to break down tasks as a few tool examples. 3. Identify the TRUE decision makers. Do your stakeholder analysis to determine who needs to be at the table to help make the decision. The RACI model can be used here as a tool. 4. Determine the format to present the information for productive and fruitful conversations so decisions can be made. In this documentation define the ranking system. I would suggest using some sort of numbering system. For example, number "1 - X" or a defined system where "1 = Must Have", "2 = Must Occur 3 weeks after 1", etc...This is just an example and this will have to agreed upon by the project team and decision makers. Make sure your rating skill is specific to clearly depict the value of the item being discussed. May be a matrix or excel spreadsheet as potential tools here. 5. Empower the decision makers to prioritize by listening to their concerns and ensuring they feel valued. Do not interpret them when they are speaking and do more listening and less talking. It's not about rushing throughbthebitems but really identifying the priority of items to be worked. This will make your life easier in the long run and really keep you focused on what should be worked at the time. This will take you really using your leading with influence skills. If there is one thing I want to stress is that the thinking you use to get to the point of prioritization is key as well as throughout the prioritization process. Always think, what is the VALUE add to what you are prioritizing? Asking questions upfront will help you to gain that knowledge. Don't just prioritize for the sake of prioritizing. Regards, Paula Bell www.paulaabell.com

Wednesday, April 4, 2012

The Virtual Business Analyst

Check out my lastest aricle on Modern Analyst

(copy and paste the below URL in your browser)

http://www.modernanalyst.com/Resources/Articles/tabid/115/articleType/ArticleView/articleId/2173/The-Virtual-BA-Business-Analyst.aspx

Regards,

Paula Bell

Wednesday, March 7, 2012

Expanding Your Role


I have had the opportunity to be in a Requirements Manager role on quite a few multimillion dollar projects. I have learned a lot about not only managing requirements but also working with people. I have been the "go to" person for multiple business analysts who are writing requirements on said projects.  I have found that in order for me to be successful in this role I needed to be very strong in the following:
  1. Strategic Thinking - making calculated decisions that will align with the overall company strategy. Ensuring I understand the organization's strategy.
  2. Holistic Thinking - understanding how the project fits with the overall company goals objectives and strategies.  Not being siloed in just my own area but understanding the impacts of other areas.
  3. Critical Thinking & Problem Solving - other business analysts are depending on me to help solve problems that are escalated to me.  I need to be sharp in solving problems and thinking critically to question assumptions.  
  4. Time Management - ensuring I manage my time to provide support to the business analysts that are working on the project in which I am the Requirements Manager as well as making sure I get my work done as well.
  5. Resource Allocation - I have to understand each resources' strength, area of opportunity, domain knowledge, personality and more to determine what task to assign to what resource. I always need to understand their resource capacity to ensure I don't over allocate a resource which in turn could result in the resource not being as successful as he/she could be and in that instance I may need to roll up my sleeves to help with the workload.  I'm not going to assign anyone anything I would not do.  We are a TEAM!!!!
  6. Negotiation Skills - there are many times during the gathering of requirements items need to be negotiated. I have found this negotiation occurs a lot when requirements need to be prioritized but it does occur through the entire life cycle. 
  7. Communication Skills - I have to be very effective in communicating out tasks, expectations and timelines. I have to know the communication style of each resource to ensure what I'm communicating is being understood.
I am very happy I've had the opportunity to be in this role as this role has sharpened my skills in so many areas and so many critical areas. If you have a chance to expand the role you are in to learn more things I suggest you welcome that opportunity. There is so much to be gained and learned.

Regards,

Paula Bell
www.paulaabell.com           

Wednesday, February 1, 2012

The Approach


I have the privilege of mentoring and coaching many business analysts and I learn so much from each relationship I am a part of.  I had a very interesting mentoring session this week where my mentee and I talked about the steps she would take if all she received was the project scope, a list of 5 SMEs and was told to gather requirements to make changes to a web application.

I must first say she is relatively new to the business analysis discipline and currently reading through the BABOK.  As we ate lunch I thought it would be interesting to see what she would do in that situation, though she hasn’t experience it yet. 

She advised she would do the following:

1.    She would do some sort of document analysis to determine what documentation is already present that she can learn from.
2.    She would then have a brainstorming session with the SMEs provided to understand their requirements and capture their requirements.

For someone relatively new to the discipline this was a good start. I told her that she was going in the right direction and we started to take more about some things she could ask and some more things she could do.  I had to emphasize that the approach she chose to take is key to project success and as she continues to do business analysis work she will get more and more skilled based off of past experiences on how she should approach certain projects. Let me state I'm not saying that the approach cannot or will not change, but there needs to be some serious thought on what should be done prior to jumping into business analysis activities. Through more conversation with this scenario we came up with the following as some additional things to consider, again this is not the end all list but it is amazing just through some conversation her two bullet points 7.

1.    Before diving into anything we decided we needed to find out more information such as:
a.    What is the timeframe for this project?
b.    Who are the stakeholders and what are their roles? (stakeholder analysis)
                                          i.    Who has worked with these stakeholders in the past? (What are their likes or dislikes? How do they like to be approached?)
c.    Clearly understand the scope
                                          i.    How does this project relate to the overall company strategy, goals, objectives, etc…? (enterprise analysis)
                                        ii.    What is the desired goal of the project?
d.    Research what documentation already exists and learn as much as possible prior to any meetings.  Determine if information in previous documents can be leveraged in the project. (document analysis)
2.    Determine the methodology and documents to be completed and how those items are going to be monitored and tracked for success (business analysis planning and monitoring)
3.    Start Elicitation activities (determine meeting time, location, agenda, individuals to be included, obtain materials for the meeting such as flip charts, post it notes, etc...)

We stated to talk some of things that could occur in the meeting such as individuals that will not talk or the individuals that take the group off in tangents briefly. 

Based on this conversation she determined that there was a lot more to think about and consider before starting the actual work. This is an area that is a struggle for BA's new to the discipline and even those who have been doing business analysis for a while.  Getting started can be the challenge.

It's not about being quick to jump into the work but rather taking time to:


1.    Understand the problem to be solved, the timeline to solve it, the stakeholders and their roles, the overall goals and objectives of the enterprise. 
2.    Determine your approach to gathering the requirements such as methodology, documentation templates that add value, conduct documentation analysis to determine what already exists that you can leverage.
3.    Begin requirement activities (elicitation, prioritization, verification and validation, documentation creation, final approval)

There is clearly more to this than just what I mentioned above but at a high level this will get your going.

Regards.
Paula Bell
www.paulaabell.com