Skip to main content

Tag: Project Management

BATimes_Apr18_2024

Beyond Frameworks: Agile Insights from a BA’s Odyssey

Reflecting on my journey from a Junior Business Analyst to a seasoned Business Analyst and eventually evolving into a role where Business Analysis and Product Management intersect, I’ve had the privilege to contribute to organizations as diverse as Boeing, Rolls-Royce, and EPAM, alongside navigating the unique challenges of smaller entities.

This path, spanning over 13 years and multiple domains, has equipped me with a deep understanding of Business Analysis from the grassroots, teaching me the crucial balance between adhering to frameworks and embracing the agility necessary for today’s dynamic business environment. This narrative is an exploration of that journey, emphasizing the transition from rigid methodologies to agile adaptability, and the critical importance of customer focus and stakeholder management.

 

In the early stages of my career, the allure of frameworks was undeniable. They presented a structured way of understanding Business Analysis and Product Management, offering a semblance of control and predictability in the chaotic realm of project management.

However, as I progressed, the limitations of these frameworks became increasingly apparent. The real-world application of Business Analysis goes beyond the confines of any framework. It demands an acute awareness of the shifting business landscape and the ability to think on one’s feet—a blend of deep analytical thinking and pragmatic street smarts.

 

This evolution in perspective was mirrored in my approach to project management. Initially, my focus was on mastering the technical aspects: understanding the ‘what’ and ‘why’ to navigate towards solutions and create value for users. Yet, I quickly learned that the essence of effective Business Analysis lies in the ability to communicate, adapt, and understand the broader business context—skills that are foundational yet flourish only with experience and deliberate practice.

 

Communication emerged as the cornerstone of my professional development. The capacity to engage with a diverse set of stakeholders—customers, engineers, designers, and executives—and synthesize their insights is paramount. It’s a skill that goes beyond mere articulation; it’s about understanding the audience, choosing the right words, and effectively conveying complex ideas in a manner that resonates.

This skill set has been instrumental in navigating the complexities of projects, ensuring alignment across teams, and driving towards common goals with clarity and purpose.

 

As I embraced the agile methodology, the importance of flexibility became glaringly evident. Agile is not just a buzzword; it’s a mindset that values adaptability, customer-centricity, and continuous improvement.

It challenged me to think differently about project management, to be more iterative in my approach, and to prioritize direct feedback loops with stakeholders and customers. This agility has been crucial in climbing the project ladder, allowing for rapid pivots and adjustments in response to new insights or changing market dynamics.

 

Customer focus and stakeholder management have been the bedrock of my growth as a Business Analyst. Recognizing the criticality of these aspects, I’ve dedicated myself to becoming adept at navigating the complex web of stakeholder relationships and ensuring that the voice of the customer is always at the forefront of decision-making. This has involved honing my ability to manage expectations, articulate value propositions clearly, and foster an environment of trust and collaboration.

 

Advertisement

 

In retrospect, the journey from adhering strictly to frameworks to adopting a more flexible, agile approach has been transformative. It has taught me that while frameworks provide valuable guidance, the essence of Business Analysis and Product Management lies in the ability to adapt, communicate effectively, and maintain a relentless focus on the customer and business objectives.

As I continue to navigate this ever-evolving landscape, these insights will remain central to my approach, guiding my decisions and actions in the pursuit of creating meaningful, impactful solutions.

BATimes_Apr17_2024

4 Tips for Managing Ambiguity as a Business Analyst

As a business analyst, it is common to face ambiguity in many different forms and aspects. It may be the ambiguity of the business analysis approach you have chosen, the requirements, or the design decisions that you have to contribute to.

Ambiguity and constant changes are something that is expected. It’s up to you to respond constructively. The following tips may help:

 

#1- Approve Ambiguity

Although you may want to have full control over the circumstances, it will not happen. It may take time and changes in order to establish a business analysis approach to customers’ needs or understand the full aspects of the system to be developed. It is fine not to have the full picture from the beginning of the analysis journey, but it is your job to progressively clear out the context and the scope. Approve the ambiguity of the intrinsic part of the analysis.

 

#2- Mindset Shift

Ambiguity can cause plenty of negative thoughts and worries. Instead of entering into a negative, endless dialogue, try to view ambiguity as an opportunity for new approaches, for innovation, and for gaining experience. Ambiguity can cause team members frustration and challenges, as the situations triggering it are mostly out of our control. It is important to reframe biassed thinking patterns concerning ambiguity into positive ones.

 

Advertisement

 

#3- Utilizing Effective Risk Response Strategies

As a business analyst, you should cooperate with the project manager to recognize factors and assumptions that can affect the business analysis objectives. You have to understand the sources of the risk and craft alternatives you can use if those risks actually occur. Whether you are a lead business analyst or other team member, your ability to identify and respond to risks effectively will affect the team’s ability to successfully complete project tasks.

#4 – Have a Compass

Having a specific compass for ambiguous situations is essential to guiding your decisions and actions. Orienting yourself and leading your team through a period of ambiguity can be supported by a stable and valuable foundation of personal and organizational vision, mission goals, and objectives. Knowing at any time why you are doing something and what you want to achieve and being true to yourself and your team can guide you as the North Stare in unpredictable and chaotic situations.

 

By viewing ambiguity as an opportunity, you can reduce the stress imposed by an ambiguous situation, experiment with new processes and ideas, and develop your team members. Identifying a goal or value that can be used as a “compass” can contribute to avoiding actions and behaviours you will regret later.

BATimes_Feb02_2024

Crafting a Compelling Business Case: A Practical Guide for Business Analysts

Developing a business case is akin to telling a compelling story—one that captivates your audience and persuades them to invest time, resources, and support in your idea. As a Business Analyst, mastering the art of creating a persuasive business case prior to crunching the numbers and making the pitch is essential for driving successful projects within your organization. Here are eight major points that will help you navigate the intricate landscape of business case development (i.e. “make the case”).

 

  • Basics of Making a Business Case

Let’s kick things off with the foundational principles of constructing a business case. Regardless of the nature of your proposal or the industry you’re in, the process remains surprisingly consistent.

First and foremost, abandon the idea of diving into logical arguments or grappling with intricate numbers right away. Instead, envision yourself as a storyteller, beginning with the identification of a problem or opportunity. Ask yourself: What business need are you trying to address? Once you’ve pinpointed this, it’s time to introduce the characters in your story—stakeholders, beneficiaries, and subject-matter experts.

Stakeholders, often high-ranking decision-makers, hold the power to greenlight or reject your business case. Beneficiaries are those who stand to gain from your proposal, while subject-matter experts provide insights into problem-solving. Collaborate with these individuals to explore various alternatives, considering efficiency, cost-effectiveness, and alignment with your organization’s culture.

Having chosen the best option, create a high-level project plan to estimate the time and resources required. Finally, clearly articulate the value your solution brings, setting the stage for the subsequent number-crunching phase, including ROI, break-even points, payback periods, net present value, and internal rate of return.

 

  • Learn How Your Organization Evaluates Business Cases

Understanding how your organization reviews and approves projects is crucial for tailoring your business case effectively. Answer questions such as: Does your company have a formal evaluation process? Is it connected to other processes, and how detailed do stakeholders want the information?

Leverage the knowledge of a colleague familiar with the evaluation process. In large companies, formal templates and specific review times may exist, often tied to annual budgeting. Some organizations use a “tollgate” process, where approval is sought for project phases, allowing gradual commitment of resources.

Smaller organizations follow a similar pattern, albeit with less structure. Identify decision-makers’ authority levels, and if your organization lacks a defined process, seek insights from successful colleagues who navigated similar challenges.

 

 

  • Know Who’s Calling the Shots

Understanding who holds the fate of your project is paramount. Whether it’s an individual or a small committee, knowing your audience allows you to tailor your case to their priorities. Your boss might have insights into the decision-makers, whether it’s the CFO, division head, or a committee representing various organizational facets.

Identify the dominant department, as their goals often carry significant weight in decision-making. Find a champion within that department or committee who can advocate for your proposal. Remember, the goal isn’t just approval but informed decision-making, even if it means rejection.

Once you know the decision-makers, understand their priorities. Senior leaders look for projects aligning with the company’s strategy, emphasizing the importance of ensuring your case dovetails with broader objectives.

 

  • Understand the Audience’s Objectives

Aligning your business case with your company’s objectives is pivotal. Begin by identifying these objectives through sources like annual reports, CEO letters, and all-staff communications. Grasp the overarching themes—whether it’s growth, cost-cutting, global expansion, or regional focus.

Those evaluating your case are likely responsible for meeting these objectives. Clearly demonstrate how your proposal contributes directly to these goals. Understand the priorities, values, and decision-making styles of stakeholders by engaging with experts from various functions and consulting your boss.

Remember, stakeholders may not always agree on how to achieve company goals, emphasizing the need to involve experts from diverse functions when building your business case.

 

  • Clarify the Need

Before delving into team-building and solution brainstorming, the business need must be crystal clear. Referred to as the “pain point,” it’s the urgent problem or opportunity driving your proposal. It could be a sales force losing bids, service desk requests falling short, or an opportunity for substantial cost savings.

Document the pain point(s) thoroughly, noting the origin, impact, and the solution’s objectives. This documentation serves as the basis for your recommendations, making it easier to present a compelling case to stakeholders later on.

Whether you identify the need yourself or stakeholders present it to you, rigorous research is essential. Document everything, keeping notes on paper or digital files to refer back to when faced with conflicting or partial information.

 

Advertisement

 

  • Build a Cross-Functional Team

Developing a business case is not a solitary endeavor. Relying solely on your perspective risks overlooking crucial aspects. Instead, assemble a cross-functional team comprising individuals from various departments and perspectives.

While you may not have a dedicated team, bring together individuals at different points in the process. Include a finance representative to provide a big-picture view of costs and benefits. Engage beneficiaries to voice their concerns and ensure a holistic problem-solving approach. If the project impacts customers, involve customer-facing representatives like account managers or customer service representatives.

External experts can offer valuable insights, whether sourced from your network, online communities, or vendors. The key is to form a tight team of experts focused on the specific case, respecting the organizational chain of command and securing support from reporting managers.

 

  • Consider Alternatives

The brainstorming phase is where your cross-functional team shines. Encourage the exploration of potential solutions, using problem statements as a starting point. Look beyond individual departments, considering how other organizations or departments might have addressed similar needs.

Emphasize that these sessions are working sessions—opportunities to generate options without delving into detailed project plans or specific vendors. Facilitate creative thinking while reminding the team of limitations and constraints. The goal is to consider all viable options before narrowing down to 2-3 choices.

Thought-provoking questions guide this process. Which option costs the least? Is it the fastest to implement? Does it have the fewest risks or bring in the most revenue? Present each option with at least one significant advantage and be ready to share rejected options and the reasons behind their dismissal.

 

Think Through the High-Level “How”

Paint a vivid picture of how your proposed solution will be implemented within the organization. While not a detailed project plan, this outline provides a realistic basis for estimating costs and benefits. Consider what tasks need to be done before, during, and after the project switch.

Engage subject matter experts and stakeholders in this process. Anticipate potential roadblocks and resource requirements, securing buy-in from involved departments. Validate your proposed solution with your cross-functional team, ensuring feasibility and uncovering any hidden costs or constraints.

This high-level planning stage helps you identify whose support you’ll need and ensures that all costs, including one-time expenses, are accounted for. It sets the stage for detailed financial calculations and further strengthens your business case.

 

Here’s to crafting a compelling case that resonates with stakeholders!

BATimes_Oct11_2023

Best of BATimes: 3 Reasons Why the BA/PM Hybrid Role is So Difficult

There are many variations of the BA Hybrid role, but the Business Analyst/Project Manager hybrid is the most widely discussed.

 

While there may be disagreement on whether there should be a blended BA/PM role and where the two roles differ and overlap, I think we can all agree on one thing: this hybrid role can be very challenging. It is also a hybrid that is gaining popularity as organizations look for ways to become leaner and more flexible. In this article, I will highlight the top three reasons why this hybrid role can be difficult for many and some suggestions to overcome the challenges.

 

1. The BA/PM role requires expertise in both disciplines.

The BA/PM role requires highly developed competencies across both disciplines which require education and experience across both to execute well. The problem is, many organizations, whether intentionally or circumstantially, assume that a good BA can quite naturally take on project management responsibilities and the same goes for PMs being able to take on business analysis tasks. The reality is that while one person could do both, there will most likely be a marked difference in the level at which they execute if they are experienced in one and not the other.

For example, an excellent PM with limited BA experience will likely get the project done but the value delivered may be less than initially expected by the stakeholders. Why? Because project management focuses on delivering the project according to the project requirements, but business analysis looks deeper at the meaning of the requirements and how the solution will be best implemented. A PM who is inexperienced in business analysis may take the requirements as stated by the stakeholders at face value, something that a more experienced BA would look deeper at and inquire more about. A BA with little or no PM experience may produce well-defined requirements but would likely struggle when it comes to managing multiple project constraints because they do not have the experience needed to make professional judgments that will keep the project on track.

 

2. This role only works well with small changes.

The IIBA Competency Model states this concerning hybrid roles, “The dual hybrid role is typically associated with small or less complex work efforts, where it is possible for a single person to perform both roles effectively.” This is true when it comes to the BA/PM hybrid and those performing these roles are certainly aware of this reality. This becomes an issue when an organization is immature in either discipline or is undergoing organizational restructuring. While it may be well understood that smaller is better with this kind of role, when an organization is not mature in performing project management and business analysis, the cost of failure and the loss of value is not easily identified.

When an organization is undergoing organizational realignment, they often take an “all hands on” approach to getting things done, which may leave one person managing large or risky efforts while holding multiple responsibilities. From the outside, it can appear as a great way to maximize resources because no one truly understands the real costs of having one person doing both.

 

Advertisement

 

3. The role may not be well-defined or adequately supported.

Any role that is undefined or poorly defined is likely to cause problems. With the BA/PM role it can be even more evident. Many BA roles already have a lot of presumed tasks that impact the nature of their work. Many PMs have roles loaded with other responsibilities outside of project management. When the two roles are combined into a BA/PM role that is ambiguous and undefined, it can produce a lot of issues, not only for the individual in the role, but also for the organization.

Many times, the BA/PM hybrid role is not even officially acknowledged as a hybrid role and appears out of necessity where the person keeps the same job title but assumes more responsibility in the other domain. These situations can also make it hard to find the right person for the role. It is not enough to simply take two full-time job descriptions and merge them together into a double job description. There must be much thought given to what they will be asked to do and what they will not be asked to do. If this boundary is not created, it will set up the BA/PM to manage their work by urgency only, because there won’t be enough time to do everything they are assigned.

 

Increasing the Odds of Success

To ensure that the BA/PM role is successful, organizations must pay attention to the role and what is needed to increase the odds of success. It is not enough to merely assign additional responsibilities to an existing role. Organizations must take the time to define the role considering the value they expect to receive and the inherent limitations of the role. Once the job is defined, there must be a concerted effort to keep assignments within the size and complexity that will best enable success and have mechanisms in place to measure that.

Additionally, there must be some consideration given to what will be needed to support the BA/PM. Are there other team members who can assist with tasks that would normally be associated with one or the other function? I have been successful in BA/PM hybrid roles where I had an oversight role on the business analysis side and was expected to review and guide the work of other BAs, rather than do everything myself. A successful support structure will also include access to the education, training and mentoring needed to allow those performing the role to sharpen their skills. All of these will increase the odds for success in the BA/PM hybrid role.

Published on: 2017/02/16
BATimes_Jun8_2023

Ode to a Picture

Practically everyone has heard the expression “a picture paints a thousand words”.  In the world of art, a picture can be used to express ideas and evoke emotions, or it can also simply be used to capture on canvas something or someone significant. In the professional world, carpenters and architects rely on drawings to build to precise specifications. In the business analysis world, the whole purpose of creating a picture, otherwise known as a diagram, is to clearly communicate information without using words.

There are many different types of diagrams at our disposal, and I will attempt to name a few key ones here: entity, activity, data flow, sequence, use case, flowchart, system context, workflow, object, component, and UML.  However, the focus here is on what you want to convey to your audience through a diagram and the benefits of doing so, rather than how or which diagram you should use to do so. The point is to emphasize the benefits in the use of diagramming in many situations to communicate meaningful information and transform your business analysis efforts!

 

What a Diagram Can do for You

Diagrams can tell a story from numerous perspectives. For example, they can be used to confirm our understanding of processes, or to define system interfaces. They can illustrate system and network connectivity. They can help to explain complex processes. Diagrams can depict workflow, business processes and system interactions. They can help to define in scope and out of scope features.  They can also help establish or confirm understanding between the business analyst and a stakeholder in a way that verbal or written words sometimes cannot.

Diagrams can help confirm requirements by illustrating what needs to happen in a system or workflow. They can also be used to model database structures and to depict data flow. Diagrams can cut across confusing jargon or long-winded verbal or written explanations and get right to the point in the simplest of terms. When you consider all of the benefits, the power of a diagram is undeniable!

 

Diagrams are Blueprints to the Past, Present and Future

Diagrams can be used as blueprints for past, current or future conditions. For instance, diagrams from the past can help explain why outdated processes or procedures might have come into existence. How many times have you come across the question “why do we do this”? The typical answer of “because we’ve always done it this way” never solves the problem.

If only you could time travel back in time to document a process using a diagram so that in the current day you or anyone else could easily answer any questions about the “why’s” of a process or procedure. Prevent this lapse of information for future questions and diagram your process!

 

Take Time to be in the Present

Although your stakeholders (and you) might be very familiar with the tasks and workflow used with a given process, it is still beneficial to take the time to depict current “as-is” diagrams.   These diagrams are helpful to illustrate current interactions between actors and systems as well as point out manual tasks that might be targets for process or system improvements. Current state/as-is diagrams can also serve as a valuable documentation tool. New employees and auditors alike tend to appreciate the information conveyed in a diagram.

Additionally, going through the process of building out diagrams for current business systems and stakeholder processes can help demonstrate the need for better written procedures. Current state diagrams can also help point to key performance indicators when changes are proposed. For instance, when comparing the proposed future state to the current state, time-consuming manual tasks will hopefully be earmarked for potential elimination. Having these diagrams at your fingertips can make these improvement opportunities stand out, which will make the task of quantifying the time saved or cost savings (or whatever differences) that much easier to document.

 

Advertisement

 

Illuminate the Future

Future state or “to-be” diagrams can help to illuminate the roadmap for upcoming changes, whether that might be a business process, a system component, or a new business system altogether. For instance, they can help define system changes and plan improvements to technical interfaces, thereby avoiding future outages. They can help to confirm our understanding of impending changes to processes and to thereby plan accordingly. They can also help identify the business processes that may become obsolete. Future state diagrams can also help the organization stay focused on the planned and specified changes or help to inform decisions to adjust the plan if necessary.

 

Conclusion

As a business analyst, the diagram has to be one of the strongest tools in the arsenal of BA weapons. There are so many uses and applications where a diagram can transform work efforts. It doesn’t have to be fancy or complex. In fact, the simpler the better. The point is to use a diagram to convey the desired information in as clearly a manner as possible. The benefits of a diagram can be felt across all levels of the organization, communicating across different levels of knowledge and understanding. Diagrams can clarify information for stakeholders and business analysts alike.

They can validate or improve existing understanding and inform future changes. They can serve as documentation for auditors, and training tools for staff. Diagrams can highlight the need for improvements and underline performance improvement indicators.

The uses and benefits go on and on, so hopefully this will inspire you to take a little time in each of your project efforts to paint the picture that will prevail in communicating your message and save yourself a thousand words!