Imagine your first few months as a business analyst being the most educational. You get all the training in required tools, techniques, and a great mentor holding your hand as you navigate through the challenges. You know exactly why certain stakeholders behave the way they do, you know exactly when to stop conducting your analysis and validate your work, and you are becoming an adept and polished BA. Well, unfortunately, for the most part, imagination is where it stays.
What if someone could hand you down 10 things that every BA must know just before they start their career?
That is what precisely this episode was produced to do. In this episode, I interview Howard Podeswa, who will talk through 10ish things that every BA must know before they start their career.
Howard Podeswa is the author of two popular BA books, The Business Analyst Handbook, and UML For IT Business Analysts. He is also a Trainer, and a prolific Artist. I had the good fortune of meeting Howard a few times, and also got an opportunity to visit one of his art exhibitions. He has been a great mentor and friend. You will find links to see samples of his artwork below in the links sections.
This episode is an extension of a question that Julian Sammy had asked him during one of the IIBA® Webinars: “What are the most important things you wish you had known when you were starting out as a BA?”. Howard shares some amazing insights, and valuable words of wisdom. This can apply to all business analysts who are at the starting point of their careers, and a great reminder for senior BAs.
Here is Howard giving out 10ish very valuable lessons:
Here is a Sneak Peek of The Episode:
- The introduction of BA role and how it impacted Howard’s work.
- His recommendation of this role to anyone with an analytical and people side to them.
- Discussion around knowing the history of the project, and why it is important.
- Why you should not hide in a corner as business analyst.
- The importance of finding out who has the signing authority on requirements.
- The value in focussing on what to achieve, rather than the procedure to achieve it.
- Why listening is the most important element while conducting interviews.
- Small demo projects, and why he is a big advocate for this.
- The power of iterations even in an SDLC model.
- Discussion around being your own PM, and time budgeting.
- Relationship between movies, storyboarding, and requirements elicitation.
Insightful Quotes From This Episode:
“I recommend this to anybody whos got an analytical and people side, its really a left brain right brain thing…”
“There is always a hidden agenda… a good BA has their nose upto it…”
“You have to know it and you need to know it, because you are walking into a minefield as a BA…”
“Don’t go out on your own for too long…”
“They trust you with the job and you will do what it takes to get the job done…”
“Don’t hide in a corner…Get help when you need it…”
“It is very very important to find out who that person is…”
“If there was a pet thing that they wanted to see in there, they can shoot you down over that.”
“What is the process going to be and who are the people behind it. (for the sign-off).”
“The personal connections that you make at the job are really a big part of the job, and they make your job really easy.”
“They had to throw out all the detailed requirements once the solution had changed (problem of solutionizing requirements)”
“I don’t care what the button is, but what are you achieving by pressing that button?”
“They already know whats wrong with the process, and they already have great ideas about what to do next… What they need is someone to coordinate this… because everybody knows a little piece… you just need to pull small pieces together. Your job is to pull together the knowledge that is already out there.”
“You can miss the tiniest little cue from somebody, that there are political issues, conflicts, or the hidden agenda… you’ve missed that if you are thinking about the solution right away.”
“Don’t think solution! Really focus on reading everything – body language, things said, things not said – from the person you are talking to; this is extremely important”
“Test your assumptions as early as possible in order to mitigate risk…”
Items Mentioned in The Show:
- Noble Inc. Howard’s Training Company
- Links for his books: The Business Analyst Handbook, UML For IT Business Analysts.
- Howard’s Personal Website (You can see a few samples of his art)
- Link to an article about his art show in September.
Howard Podeswa in Brief:
Howard Podeswa is the co-founder of Noble Inc., a business analysis training and consulting company. He has 29 years of experience in many aspects of the software industry, beginning as a developer for Atomic Energy of Canada Ltd. and continuing as systems analyst, business analyst, consultant, and author of courseware and books for business analysts, including UML for the IT Business Analyst. Directly, and through his company, he has provided training and consulting services to a diverse client base covering a broad range of industry sectors, including health care, defense, energy, government, and banking and financial institutions. Podeswa has developed BA training programs for numerous colleges, universities, and corporate education centres. He has been a subject matter expert in Business Analysis for NITAS—a BA apprenticeship program for CompTIA—and a contributing reviewer for the IIBA’s Business Analysis Body of Knowledge (BABOK®).
If you have any comments or questions for this episode, please post them below.
Enjoy the show and don’t forget to spread the word about this awesome episode using the social sharing links.