Top Posts & Pages
Join 2,897 other subscribers
formerly of Professional Project Services, LCC
Announcing the release of Leveraging Business Analysis for Project Success, a new book by Vicki James, PMP, CBAP, PMI-PBA.
Only 39% of project today are successful. Nearly half of the projects that fail, fail because of “poor requirements management” (PMI 2014). Leveraging Business Analysis for Project Success explores the role of the business analyst in setting a project up for success. It informs and educates project managers, sponsors, and organization leaders on what is necessary for project success. It goes beyond requirements management in exploring the how the business analyst can contribute to increased profitability through project selection, scope definition, and post-implementation evaluation. The reader will learn about the history of business analysis, professional organizations and resources to support the profession, and what to expect from the business analyst at each phase of the project lifecycle as presented in a case study throughout the text. Project leaders will better be able to support the business analysis needs of the project by understanding the skills, expertise, tasks, resources, and time needed to do business analysis right and maximize the return on investment for each project.
Leveraging Business Analysis for Project Success is available on electronic or print format on Amazon or directly from the publisher, Business Expert Press. Educators may request an evaluation copy through the publisher website.
Please contact Vicki at email@example.com if you would like more information regarding this publication.
I have noticed trend developing recently that I find troubling. It started when I participated in the public review of the draft A Guide to the Business Analysis Body Knowledge (BABOK® Guide) version 3 this past May. My biggest concern with this draft was the addition of tools and techniques. The number of tools and techniques went from 34 to 46, but even more troubling was that I did not recognize some of the added tools and techniques including Business Model Canvas or Business Capability Analysis. Not only that, I did not see where they were common and useful enough to add to a collection of generally accepted best practices separate from the 34 that were already there. Aspiring CBAP’s® and CCBA’s® will need to thoroughly understand each of these in order to prepare for the certification exams.
Then in May 2014, the Project Management Institute (PMI®) introduced the PMI Professional in Business Analysis (PMI-PBA℠) credential. The PMI-PBA Examination Content Outlines specifically calls out 76 techniques in 22 different categories. Add their newly released Business Analysis for Practitioners – A Practice Guide with an additional 10 techniques and business analysts who are availing themselves to certification need to learn a whopping 86 business analysis tools and techniques in order to prepare for any question the PMI-PBA℠ examination may throw at them. WOW!!!
Many of these new techniques, while great in concept, are not actually in the collective consciousness of the business analysis community as a generally accepted best practice tool or technique. With things such as Kano model, Ecosystem Map, and Interrelationship Diagram it all gets very confusing very fast. Even for a seasoned pro like me.
I think part of the problem is that the terms tool and technique is not being used as I would expect. A technique is a method (procedure, formula, or routine) to accomplish a task. A tool is a device that will aid in completion of the task. Business analysts will often have the tools and techniques to accomplish a task without adding to the toolkit or the vocabulary. Fore example, business capability analysis is a task that skilled, seasoned business analysts can accomplish without adding to the toolkit.
Is a carpenter with 86 tools in his tool belt any better than a carpenter with 34 tools? Perhaps, but not because of the number of tools he holds.
Instead, I would apply the Pareto Principle (aka 80/20 Rule) and say that 80% of the value comes from 20% of the tools. This 20%, or approximately 17 tools, are the core basics that any business analyst should have in his or her tool belt. The business analyst should not just have theses tools, but make sure that these tools are of the highest quality and grade. A business analyst should further be armed with the competency to research and find, or develop his or her own tools that will make the job easier and provide greater value to the project if, and only if, the existing tools are not quite fitting the need.
You are probably now wondering what 17 tools and techniques I would consider the core basic. Well let me take a stab at this.
So there you go. Vicki’s 17 Core Business Analysis Tools and Techniques. Couple these with great organizational skills, an inquiring mind, along with the ability to adapt, and you have a top-notch business analyst who will help your project and your organization achieve great things. Let’s spend the time we would otherwise use in learning about the other 59 tools to refining and perfecting these 17 and adapt from there as needed.
What tools and techniques do you feel are most essential for a business analyst?
I realize that it seems as if I have given up writing by the looks of my blog page. I assure you this is not the case. I have written extensively for Watermark Learning about things such as the new PMI-PBA credential from the Project Management Institute and the public review draft of the BABOK© Guide v3 from International Institute of Business Analysis. I even have a guest spot up on Business Analysis Times with a re-print of my popular The Project Manager vs. The Business Analyst post.
Here are a few titles for you to check out. Follow the link at the top of the page to “Become a member of our learning community” to get Watermark Learning news first hand.
It has now been a month since the International Public Review of A Guide to the Business Analysis Body of Knowledge® (BABOK®) Guide v3 began. I have had a chance to do a bit of review firsthand and wanted to share some findings. BABOK … Continue reading →
The Project Management Institute (PMI) launched the pilot of the PMI Professional in Business Analysis (PMI-PBA) certification last week. The pilot continues through August 4, 2014. The PMI has provided a couple of incentives for participating in the pilot. Education hours … Continue reading →
A Sneak Peek at the BABOK Guide v3
The IIBA has announced “the International Public Review of A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide) v3” begins May 12th. I had an opportunity to get more news on the release at the Minneapolis-St Paul IIBA … Continue reading →
PMI-PBA and CBAP/CCBA Side by Side
Last week the Project Management Institute (PMI) ® announced their PMI Professional in Business Analysis (PMI-PBA) certification. They cite a statistic by the US Bureau of Labor Statistics that “business analysis jobs are predicted to increase by 22 percent by 2020.” The …Continue reading →
Three Reasons to Achieve Your IIBA Certification in 2014
Is achieving IIBA® Certification on your bucket list? The International Institute of Business Analysis (IIBA) announced at the Building Business Capability conference in Las Vegas last November that the current version of the Guide to the Business Analysis Body of … Continue reading →
I will be posting more on this blog as I have thoughts and contents that do not directly align with the Watermark Learning business…oh, and time! So stay tuned!!!
This is the third and final installment of the So You Want to be a Business Analyst…Or Perhaps You Already Are series. Part One discusses the role of a business analyst with Part Two focusing on a better understanding of when you play both roles and determining where you may lean given your capacity and skills. In this third part will explore how to pursue your career as a business analyst.
You are what you do and not your job title. If you do business analysis then you are a business analyst. Maybe your job title is project manager, technical writer, program manager, product consultant. It does not matter. My first six-years in the project world I held the working title of “product manager” and job classification of “state financial consultant”. You will find this work listed as “business analyst/product manager” on my résumé and LinkedIn profile. “Business analyst” is industry standard for the work done and provides a commonality across organizations.
Repeat after me. “I am a business analyst, I am a business analyst…”
What does your résumé say about you and the jobs you have held? Give your résumé a hard look and find those tasks and deliverables that you have listed that fit under the category of ‘analysis’. Try this – type the word “analysis” in Word and then right-click to view synonyms. Let me help you out with a picture of the results I get. Use these words as a guide in reviewing your résumé.
Take this a step further. What missing from your résumé? Think about the work you have done and what you can add that lends weight to this aspect of your experience. I have provided further guidance on documenting your experience in my article, Document Your Project History.
Remember to update your LinkedIn profile as well. Use the Skills section of the profile to highlight this experience and ask connections to “endorse” these skills.
Nothing speaks more to your professional aspirations and commitment then involvement in a professional organization. Not only does it look good for you, but you gain the benefit of a network of peers in comparable roles to learn from and share experiences with. There are varying levels of involvement and added benefits come from each.
At this level you will have access to an electronic copy of A Guide to the Business Analysis Body of Knowledge (BABOK®), a subscription to The Connection newsletter, and a wealth of resources online including articles, discussion groups, webinars, and tools.
Meetings and workshop will increase your exposure to best practices and make sure continued education in business analysis topics. This further demonstrates your commitment to the profession as well as your own professional development. You will also build your local network of business analysts that can help you through struggles you have on the job in your next career move.
Volunteering is hugely fulfilling and beneficial to your career. It takes you from to the next level as far as demonstrating your passion for business analysis as a profession. It provides opportunity to show your work to other business analysts and build a reputation as a professional. Those who volunteer for my Chapter will find a ready referral and reference from me as they pursue future opportunities. This may be volunteering on a committee, with a specific task, for a project, or as a board member. Volunteer positions tend to be what you make of them and a lot can be accomplished in a few short hours a month.
Don’t forget to put your volunteer activities on your résumé and LinkedIn profile.
The time, effort, and money you put into the certification process exhibits your commitment to being a business analyst professional. You must prove earlier experience to sit for the exams. You must learn, keep, and prove you have a significant amount of knowledge on business analysis best practices from Enterprise Analysis to Solution Verification to pass the exam. Apply what you know in the real world and this step will take you far.
I hope this series has provided some helpful information as you pursue your career in business analysis. Please feel free to contact me (firstname.lastname@example.org) for more information or guidance. Follow this blog to get receive alerts of future posts that will be of interest to you.
So You Want to be a Business Analyst…Or Perhaps You Already Are
Last week I posted Part 1 with discussion on what a business analyst is. You may be more confused than before on what it is you are. I will quickly clarify a few points by addressing a couple of common questions.
Question 1: I am a project manager that is responsible for business analysis on my project. Is this wrong?
Answer: It depends on the project and the situation. If it is a small project with a small team and you are familiar with the business then it may make sense. The test is if you are effectively and efficiently juggling managing the project (planning, tracking, risks, stakeholder management, etc.) with the business analysis tasks (eliciting requirements, creating models and documentation, working with stakeholder to prioritize, translating for the technical team, etc.). However, if you are not able to manage both roles effectively within a normal workweek it means you are working two full-times jobs, rather than two half-time jobs. Getting a BA on your project will allow you to focus on one job and lead the project, project team, and influence stakeholders much more easily.
Question 2: I have worn many hats on my projects. How do I know if I am a business analyst?
Answer: The answer lies in where you natural aptitude and desire are. Answer the three following three questions to help you find the answer. (Disclaimer: this is not a scientific aptitude/skills test)
1) When it comes to solving a problem, I tend to want…
2) When I waiting for service in a long, slow line I tend to…
3) When told to do something that I do not quite understand I respond by…
Here are the results to this three-question assessment. If you scored mostly
You may truly have a mix of aptitude and preference of these roles. That is okay. However, you need to define your role for each project and stick to it. This allows you to focus on your responsibility and give the autonomy to others on the team that they have earned and deserve.
Continue to Part 3 for steps on making the shift from someone who does business analysis tasks to a business analysis professional.
Image courtesy of chanpipat / FreeDigitalPhotos.net
As the Seattle Chapter President of the International Institute of Business Analysis (IIBA®), I often get questions about how someone can learn more about becoming a business analyst. Often times those asking have been doing business analysis work realizing it for some time; only they have not yet realized it. This three-part series is to help you understand what business analysis is (part 1), how to know if you are a business analyst at heart (part 2), and offer the first steps to advancing your career as a business analysis professional (part 3).
I will start with the definition of Business Analysis. The IIBA® defines this as
Business analysis is the set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure, policies, and operations of an organization, and to recommend solutions that enable to the organization to achieve its goals (Business Analysis Body of Knowledge [BABOK®] Guide, Version 2.0 Page 3)
The following two lists offer some more context to “tasks and techniques” by listing tools used and items developed and delivered by the business analyst as documented in the BABOK®.
These lists show that many roles do business analysis activities and deliver business analyst results. Some common project roles include data analyst, project manager, technical writer, and developer. Many people do “business analysis.” So what is a business analysis professional?
The project manager, developer, and data analyst may use some tools and deliver some of the same results as the BA as it relates to their specific role. A business analysis professional works with all the business analysis tools and techniques to deliver work that supports defining, managing, and evaluation the solution or resulting product (“to recommend solutions that enable to the organization to achieve its goals”.) The project manager, data analyst, technical writer, or developer rely on the work of the business analysis to provide clarity on the solution and allow project work to focus on steps needed to most efficiently deliver the desired result. The business analyst is responsible for defining is what will bring value to the business, ensuring the requirements are fully vetted and understood, and that the solution meets these expectations. This allows the project manager for focus on the project process, progress, team, risks, and all those other aspects that make project management a full-time job. Read more on this in The Project Manager vs. the Business Analyst. Further, the business analyst frees the technical people up to design and build the solution to meet the need the first time.
You likely play a combination of roles if you are reading this article. Next week we will discuss how to know what you are when you wear multiple hats.
Find out if you are a BA at heart in Part 2.
Image courtesy of chanpipat / FreeDigitalPhotos.net
The role of business analyst falls under many job descriptions. I talk to people all time that are business analysts, only they don’t know it. Maybe the have the job title of “technical writer” or “program manager”, but in reality, they are analyzing the business. Here are some signs you might be a business analyst..
Do you want to join in the conversation? Visit the Business Analysis Times LinkedIn group!
Last weekend I attended the Cirque Du Soleil show, Amaluna. While most of the audience was mesmerized by the beauty and awesomeness of the feats, I was mesmerized by the demonstration of what great teamwork can accomplish. Here is a quick run-down of my observations on the benefits of great teamwork.
The troupe is truly putting their lives in each other’s hands. With high-flying acrobatics and water stunts, the impact of something going wrong can truly be life threatening. It takes a huge amount of confidence to entrust your life into your co-workers hands, but the results are astounding. When thinking of who needs to trust whom, it goes beyond other performers who are putting their safety at risk, but also the engineers and riggers.
What could you accomplish in your current project if you had that much faith and trust in your teammates? Would the project have better flow and less resistance? Do you give your teammates the trust they deserve? We are each experts in our own rights of our own domain. Trust in that and keep conversations on using the various areas of expertise to achieving the goals of the project. Identify underlying issues to deal with the root cause to address team members you believe not to be trustworthy.
Don’t think for a second that every show goes off without a hitch. I saw a couple of “slips” (some obvious, others not) and am sure I missed many more. What keeps the show amazing is the graceful recovery. The most obvious slip I noticed, the performer just kept going and tried again. She succeeded and the audience was amazed. Other slips were covered by their team performers adjusting their movements to minimize the impact on the show, the performers, and keep the show entertaining for the crowd.
We often experience slips in projects. Maybe there is a slip in schedule, defects in code, or risks that turn into issues. It is okay. Our project plans help us decide the graceful recovery in advance. There may be an unforeseen issue that affects the project. The issue is what is it is. Focus on the graceful recovery in support of the project. Refer to point number one and trust that your teammates will contribute to the graceful recovery.
Here is a quick side note. The music in Amaluna was live. It would be very difficult to recovery gracefully if reliant on a soundtrack that prevented needed corrections.
Bad things happen when you are not trustworthy. A performer in Amaluna would not feel safe to give a 100% on feat where their safety was in my hands and I’m not trustworthy. I may lose opportunities to perform. The show would lose a great deal of awesomeness with the troupe not trusting in each other to give 100%. Signing up to perform a feat that one is not ready for, performing when physically compromised, or not being reliable in showing up for rehearsal could destroy valuable trust and compromise the show.
Are you trustworthy when it comes to your projects? Do you make meetings on time, participate fairly, complete assignments as agreed? Do you refrain from gossip, always give honest status on the project, and help your teammate recover from their slips? The person who can do this with integrity, consistently will be a very important contributor to the project. Only when all teammates, including yourself, are trustworthy will you have the level of trust needed to pull off amazing acts. It is the rare project that is delivered on time, on budget, and with promised scope that brings value to the business…a truly amazing feat.
Here is a short promo video of Amaluna to amaze you. A fourth secret follows.
A fourth observation? Yes, risk management. Telling you this is admitting to what a nerd I truly am. The video shows the scene with the contortionist in the water splashing all around. My mind realized that water on stage could be deadly to those that follow her act. Brilliant risk management is at work here.
Four strategies to mitigate the risk of water on the stage endangering the performers.
Please share your stories and thoughts on what makes for amazing teamwork.Photo by Cirque du Soleil at http://www.cirquedusoleil.com/en/shows/amaluna/default.aspx
How often have you been called upon to remember past projects? Are you prepared to respond to “tell me about your favorite project and why it was your favorite”? If you are pursuing professional certification, a new job, or promotion, be ready for this question. If your brain is like mine, it is an overflowing file cabinet with some of the best material buried in the back corner. It is not always easy to access the things you have done in the past, especially when new projects are always sitting on the forefront of the mind. As a result, you will likely shortchange yourself by relying on the more accessible recent experiences that may be less relevant in the context of the position. Perhaps you come up short on needed hours experience for that professional certification because you had forgotten about that part time project you worked on when in a different position. There is a remedy for this. That is your Project Portfolio History.
I created my Project Portfolio History when applying from Professional Project Manager Certification from the Project Management Institute. It was a necessary step for completing the application, but I quickly saw a multitude of uses for this listing. The list includes:
Customize your Project Portfolio History to meet your specific needs. You may add a column for percentage of work time spent on the project, the project sponsor, team members, project methodology…whatever makes sense to you. This is your reference and a supplement to your resume, not a replacement. You may opt to share with recruiters in which case it might make sense to keep a “private” version in addition to the “public” version with the private including key words or signals that you want to remember without sharing. My private version has notes to remind me of my favorite projects, least favorite projects, projects where I learned the most, and many of those other common asks when discussing your project past.
The project description should help describe each project and what made each unique. What technologies and methodologies where used? What was the team structure? Who were the users of the solution and how the accessed it? You do not need to answer each of these questions – rather you are looking for what about this project sets it apart from others.
This document has helped me in describing experience in resumes, cover letters, and in interviews, as well as document hours for both the PMP and the Certified Business Analyst Professional (CBAP®) certification. I use it when customizing my resume to the job I am submitting for, developing my cover letter, review prior to an interview for a fresh look, and I even request to keep the document out and handy during an interview. I have yet to be refused to have my “cheat sheet” handy. Recruiters and interviewers have requested a copy. Remember to have a public version available. One recruiter I worked with said, “This is great! Every project professional should have this.” Start putting your together today. I have linked a Project Portfolio History template so you can get started on yours today. Start with your current project and work backwards. You can always add rows to fill in gaps if you miss something along the way.
Please share your experiences with this or a similar document by commenting on this post.