Watermark Learning offers valuable industry articles on timely topics and issues affecting
business analysts and project management professionals. To read any of our articles in their
entirety, you must be logged in as a Watermark Learning Member. Click here to become a member and gain access to our industry articles and other valuable resources
Want pointed and topical blogs on Business Analysis, Project Management, Business Process Management, and Influencing Skills? View our extensive blog section. Or, check out numerous tips.
Articles are tagged with these icons to indicate subject matter, and are organized alphabetically:
Project Management Skills
Business Analysis Skills
Business Process Management Skills
Leadership & Influencing Skills
Interested in using one of these articles on your website or newsletter? Contact us for more information.
2017 Trends in Business Analysis, Project Management, and Agile
by , Richard Larson, PMP, CBAP, PMI-PBA, and Andrea Brockmeier, PMP, CSM, PMI-ACP, PMI-PBA
Agile is Not a Project Management Framework
I have the same thought each time I read an article or attend a workshop on “Agile Project Management.” Agile is not about project management. The title is “Manifesto for Agile Software Development.” The statement is “We are uncovering better ways of developing software by doing it and helping others do it.” Agile is a strategy for executing the product development of a project, not a project framework.
Is The Business Analyst a Product Owner or Tester on Agile Projects?
There have been many articles lately about the role of the BA on Agile projects. Some postulate that the BA role is closest to the product owner. After all, it is often suggested, they reside with and represent the business. They are in the best position to be the final voice when defining and prioritizing requirements. Others believe that the key role for the BA on Agile projects relates to testing. Since they define the requirements, they should complete the appropriate testing processes to ensure the final solution meets the requirements. I believe that neither of these is a business analyst role. That's not to say that someone with the title of BA cannot play other roles as well. It's just that when they are playing these other roles, they are not doing business analysis work.
Is Your Organization Agile Ready?
For years we've been getting questions from Agile seminar participants about how to apply Scrum to "real life." As though these methods are "good in theory, but not at my company!" Some organizations may not be ready to adopt Agile methods completely, so we encourage people to take an organizational readiness self-assessment to see where they are in their Agile growth.
Scrum Vs. Waterfall: A Heavyweight Fight
In Part 1 we began our "fight" by exploring two estimating techniques that are often used on both Scrum and Waterfall projects. The first was relative sizing (one kind of analogous estimating) and the second Delphi (called Planning Poker in Scrum). Scrum won both rounds (barely) because although both techniques can be used on both types of projects, their usage in Scrum seems easier to understand, learn, and apply.
In Part 2, we compare Waterfall to Scrum in a variety of ways—looking at their similarities and differences and implementation of each.
101+ of the Most Effective Questions You Can Ask to Elicit Requirements and Uncover Expectations
When eliciting requirements and uncovering expectations for a project, much of the challenge stems from learning what the business needs from the new product being built. Often times, we may not even know the right questions to ask to get started, much less get into enough depth to discover all the important needs of stakeholders. This handy guide is a summary to help you get started with your questions and to help ensure you've asked the important before and during a project.
BABOK Version 3 vs. Version 2—Taming the New Guide
The IIBA® has produced an important update to its definitive Business Analysis Body of Knowledge, the BABOK® Guide. Released in April 2015, the BABOK Guide includes major upgrades, ranging from the BA Core Concept ModelTM (BACCM), to changes to most Knowledge Areas, the addition of 16 new techniques, and the addition of an all-new section containing five perspectives on Business Analysis.
Constrain Your Way to Better Data Definitions
Whatever the scope or size of a project, it is likely that you'll have to deal with generating new data. This article takes a look at how to define data requirements to ensure the right data is collected and reported.
Data Modeling—Just Don't Show Me Any Crows' Feet!
(Part 1 Data Modeling Overview)
This is the second in our series of requirements modeling. In this article we dive into data modeling, one of the core model types. We start here because data requirements are an important foundation for most information technology projects. If you are a business analyst and not doing data modeling today, you should be able to at least read them to validate requirements against what a data modeler has created.
The Courage to Scribe, Part 1
Many organizations do not understand the importance of scribing and view it as a waste of time. In those organizations there is apt to be pushback about having a separate scribe role in requirements workshops and in spending the time needed to document the results.
The Courage to Scribe, Part 2
In Part 1 I discussed the role of the scribe, how the scribe and facilitator work together, and some of the critical skills that effective scribes need to turn the chaos of random discussions into the structure needed to develop the solution. In Part 2 I will explore why organizations need courageous scribes.
The Courage to Scribe: 42's Trusted Advisor
Recently I saw the movie "42," based on the true story of Jackie Robinson, who in 1947 bravely fought custom, bigotry, and violent hostility to become the first African American to play major league baseball. As I watched the movie, I was equally taken with the story of Robinson's "scribe," Wendell Smith. From the beginning, Smith establishes his role not only as “scribe,” but also as trusted advisor.
Demystifying Use Case Modeling
We all know how difficult it is to achieve project success without complete product requirements. Yet gathering complete requirements without exhausting the project schedule and budget remains elusive on many projects. In this article we will provide tips for gathering hidden requirements quickly.
For people dedicated to the field of business analysis, CBAP® certification is becoming the "gold standard" of the profession. Undoubtedly, many of you are either thinking about becoming certified or have already started the process. This article summarizes the CBAP® program, and how business analysts can create a foolproof plan to obtain their certification. This article provides 7 crucial steps for your plan and several tips on how to execute these steps successfully to become certified.
Gathering Requirements: Go Away Please!
Requirements elicitation requires building relationships and trust among project stakeholders. When trust is absent, the requirements elicitation process will take longer, be incomplete, and lead to lower morale. Although building relationships takes time and effort, it can actually shorten project time and result in improved project performance.
This article was originally published as part of the PMI® Global Congress North America Proceedings, Toronto, Canada.
How CBAP® Helps You Become a Better Consultant
My introduction to business analysis and process improvement was over twenty years ago when, as an electronics engineer in a GE plant, I received training in the Workout™ process improvement methodology. Since then, my knowledge and understanding has steadily increased as I learn how to analyze and improve business processes in the simplest and most sustainable way. When I found the IIBA a couple of years ago, I realized that the skills, experience and knowledge required by a Certified Business Analysis Professional (CBAP®) broadly described the point I had reached in my career.
Kicking The Hornet's Nest
I have kicked a few hornet's nests in my career. Some of these nests were full of angry hornets and some full of non-aggressive bumblebees. However, every instance reinforced the importance of doing the right thing for the organization, even if it meant getting stung.
PMI-PBA® Certification: What It Is and Why We Need It
Many in the industry wonder how the new PMI-PBA® certification will affect IIBA, and its CBAP® and CCBA® certifications. We see all three credentials co-existing and serving different purposes. In this article, we explore the differences and commonalities of these certifications to help you select the certification(s) that are right for you and for your staff.
This article was published in Modern Analyst.
Parallax Effect on Requirements
Have you ever gazed out at the stars and found it too difficult to focus on a particular one? Scientists call this the parallax effect. Too often, the same phenomenon occurs in projects—business analysts tend to focus on too few methods to elicit and analyze requirements.
In this article, we provide strategies to overcoming the parallax effect. We provide techniques you can use immediately to better define requirements so that problems may be solved efficiently.
Projects Without Borders: Gathering Requirements on a Multicultural Project
One of the most difficult tasks project managers and business analysts face is obtaining customer requirements. When the project includes multi-cultural stakeholders, particularly if they comprise a virtual team working in geographically dispersed areas, the job becomes much harder. As the world gets "flatter" and the need for collaboration beyond political borders becomes the norm, the ability for project professionals to bridge cultural gaps will become a necessary skill set. This article provides tips and techniques for project teams to do just that.
I’ve been helping people obtain their CBAP® since 2007, and I’ve seen a number of approaches. Most have been successful I’m happy to say. A few others have not been, either because candidates stressed out or were underprepared. The individuals were understandably disappointed. This article is a summary of the top mistakes people have made in working towards their CBAP® or CCBA®, including my own experience with the CBAP® and PMP®..
Using Storyboards to Get the Big Picture
A shortcoming of written requirements in any format (user stories, use cases, SRS, etc.) is that it is often difficult to visualize the process described or proposed by the requirements. This article details how to use storyboards to better define requirements and processes for more effective project flow.
Why Don't Use Cases Just Go Away? Part 1: Use Case Diagrams
Use case models have been around for decades. Long after Information Engineering was all the rage and through object-oriented analysis and design they hung around. They threatened to disappear when Agile methods gained popularity, but here they are. Discussed, dissected, blogged about—why don’t they just go away?!
I Don't Have Time to Manage Requirements — My Project is Late Already!
Lack of a well-managed requirements process leads to common project issues, such as scope creep, cost overruns, and products that are not used. Yet many projects skim over this important part of the project and teams rush to design and build the end product. After all, some of our sponsors think that "we're not productive unless we're building the product."
This article addresses concerns and provides an overview of the essential skills that are needed today to manage customer requirements, emphasizing the relationship between requirements management and project management. It focuses on a core set of processes for ensuring that the entire requirements process is managed, that requirements are gathered and documented, and that customers get a business solution that really works for them.
This article was originally published as part of the PMI® Global Congress Europe-Middle East-Africa Proceedings, St. Julians, Malta.
Life Cycles and Requirements Approaches
The following is an excerpt from the book Practitioner's Guide to Requirements Management, written by the authors.
Much has been written over the years about systems development life cycles, methodologies and approaches. Why write one more article on the subject, you may ask? When travelling around the world doing training, mentoring, and speaking on business analysis and project management, we encounter a huge variation in understanding of these important concepts. Here is our condensation of the topic that we hope clarifies some of the topics.
Requirements Management 101
The following is an excerpt from the book Practitioner's Guide to Requirements Management, written by the authors.
Requirements management, like project management, is a discipline comprised of inputs and outputs, tools, and techniques, processes and activities, but just for business analysis activities. Requirements management includes the planning, monitoring, analyzing, communicating, and managing of those requirements. This article gives you a quick refresher on this important topic and the components of a good requirement.
Requirements Modeling: Time Waster or Time Saver?
How often do we hear “We don't have time for analysis—let's just get the project done!” Or “Modeling is the developer's job. Yours is to get the requirements.” Or “We're doing Agile. Requirements evolve, so let's not waste time with use cases or process models.” We have often heard every argument under the sun why spending time modeling requirements wastes time. However, we believe that modeling actually saves time.
Seven Success Factors for Requirements Planning
If care isn't given to planning the activities of defining product requirements, the entire project could go awry. It is one of the biggest reasons why 60% of project defects are due to requirements and almost half of the project budget is spent reworking requirements defects. There are many success factors that can relate to projects, products, and processes. Some apply to all three...
Business Process Improvement: Which Approach is Best for Your Organization?
Six Sigma, The Theory of Constraints, Lean, The Toyota Production System, Process Based Management, Business Process Management, Customer Focused Improvement, Value Added, Kaizen, Taylor, Deming, Welch,...which one do you follow? This article peels back the mystery and addresses the all-important question: how do you choose the right approach to attack the business problems you face today?
No Matter What You Call It, It's Still About Managing Processes
What is being addressed today as Business Process Management (BPM) has gone under the guise of many things over the years. It was known as just-in-time manufacturing in the 1980s. In the 90s it was repackaged as re-engineering, then as Lean, Six Sigma and Value Stream Mapping. While all of these methodologies tend to focus on vertical, or functional process improvements, today’s BPM is about looking at organizations horizontally to improve the whole. It is about delivering well-orchestrated value to customers, and efficiency and profitability to the organization. When the whole business is in sync, both customer and stakeholder value is maximized.
To Understand Business Processes, Just Use Your Loaf
Many recruiters call for specific domain experience when they want help in process redesign. But, whether your product is life insurance, cakes or motorbikes, the principles of business process are the same: you want a defined output from a set of inputs, and you want that output to be provided at consistent time, cost and quality. To do that, you need a designed and managed process.
Avoiding Conflict Between the PM and BA, Part I
What are the roles of the Project Manager (PM) and the Business Analyst (BA) in the early stages of a project? The two bodies of knowledge, the BABOK® Guide 2.0 and PMBOK® Guide-Fourth Edition each allude to work being done at the beginning of the project so it is not surprising that conflict between these two roles can arise.
This article details how to avoid conflict between the PM and BA to ensure a successful project outcome.
Avoiding Conflict Between the PM and BA, Part II
What are the roles of the Project Manager (PM) and the Business Analyst (BA) in the early stages of a project? In part 2 of this article, Elizabeth provides some great advice on how project managers and business analysts can work more efficiently and effectively.
Barriers to Influencing
By, and , Co-Principals, Watermark Learning, Inc.
In our article, "The Influencing Formula," we discussed our concept of the "formula" to help become influential. There are three main components, namely trust, preparation, and courage. A formula sounds as if it may be an easy thing, but of course it is not. We also know that we should do the right thing for our projects, our business units, and our organization. So what's stopping us?
Be Satisfied With What I Give You–It's Better Than What You Asked For
My husband and I usually stay in hotels on vacation and sometimes our expectations, those unspecified requirements, are not met. This article deals with two aspects of unmet expectations: unwanted features and making changes.
Creating Bulletproof Business Cases
Too often we've heard people tell us that their projects, which are intended to help the business solve its problems, continue to cause "pain" or fail to address the issues they were designed to solve. Projects are often justified or initiated by the need for a solution, and this usually means either no business case was created or an insufficient business case was created. Inadequate or non-existent business cases can result in unclear project scope. Building a "bulletproof" business case helps ensure that your project moves along smoothly and solves the problems that it was intended to solve.
There are many different types of 'intelligence'. Components of intelligence can include such things as: understanding, learning, use of language, creativity, emotion, etc. Today, the focus seems to be on cultural intelligence. In this article we look at how being more culturally aware and courteous can enhance productivity and build relationships.
Gather Trust Then Requirements
This article shows practical ways of building trust between project teams and stakeholders in order to achieve better project success.
The Influencing Formula
by, and , Co-Principals, Watermark Learning, Inc.
We often get asked, "How can we get stakeholders to attend our meetings?" or "How can we get stakeholders' buy-in on the project?" These are complex questions, and the simple answer is that we can’t. As business analysts (BAs) and project managers (PMs) we can’t get anyone to do anything, but we can certainly influence them so that they want to. Similarly, we hear other BAs complaining that they are given a solution and don’t believe that they can step back and take the time to understand the business need. We're told, "I can't speak up when my sponsor sets the direction of the project" or "In our organization, they shoot the messenger." How can we effectively influence when we have no authority to do so?
Influencing Without Authority: Rev Up Your Internal Consulting Skills: Part 1 (Why Don't We Have More influence)
How often have you met with business clients to plan a project or elicit their requirements only to have them provide you with their solution? And because they have already given their solution, they can't understand why you want to spend any time shaping the product or defining their requirements! Or, perhaps your sponsor or business clients are at the opposite end of the spectrum. They may be overly busy, stressed-out, and distracted, and again don't have time to define their real needs, or to articulate their detailed requirements.
This two-part article addresses these common quandaries by making a case for a consultative approach to better provide internal clients what they truly need and want. The framework is straightforward, yet reduces the amount of time you hear these dreaded words from clients: "Oh, darn, you gave me what I asked for!" It offers tips on how to respectfully question key stakeholders about their real needs and provides recommendations that best meet their business objectives. All in all, the benefits of this approach are to reduce the amount of rework on projects, improving client satisfaction, and saving time and money.
Influencing Without Authority: Rev Up Your Internal Consulting Skills: Part 2 (Overcome the Barriers—Start Influencing!)
In part 1 of this article, we explored several barriers that prevent project professionals—Project Managers and Business Analysts—from influencing without having the authority. We listed four main factors that we've seen and exist in virtually every organization: lack of positional authority, lack of sponsor support, unclear roles and responsibilities, and other factors such as company culture, product complexity, time pressures, etc.
Now we're ready to explore some ways that help overcome these barriers. They revolve around the theme of project professionals acting as consultants, whether you are an internal or external one. We both worked as internal consultants early in our careers. It taught us the value and power that comes from a consultative approach. Your clients will thank you for using it because it helps solve business problems and get things done.
Is There a Personality Profile for the PM and BA
Are there certain personality traits that Project Managers (PM) and Business Analysts (BA) share? During a presentation on the topic of BA and PM roles, we were asked this question. In this article we share some of the audience responses and delve into each of these traits in more detail.
It's Not Like Selling Pots or Pans... Or is It? A New Way of Selling Project Management to Senior Management
Project management professionals often find themselves in situations where they have to sell things to decision makers. It might be selling a project, or a new function such as Project Management Office. By understanding critical success factors, sales "knowledge areas," and a repeatable process, we increase our chances of success.
This article was originally published as part of the PMI® Global Congress Asia Pacific Proceedings, Bangkok, Thailand.
Oh No, You Gave Me What I Asked For!
Project professionals—specifically project managers and business analysts—realize that no matter how well projects are executed, projects still fail when customer requirements are not clearly defined and customer expectations are not met.
Tips and Tricks for Facilitating Conflict Resolution
We all know that conflict is a difference of opinion and therefore neutral—neither good nor bad, Right? But try telling that to a project manager or business analyst embroiled in conflict. Conflict can threaten to destroy the team and sabotage efforts to elicit requirements. But it doesn't have to. Having a strong, neutral facilitator and a process for conflict resolution can reduce tensions and bring about a positive outcome.
Virtual World Communications
Cell phones, laptops, PDAs...these devices have distracted, disrupted or otherwise negated the impact of meetings and interfered with work focus. This article discusses some relevant research about technology and its impact on communication and productivity.
This article provides 5 rules for successful projects, based on Kids' Rules of World Cup Soccer.
10 Critical Steps to Creating a Project Plan
One of the critical factors for project success is having a well-developed project plan. This article provides a 10-step approach for how to create an effective project plan. It also provides a roadmap for project managers to follow and explores why it should be the project manager's primary communications and control tool throughout the project.
We're proud to note: This article continues to be the most viewed article on the Project Times website, with more than 818,000 views as of May 2016!
Achieve Project Success with Sponsorship and Clear Vision
Here is a brief article that identifies five major factors leading to project success.
Assumptions are Project Killers
Assumptions are project killers, however they are a necessary evil. In this article I will explore several areas where assumptions can be problematic and look at how we can approach assumptions differently. Specifically I address the utilization and impact of assumptions, risk of assumptions, assumption ratings, monitoring and performance.
Foundational Concepts for Project Management and Business Analysis
We use certain terms every day without thinking of their meaning, or perhaps use them with an incomplete or even incorrect understanding. This month we invite you to take a moment to clarify some basic concepts of business analysis and project management. This article looks at some foundational terms and their distinctions. You may be surprised by what you learn.
Managing Small Projects: The Critical Steps
If you think that executing a small project does not require advance planning, think again. This article endorses the planning process and outlines five important steps for successfully managing small projects.
Top 5 Causes of Scope Creep...and What to do About Them
Scope creep is a dreaded thing that can happen on any project, and it can waste money, decrease satisfaction, and not provide the expected project value. Most projects seem to suffer from it, and both project teams and stakeholders are consistently frustrated by it. Why does an effective means of controlling scope seem to continually elude us?