Skip to main content

Tag: Team

I googled ‘meeting management tips’ and here is what I have learned

Have you ever wondered what it takes to lead the perfect meeting?

Have you looked at your own performance in leading meetings and wondered if it was effective? You may have been tempted to google ‘meeting tips’ only to receive a plethora of Top 3 or Top 10 and the like in your search results. But which one to follow? It seems the number of meetings we attend in a week makes project managers ‘professional meeters’ and one would logically conclude there must be some sort of magic formula.

The reality is that managing meetings effectively takes a lot of practice and a lot of skill. Needless to say that no meeting is ever the same and no attendees are ever the same so dynamics, emotions and agenda items will vary and each will need to be managed. Meeting Management, of course, refers not only to the meeting itself. Meeting Management primarily encompasses three phases, the preparation before the meeting, the facilitation of the meeting and the follow up. The various authors of best practice advice have recognized many components of successful meeting management so each of the three areas has several essential components to consider that appeared most frequently in a google search on ‘meeting management tips’.

Effective Meeting Preparation must include setting clear objectives, setting an agenda and selecting participants.

Let’s focus on the first phase, Preparation. The number one, most frequently given piece of advice is to set your meeting objectives. In preparing for your meeting you should consider if the meeting is necessary, and what the defined objectives are for this meeting. This may detail the specific outcomes from the meeting, such as if you want to merely discuss a topic to level-set or make a decision. Visualize the meeting’s agenda and critically think how you will guide the participants through the topic(s). This will help you firm up the agenda. Consider the level of prior knowledge or interest of the participants and structure the content accordingly. You should start with broad topics and then move to a narrower description, or start to give high level information before tackling detailed discussion. Knowing your participants and selecting appropriate decision makers will be key in arriving at your desired objectives. Sometimes the length of time you have available may not be sufficient to work out the relevant detail so pre-work for participants may be required. This has a nice side-effect in that it may create a feeling of ownership of the meeting and the meeting outcome.

Now to the actual running the meeting. As a project manager you may be facilitating your team to lead a discussion, make decisions, provide status updates, and many other purposes for assembling a team for a period of time.


Advertisement

Facilitate your meeting by controlling your meeting logistics, manage to time and manage your participants.

Aside from planning the obvious meeting logistics, such as selecting the right room, technology and set up there is a number of other logistics items that you can influence ahead of time that will make your meeting run more successfully. Planning a ‘no technology meeting’ and informing participants in advance that no laptops or mobile phones can be used could encourage a faster completion of the agenda and promote more engagement during the meeting. After all, multitasking is a myth, at least if you want to give quality attention to one thing. Another overwhelming number of best practice tips focuses on participant selection. What would a meeting be without its participants and therefore how can you make sure that the right participants will show up?

During the meeting, manage to time. It seems to be one of the biggest grievances of meeting attendees when a meeting runs over time and topics are not handled with sufficient attention. Not only will consistently over-time meetings annoy your patient attendees, it will create a snowball effect for subsequently meetings where attendees show up late. One of these meetings may be your own.

It may sound obvious but facilitating an effective meeting means managing your participants well and this can be one of the biggest challenges. Whether you know your participants well and have to tackle a difficult conversation, or you do not know your participants well and try to get through unfamiliar topics. In the first scenario your challenges might come in the form of unexpected emotions, or on the other side of the spectrum a phenomenon called ‘group think’ where in order to ensure harmony the group may make irrational decisions to keep the balance within the group and what is worse the facilitator is often unable to recognize it. The second scenario of unfamiliar attendees and topics already provides a queue to the facilitator to prepare in advance of the meeting, learn about the individuals invited, and prepare the agenda well.

Follow up and close the loop.

Meeting done and closed. Let’s move on. Not so fast! An integral part of any meeting is to close the loop in the form of action items and notes from the meeting. Following up on the discussions held and making sure that agreed decisions and actions are communicated not only ensures that attendees remember what they agreed to, but it creates a sense of purpose that the meeting was time well spent, opinions and ideas were heard and documented.

Some final thoughts

Did you know that the average office worker spends about 35% of their time in meetings? You may say this is true for you. Or you may say this is widely underestimated. The truth is, we all hate to waste time in badly planned or facilitated meetings only to find that the agreed actions are not followed up. Our job as project managers and meeting facilitators is to make sure that we facilitate effective and efficient meetings that will ultimately further the aims of the project. The above meeting management tips are not a comprehensive guide to any meeting but they touch on the most essential components that authors and meeting facilitators again and again select as their top tips.

A Roadmap to Agile

Transitioning to Agile is well worth the effort and benefits, but the way is not always easy and can be filled with issues and frustrations, as well as wrong turns.

To try and be successful in your transition, use a roadmap for the effort, and plan to spend some time and effort on the journey itself. Steps to start can look like this:

Pick the right person to lead the transition effort. This person will have energy and enthusiasm, and insight into Agile.
Pick a small project, one without a lot of complexities surrounding its next release target, and one with team members ready to learn.
Use a collaboration tool that may already exists in your org or purchase a limited number of licenses on something new, or select a different method to collaborate such as a wall board.
Get together with team members and set some goals, gain a common understanding of what comes next, and what comes later.
Expect the change to take some time and energy.
The lead of the transition effort can secure the collaboration tool and users’ access or create the wall board, schedule the meetings, and answer questions as they surface.

Plan for the first phase:

Pick a practice or a handful of practices to start with, such as changing requirements to stories, then start using the tool or wall.
At a round table, get everyone’s buy-in and ownership-of a workflow, keeping it simple for this first phase.
Schedule and set expectations of a daily standup.
Estimate your stories or translate estimates from the Project Plan.
Start sprinting, with a Sprint Planning session.
Have a retrospective at the end of every sprint for a while, even if just to share, question, and vent.

By roles, have each team member do some part in transition prep, a possible list could look like the one below:

Agile Lead: secure the tool or wall for collaborating, schedule standups and a Sprint Planning session for 2 or 3 weeks forward. Use Agile terminology, to start making it common language.
Product Owner (BA): start to translate the highest priority requirements into stories and organize them into epics, facilitate with team member inputs.
Create the backlog and prepare stories for Sprint Planning. Readiness means that the stories will have the details of the requirement, be useable by developers and QA, and be estimated. Work with the business to start ordering the backlog by priority.
Developer: Contribute to grooming the former requirements, now stories, with the PO/BA and give your best-guess estimates.
QA: Contribute to grooming the former requirements, now stories, with the PO/BA and start deriving your Test Plan and Test Cases. Follow the Backlog order of priorities.
Lead (again) be ready for Sprint Planning, and in the beginning, invite everyone to contribute and participate.

Leadership needs to be involved too, especially at the start and through the first phase. Whoever has the power and authority to set a directive needs to step forward and communicate clearly that this is desired by the organization and that the participants need to participate. This is critical in overcoming resistance, even among team members who seem to be eager and willing initially.


Advertisement

The next step is to set the objectives for phases 2 and 3, and onward. This will accomplish two important aspects of success:

  • setting shorter term goals that are easier to reach
  • measuring success by outcomes

As well, creating and displaying a phased roadmap can instill the idea that Agile is ongoing in its adoption, continuous as the team grows into it, and a practice that can optimize over time.

mclaughlini 032218 1And, information can be shared and leadership can take note that there will be slow changes not only in delivery, but how people are working. At its best, the list below is how teams and individuals transform:

  • Authoritative hierarchy -> self-organized
  • Silo’d work -> interactive
  • Predictable and rigid delivery of work -> nimble, and changing or changeable
  • Documentation heavy -> documentation light
  • Formal communication -> transparent and informal communication

These changes are significant for teams who experience them. Many people have spent a career honing and executing specific skills and may need time to change their way of working. Others, may have recently finished school where Agile-like practices were the norm. Changes in the workspace atmosphere and social interactions should not be underestimated. These personal, and interpersonal changes require support and attention from leadership. Stress and resistance can best be eased through inclusion, especially in decisions, and fostering ownership of results by the team members themselves.

After at least 3 sprints, a team will be ready to look back and start planning for Phase 2. And in an Agile approach, they can set sights on what Phase 3 will look like. Post and socialize your roadmap to see what comes next, and be sure to come together often as a team at round tables!

Onboarding a New Business Analyst

It’s always exciting to add a new member to your team, but it can be a bit stressful.

Some advanced planning can make the transition easier and ensure that your new Business Analyst has everything needed to be successful.

Every new employee comes with a unique set of experiences, so it is necessary to assess their current skills as compared to the responsibilities of the new position. Some of this assessment was done at a high-level in the interview process, but now the details need to be analyzed. Consider the following criteria:

  1. BA Skills: How many years of business analysis skills does the team member have. If they are moving from another team within the company, they may need more basic training in Business Analysis techniques.
  2. Industry Knowledge: Has the BA worked in your industry before. There may be specific terms, acronyms and business concepts that they need to know.
  3. Technical Skills: Determine what tools are commonly used by your team that require training. Examples include: Team Foundation Server, Jira, Confluence, SharePoint, video and screen capture tools.
  4. Soft Skills: This may not be immediately apparent when evaluating a new team member but there are several that all Business Analyst need in their toolkit.
  5. Software Methodology: Is your project using a traditional waterfall or Agile methodology. Does your team need to understand the Software Development Life Cycle (SDLC), Dynamic Systems Development Model (DSDM) or Scrum?
  6. Internal Processes: These are different for each organization and department and will need to be included for every new team member.

Once the required knowledge and skills have been identified, we need to look for existing resources available to train new hires. Be creative. Think outside the box but stay within your budget.

  1. Organizational materials: Most companies have some basic training materials. Some departments may have developed some on their own. Ask if they will share and see if all or portions are applicable.
  2. Team Handbook: Providing the new BA with a handbook or Quick Reference Guide of internal processes can provide a high-level view of the new role. When they ask questions that are not answered in the handbook, the resulting revisions will help the next new team member. If it doesn’t already exist, now is the perfect time to build one. Start at the beginning, what does a BA do every day, every week, every iteration, every release.
  3. One on One training: Internal processes are typically trained by another person on the team. Shadowing an existing BA as they take a feature or requirement from beginning to end is quite helpful.
  4. Internal training classes: If you company provides software internally or externally, they may also have classes or computer-based training available for the application.
  5. Reference Books: Does your team have a library or book shelf of technical reference books? These are very useful for information on BA techniques, technical skills and software methodology. Make it a habit to browse your favorite book seller every few months for new titles.
  6. Learning Management Systems: Some organizations subscribe to a Learning Management System (LMS). Scour the catalog for topics that have been identified.
  7. Blogs, articles and webinars: Always look to BA Times for webinars and articles that meet your training needs. In addition to tasking them to create an account, provide a list of links to the webinars and articles to view.
  8. Third party vendors: Determine if there are in person classes from a third-party vendor in your area for some hands-on training.

Advertisement

Creating an onboarding plan will help clarify expectations and provide some short-term goals for the new addition to your team. Some suggestions are:

  1. Checklist: A standard checklist for your team can be created that is reusable and modified based on the individual needs. This keeps the things from falling thru the cracks during that hectic first few days.
  2. One-month plan: Define the most important training tasks to be completed in the first month.
  3. Track tasks: How does your team track tasks? Outlook, Excel, SharePoint, Kanban, Jira or Team Foundation Server? You may consider creating tasks for the training to be completed.
  4. 90-day plan: What are the longer-term goals. What activities should the BA be proficient in to be considered a contributing member of the team.

The onboarding experience creates a lasting impression that can determine the new employee’s success and happiness on your team. Conversations about goals and expectations should occur weekly in addition to explaining the “why” behind the processes. Handbooks and training materials should be updated and relevant. Reasonable time should be provided for the team member to complete necessary training. Don’t overwhelm your new employee in the first few weeks. Remember, everyone is unique and there is not a one-size fits all approach.

Survival Guide for the BA Consultant – Top 10 Techniques

This article describes survival techniques that can be used by anyone who has an office job, but focuses on consultants, and in particular, business analysts.

Business analysts are generally in contact with more members of an organization than other consultants, since they interact with both IT and business personnel and are often called upon to explain to senior management the business requirements, solution options, and the alignment of the solution with the business. The manner in which business analysts interact with these different types of people is critical if solid working relationships are to be established.

1) Be Courteous

Thuswaldner 112817 1It’s good to know your stuff, but no matter how good you are or how many books you’ve written, if you are perceived as being difficult to work with, people will find ways to avoid you. If you’re a contractor this will result in, at best, the non-renewal of your contract, or at worst you may find yourself being escorted off the premises by security. If you’re an employee, you may find yourself tasked with a make-work project that requires minimal interaction with staff. Either way, the outcome will not be pleasant, so make an effort to be courteous and pleasant with your colleagues and you will find your day to be more enjoyable and the people that you need to interact with will want to talk with you. Remember, you’re never too important to be nice to people (John Batiste).

2) Listen

Thuswaldner 112817 2If you are an experienced business analyst, you probably have lots of great advice to offer and lots of stories to share. The challenge is to limit the sharing of your personal experiences and to spend more time listening than talking. The saying that you have two ears and one mouth so you should do twice as much listening as talking speaks volumes.

Are people looking at their watches when you drone on and on about yourself? Look for signs of interest or disinterest in the people that you’re speaking with, and adjust your delivery accordingly. Listening to someone explain something that they know about is a great way to get that person onboard.
It’s a tough pill to swallow, but you may not be as interesting as you think you are and not everyone is going to want to listen to your war stories. You’re not going to learn anything if you’re talking, so put your ego aside and start listening.

3) Remember Names

Thuswaldner 112817 3Have you ever been introduced to someone and then immediately forgotten their name? You’re not alone. As a business analyst, you will meet many people that you will interact with on a regular basis, so you may as well get to know them. That begins by not just remembering their faces but by remembering their names. There are lots of techniques that you can learn in order to remember names, and we won’t go into all of those methods save for one: When you are introduced to a person for the first time, repeat the name by saying “Hello Jennifer”, or “Hello Peter”. This will emphasize the name in your memory.

Remembering a person’s name is not just good form, it gives you a leg up on those who don’t remember, either because they’re not able to or can’t be bothered. It also serves as a message to the other person that you are interested in them and what they have to say, and you are more likely to get quality information from this person that will help you do your job.

Forgetting someone’s name, or making a guess, is something to avoid, but if you forget it’s best not to guess – just apologize, admit that you’ve forgotten, and move on.

4) Research the Organization

Thuswaldner 112817 4Equipping yourself with knowledge about the organization will demonstrate to your clients an interest in the organization and will also enable you to adjust your approach in order to be compatible with the organization’s culture and work environment. Some factors to consider when researching an organization are:

  • Organization size and the number of employees
  • Organizational structure, culture, and mission statement
  • Organization history
  • Competitors
  • Working conditions and work environment
  • Main products, services, and programs
  • Annual sales, funding sources, annual budget
  • Location of headquarters and other office locations
  • Internal job descriptions
  • Dress code
  • Morale of employees

5) Make Your Ideas Your Client’s Ideas

Thuswaldner 112817 5As a business analyst, especially as a consultant, you are hired to use the experience that you have acquired over the years to deliver innovative and creative solutions. Your goal is to contribute to the successful delivery of the project or the organizational initiative. You are not looking for a promotion, but your client might be, and if the project or the initiative that you are working on is successful, the chances of your client being promoted, or at least recognized, are elevated. This may be warranted because if your client was smart enough to hire you, and you delivered, then that deserves some recognition. Therefore, try to be humble and make it your mandate to make the people who hired you look good by letting them take the credit for your work. If you put those around you first, this will be noticed, your client will love you, and you will be rewarded with respect.

6) Deliver Beyond the Expected

Thuswaldner 112817 6

Your client has more than likely indicated to you what is expected from you and you will, of course, make those deliverables your priority, but that doesn’t mean that those should be your only deliverables. As an experienced business analyst, you know that there may be other areas that will need to be addressed, and as long as you are not treading into someone else’s area of responsibility, you might consider identifying these areas to the client. Consider for example a business analyst who was asked to develop a series of process models describing a particular business area. This particular person was hired because she has experience in process modeling, but she also has experience modeling business information, and knew that if each of the process models identified the information that is used or created, there would be added value for the client. The business analyst spoke to the client, made the pitch to develop a logical data model, and delivered more than was expected of her.

Exceeding your client’s expectations doesn’t always have to have the “wow” factor. There are many less grand ways that value can be added to the service that you provide. By thinking outside the box and avoiding the status quo, asking yourself if there is a better way to accomplish the tasks that are at hand, and keeping in mind the best interests of your client, you will exceed your client’s expectations.


Advertisement

7) Make Friends with Admin Assistants

Thuswaldner 112817 7Although the administrative assistant holds one of the lowest paying jobs in an organization, they play a key role in its success. They are usually the first person in an organization to answer the phone. They are responsible for booking meetings, arranging documents to be signed, and locating specific documents.

They are the gateway to the executives of the organization, and they have the power to help or hinder you as they choose. If you treat them with respect they are more likely to make things happen for you. Like any person, when they are treated well they will respond in a positive manner. It’s just all the more important to treat the administrative assistant respectfully, because they can make or break you.

8) Make the Difficult Client Your Friend

Thuswaldner 112817 8If you work long enough in an office environment you will eventually find yourself having to work with someone who is difficult. This is a person who will irritate you by either being uncooperative, disagreeable, unfriendly, or outright caustic. If it hasn’t happened to you yet, it is just a matter of time, and if it has happened to you, it will probably happen again, so it is a good idea to equip yourself with a few ways to manage this type of person. The first step is to realize that there is always an underlying reason that makes the difficult person difficult. It may be due to an insecurity, a perceived sense of a lack of respect among their colleagues, or problems that they may be having in their personal lives. Whatever the reason, you do not want to add to their stress by becoming a threat to them. A natural tendency is to avoid such people altogether, but before you revert to this, there may be a better way. Instead, draw them into a conversation where they do not feel threatened. The manner in which you engage them needs to be gentle, and the topic needs to be carefully chosen, but the main point here is to make them feel valued. If you don’t know the person, then you have no reason to doubt that they can make a valuable contribution to the task at hand. If on the other hand you are acquainted with the person and know that they may not be that helpful, you will need to find a way to gracefully minimize this person’s impact on the project and the team members.

9) Proofread all client-ready documents

Thuswaldner 112817 9We are all writers and readers with the need to be understood and to understand, and therefore, writing in an effective and efficient manner is important. Written materials such as formal documents, slide decks, handouts, and emails that you produce are a direct representation of you and the quality of your work.

With spell-check, there is no excuse for spelling errors, and poor grammar can contribute to confusion and create additional work in order to clear up misunderstandings. Learn to “write right” either by taking a course on business writing or at the very least picking up a book on the subject. A book that I refer to often is The Elements of Style (William Strunk and E.B. White). When your client reads a document that you wrote they will have one of two thoughts, and it will be either good or bad – a document is rarely thought of as middle-of-the-road, and why take that chance anyway? This is your time to shine, so you might as well put everything into it and wow them.

10) Sometimes “Good Enough” is “Perfect”

Thuswaldner 112817 10Up until now, we have talked about being better at what we do as business analysts. We have talked about talking less and listening more, remembering people’s names, being humble and not seeking validation all the time, greeting people in the morning (when all we really want is to be left alone with our emails and our coffee), working with grumpy people, writing awesome documents, and so on. But sometimes, it’s ok to take a break from this drive to be the perfect business analyst and be satisfied with who we are. The suggestion is not to revert to sloppiness, but rather to strike a balance between what is desirable and what is achievable. The perfect document, for example, that is never shared is far less helpful than one that is 80% quality, since the extra 20% may not be worth the time required to achieve it.

Conclusion

We all want to survive in the office environment. But most of us want more than to just survive – we want to thrive. We want to feel good about the work that we do and we want to have good working relationships with our colleagues, and in order to do that we need to recognize that human relationships are just as important as technical know-how. By implementing any or all of these survival techniques, you will see positive changes in the quality of your deliverables and how you work with the people around you.

A Project Full of Business Analysts

If you are your company’s only Business Analyst, you might have it easier than the rest of us.

You make the BA rules and you are always on the same page with yourself. You read all the articles on how to gather requirements and you have the documentation down pat. From beginning to end, you have all the answers, you understand the business need perfectly and you know things will go as planned. In your “the only BA” world, there are no surprises for you unless you forgot something or you assumed something or the change failed. My point is, you have the control and the full responsibility.

When BAs share a change or a project, things can get tricky … fast:

  1.  Get the BIG picture: If all of the BAs who will be involved in the project do not know the why, what and when, problems are a sure thing. For this reason, we want to avoid coming in late to a project or miss a kick-off meeting at all costs. We may not be good at having the right people in the room, so BAs need to be aware of initiatives coming down the road and make sure we are included day one. Every BA involved needs to start on the same page and begin communicating with each other right away. “Here are my take-aways” and “My change starts when you are done, but before ….” etc. I know, the big picture changes, but multiple BAs need to know where they fit in relation to different requirements. Chase that moving target down!
  2. It’s all about Bandwidth: We are assigned to the same project, but I am ready to go and you are still finishing a different project. This means we have to talk about our bandwidth and our calendars – business and personal. We can agree on a date to start, but if you are OOO two weeks later for four days, I need to know this. My testing may need to be put on hold, I may start another task early while waiting for you to return. Share calendars!

  3. Advertisement

  4. The Multiple requirements: Our individual requirements may be different in why we need to make a change or build a new process, but we know for a fact that we are linked together by a common project. BAs that try to run alone during a multiple BA project end up taking everyone down because the loner was positive their changes did not impact anyone else. We need to look for those points where our process starts, updates, communicates and hands off to the next step in the big picture process. Meet with the BA that is making changes that flow into yours or just before your changes. Document this info. If you are updating, find the BA who supports what you are updating/adding/cancelling/communicating and make sure the format is expected and the timing is correct. Document this info. Understand what happens when your personal process change ends. Find the BA who takes it from there and make sure they have what they need from you. Document it.
  5. We got test plans! : My test plan tells me I have my ducks in a row, just the way I planned. What it doesn’t tell me is how my changes fit in with anyone else’s changes or an existing process. Reach out to the other BAs on the project and ask them to let you know when they are ready to test with you. Don’t be surprised when that BA who is used to working in a silo pushes back. This is our opportunity to make all the BAs better by saying we want our project to run smoothly. 😉
  6. Uh-oh: Such a great feeling when the changes move to production and things are working as expected! Yes, but when something goes wrong it is also a great feeling having BAs working together to solve the problem. Nothing is your fault. You worked together and communicated about the why, what and when. You all built the new process together and a hiccup anywhere along the line means everyone has the hiccups. You can hear the conversation now – “We tested this piece, right?”, “What did we miss here?” and (my favorite) “Umm, I never heard that was a must have, did you?”
    A team failure is quickly another team win when the group solution is found and the lessons learned are discussed after the fix is in. This kind of win is huge!

So, get on the same page, communicate regularly, support each other and provide a second set of eyes. Know your peers that are involved and what kind of knowledge they can share with you and let them know you are available to return the favor! BAs working together on requirements and changes make for a strong project.