TopPodcast.com
Menu
  • Home
  • Top Charts
  • Top Networks
  • Top Apps
  • Top Independents
  • Top Podfluencers
  • Top Picks
    • Top Business Podcasts
    • Top True Crime Podcasts
    • Top Finance Podcasts
    • Top Comedy Podcasts
    • Top Music Podcasts
    • Top Womens Podcasts
    • Top Kids Podcasts
    • Top Sports Podcasts
    • Top News Podcasts
    • Top Tech Podcasts
    • Top Crypto Podcasts
    • Top Entrepreneurial Podcasts
    • Top Fantasy Sports Podcasts
    • Top Political Podcasts
    • Top Science Podcasts
    • Top Self Help Podcasts
    • Top Sports Betting Podcasts
    • Top Stocks Podcasts
  • Podcast News
  • About Us
  • Podcast Advertising
  • Contact
Not in our directory?
Add Show Here
Podcast Equipment
Center

toppodcastlogoOur TOPPODCAST Picks

  • Comedy
  • Crypto
  • Sports
  • News
  • Politics
  • True Crime
  • Business
  • Finance

Follow Us

toppodcastlogoStay Connected

    View Top 200 Chart
    Back to Rankings Page
    Education

    Mastering Business Analysis

    Your key to advancing your career as a Business Analyst and beyond

    Advertise

    Copyright: © MasterClass 247 LLC

    • Apple Podcasts
    • Google Play
    • Spotify

    Latest Episodes:
    MBA066: Starting a BA Community of Practice Apr 05, 2016
    Show notes

    In this episode, Hans Eckman helps us to understand how to set up a Community of Practice or Center of Excellence, even in an organization that may be resistant to the idea.

    

    After listening to this episode, you'll understand:

    • How a CoP or CoE can benefit Business Analysts and the organization
    • Why some organizations may be resistant to the idea of starting a community
    • How to start a community of practice or center of excellence
    • How to use a story telling approach to convince people of the value of the community
    

    Show Notes

    Starting a Business Analysis Community of Practice or Center of Excellence is a great was to develop the skills of all BAs in an organization as well as share good practices and tools for a consistent experience. However, some organizations can be resistant to the idea. How do you start a community in an unfriendly environment?

    Let’s first be clear on some terms.

    Center of Excellence: A CoE is a group of thought leaders and change agents who act as advisors, experts, or facilitators for that practice. Apply their knowledge to improve a particular role or area in an organization.

    Community of Practice: A CoP is a group of people in similar roles or with a similar background to share and exchange information and help better the organization.

    If you’re dealing with a small group of people trying to lead and help an organization evolve. Larger group of people sharing information and good practices. It’s not an either/or proposition; organizations can use both models at the same time.

    Getting Started

    It’s much easier to start a Center of Excellence or Community of Practice if you can have an open discussion with the leadership team to get their buy-in and together decide what type of model you need. Unfortunately, you may not get the organizational support you seek.

    One approach that worked for Hans was to operate as an informal group for the betterment of the Business Analyst role.

    Then put together a charter to form an official CoP or CoE and meet with appropriate individuals to get approval. If at that point, you do not get approval, you can continue to meet informally and drive change.

    Getting small wins within the group can help build up your credibility and allow people to see the benefit of a group of likeminded individuals all driving towards a goal.

    Part of your process for starting a Community of Practice or Center of Excellence may be to start by analyzing your current environment to identify the benefits and challenges would be. Performing something like a SWOT analysis allows you to apply your BA knowledge and skills to create a community for the betterment of Business Analysts in your organization.

    With limited resources and limited authority (before official approval of the CoP or CoE), you’ll need to make sure what you do has a positive impact and rack up some quick wins. Above all, we need to become advocates for our own role, career, and organization.

    In an environment that undervalues the role and contribution of the Business Analyst, Hans recommends a quieter and assumed authority approach. Helping others to understand the role and develop training that will improve and standardize BA interactions will help others see the value of your group.

    Listen to the full episode to hear all of Hans’ examples, tips, and advice for starting a CoP or CoE.

    http://traffic.libsyn.com/masteringbusinessanalysis/MBA066.mp3

    Z

    Your Homework

    Links mentioned in this episode:

    • Hans Eckman’s website www.HansEckman.com
    • Link to Hans’ presentation
    • The BA 2020 Vision
    Hans Eckman

    Hans Eckman

    GVP at SunTrust Bank

    Hans Eckman provides linchpin leadership and consulting for rapidly evolving companies, with 19 of his 25+ years’ experience creating workflow & support optimization solutions across diverse industries. Hans rejoined the Innovation Programs team at SunTrust Bank, where he helps develop disruptive programs and products that drive innovation, process improvement, and engagement across the enterprise. Hans co-founded the SunTrust BA Center of Excellence. His presentations can be viewed at http://hanseckman.com.

    Thank you for listening to the program

    To get more valuable content to enhance your skills and advance your career, you can subscribe on iTunes.

    Also, reviews on iTunes are highly appreciated! I read each review and it helps keep me motivated to continue to bring you valuable content each week.

    The post MBA066: Starting a BA Community of Practice appeared first on Mastering Business Analysis.


    MBA065: The Value of Business Analysis Mar 29, 2016
    Show notes

    In this episode, Doug Goldberg help us to understand the true value that Business Analysts bring to a project and organizations.

    

    After listening to this episode, you'll understand:

    • Where Business Analysts can deliver value
    • Why the value isn’t in the documentation (and where it really is)
    • How to deliver value at every point in a project life-cycle
    • How to change perceptions about business analysis
    

    Show Notes

    As Business Analysts, we traditionally create documentation and manage requirements, but is that the value we deliver? We need to realize that we provide more value than what is captured in document. Documentation is just a mechanism to capture the value that a Business Analyst creates.

    Documentation is a means to an end and that end is a successful business outcome. Business Analysts contribute to that successful outcome by putting together relevant information to create a vision of the proper solution to a problem or opportunity. The value isn’t in the documentation, it’s in the analysis activities that help define the scope, vision, and solution.

    What creates value in the end of an initiative is critically important. We also need to understand what creates value right now and how we can provide value right away. Figure out how you can show value early in the project (before documentation) through facilitation, creating a shared vision, or whatever else creates value for the organization.

    The analysis effort needs to provide some sort of value proposition at any point throughout the lifecycle. How can you show people the value of your analytical capability early on?

    In the end, the effort may result in higher revenue, a better customer experience, or solving an organizational problem. Helping people to understand the value that you will contribute to the organization can help you achieve small wins along the way to that end result. Communicating the value of your efforts at the beginning may increase your involvement throughout the project and allow you to add value incrementally.

    Communicating the Value of Business Analysis

    Before we can communicate the value that a Business Analyst brings to an initiative, we need to change the way we view ourselves. Think about the way in which you operate on a daily basis. If you’re the type of analyst who simply acts as a note taker, you’re cementing a lower perception of what you do. Think about how you can show the value in your analysis work. Produce something that people can use and that is valuable.

    Next, take both a top-down and bottom-up approach in your organization to communicate the value you bring.

    Get a sponsor to help shepherd the message. Show them evidence of your contribution to influence their perception. For a grass roots approach, take accountability for your message as an individual and start sharing and promoting that message with your peers.

    Carry your message into a social setting by joining and participating in professional organizations to help bolster your message.

    Analysis Paralysis

    Shift your value emphasis to analysis work and make sure you aren’t caught in analysis paralysis. Don’t focus on the “what” and the “where”; focus on the “who” and the “when”. Think about who needs information and when they need it. This allows you to focus on the individual and their needs and constraints.

    This approach keeps you aligned to what’s really important to your customer; the time, the scope, and end result.

    Listen to the full episode to hear all of Doug’s advice and tips for understanding and increasing the value you bring to your organization.

    http://traffic.libsyn.com/masteringbusinessanalysis/MBA065.mp3

    Z

    Your Homework

    At the beginning of an initiative, think about the value that you will produce. Consider the “who and when” and what you need to do to meet that value proposition. Allow the team to understand your capabilities and the value of your analytical capability.

    Links mentioned in this episode:

    • Doug’s website
    • Doug’s blog post on documentation and requirements
    Doug Goldberg

    Doug Goldberg

    DougGtheBA.com

    Doug Goldberg is a Certified Business Analysis Professional (CBAP) with more than 22 years of experience. His background includes graphic design, printing, proofreading, typesetting, corporate communications, commercial kitchens, software support, online help development and training, J2EE/Java development, quality tester, and a few other sundry experiences. Doug mentors other business analysts and has a blog at DougGtheBA.com.

    • X
    • LinkedIn

    Thank you for listening to the program

    To get more valuable content to enhance your skills and advance your career, you can subscribe on iTunes.

    Also, reviews on iTunes are highly appreciated! I read each review and it helps keep me motivated to continue to bring you valuable content each week.

    The post MBA065: The Value of Business Analysis appeared first on Mastering Business Analysis.


    MBA064: Transitioning to a Product Owner Role Mar 22, 2016
    Show notes

    In this episode, Angela Wick explains the skills needed to successfully transition to a Product Owner role and how to overcome some of the associated challenges.

    

    After listening to this episode, you'll understand:

    • Which business analysis skills overlap with those of a product owner
    • The mindset shift needed to become a product owner
    • Common gaps in the business analyst skill set and how to address them
    • What you need to do to successfully transition to a product owner role
    

    Show Notes

    Can a Business Analyst be successful in a Product Owner role? There’s so much overlap between the roles and many opportunities to collaborate with the Product Owner. Because of the overlap in skills, the Product Owner role is on the career path of many Business Analysts.

    The two roles are so closely aligned that almost everything in the Guide to the Business Analysis Body of Knowledge (BABOK) is part of the Product Owner role. The most foundational difference between a product owner and a BA is decision making authority.

    Business Analysts facilitate the conversation with decision makers to arrive at a decision while the Product Owner has the authority to make decisions about the product themselves.

    Many teams and organizations view the Product Owner as the decision maker and customer/business facing role and the Business Analyst as the internal, team facing role.

    Bob Galen’s Product Owner model describes the role in four dimensions; Product Manager, Project Manager, Business Analyst, and Leader. These elements are also in the Business Analyst role and the BA can either partner with the Product Owner or transition to the PO role.

    What is a Product Owner?

    A Product Owner is a role on a scrum team that is responsible for determining priorities and what gets build. The delivery team then can focus on how to deliver that product.

    The product owner may perform elicitation, analysis, prioritization, visioning, and more to ensure a shared understanding of customer value. It’s their responsibility to create a healthy, prioritized list of backlog items that the team can deliver.

    Core BA skills that are transferrable to a PO role

    • Facilitation: Facilitation is a key skill. That includes facilitation to create a shared understanding and to elicit requirements.
    • Decision Making: A Business Analyst may be used to making decisions through models and analysis. Decision Making is also needed for Product Owners to decide the best features and capabilities of the product to maximize customer value and return on investment.
    • Prioritization: Prioritization may be an issue for some Business Analysts because they’re accustomed to prioritization through consensus building. However, as a Product Owner, you have decision making authority and the expectation is for faster prioritization decisions.
    • Systems Thinking, Modeling, and Analysis are also needed to be a successful Product Owner.

    One area where Business Analysts transitioning to a Product Owner role may struggle is documentation. If BAs see their value as producing documentation, there is a mindset shift needed to be successful as a Product Owner.

    We must shift from the need to create documentation to the need to facilitate a conversation. When we do need to create documentation, it should be just enough, just in time.

    Where are the gaps?

    The most basic gap between the Business Analyst role and the Product Owner role is the mindset. While Product Owners use many of the same skills and techniques, there is a fundamentally different way of thinking about the role and the product.

    We need to understand our own mental model and how that drives our behaviors. From there, challenge some of those thought patterns. It takes time to shift your thinking to incremental work, empowerment, and a culture of collaboration over documentation to get a shared understanding.

    The other area with which Business Analysts often struggle is Product Management; understanding the product and the value it provides to customers. As a Product Owner, you need to understand the product and which changes will be valuable to customers.

    This includes talking to customers to understand them better and create a vision of the product to align the team. From there, you can create a roadmap to develop a shared understanding of priorities and where the product is going. You may also need to create a release plan based on delivery customer value (instead of based on technical changes) and aligned to the product vision.

    We need to put customer value first and let that drive the roadmap.

    Listen to the full episode to hear all of Angela’s advice on transitioning from a Business Analyst to a Product Owner role.

    http://traffic.libsyn.com/masteringbusinessanalysis/MBA064.mp3

    Z

    Your Homework

    Keep learning! The role keeps changing and evolving. You need to have a mindset of continuous improvement and continuous growth.

    Links mentioned in this episode:

    • BA-Squared website
    • Angela’s course on Lynda.com
    • Angela’s blog on BA Times
    Angela Wick

    Angela Wick

    CEO of BA-Squared

    Angela Wick is CEO of BA-Squared. She was a member of the IIBA BABOK v3 Core Team, expert reviewer of the PMI BA Practice Guide, lead author of the IIBA Competency Model, and is a frequent speaker at industry conferences

    Angela’s passion for business and product requirements, combined with her deep and broad experiences in the field, bring a unique perspective that helps all teams develop effective, flexible requirements practices.

    • X
    • LinkedIn

    Thank you for listening to the program

    To get more valuable content to enhance your skills and advance your career, you can subscribe on iTunes.

    Also, reviews on iTunes are highly appreciated! I read each review and it helps keep me motivated to continue to bring you valuable content each week.

    The post MBA064: Transitioning to a Product Owner Role appeared first on Mastering Business Analysis.


    MBA063: Starting a Career in Business Analysis Mar 15, 2016
    Show notes

    In this episode, Laura Brandenburg explains how to use your existing skills and grow your experience to start a career in business analysis.

    

    After listening to this episode, you'll understand:

    • What key skills you need to become a successful business analyst
    • How to expand your business analysis experience
    • How to know what skills hiring companies need
    • Benefits of connecting with other business analysis professionals
    

    Show Notes

    To get started in the business analysis career, you’ll need to have a few key skills. The most important skill is communication. This includes not only written communication as in the documenting of requirements, but also verbal communication and facilitation.

    You’ll need to be able to draw information out of people and relay that information in a clear and direct way. Good communication skills are foundational. From there you can layer on other skills such as visual modeling, facilitation, and business analysis techniques.

    Getting started

    It’s difficult to get a role as a business analyst without experience as a business analyst. We need to be able to find a way to grow our experience without having that role.

    There are a lot of people were performing business analysis work without having the title of business analyst. There may be skills and experience in your current role or in your past that you can leverage. What’s relevant is that you have experience doing the kinds of things that a business analyst does.

    You may have experience in communicating with stakeholder groups, facilitating meetings, mapping of business processes, or working with the software solution.

    The first step is to reflect back on your experience and pull out the skills and knowledge you’ve gained that aligns to business analysis. You can then learn the BA terminology and translate your experience into the skills and techniques of the business analyst.

    Once you’ve mapped your skills and experience, look for opportunities to apply those skills and techniques in your job. Use this to not only build your business analysis experience, but also demonstrate that you can perform business analysis tasks successfully.

    This can lead to a snowball effect where small successes can lead to more opportunities and more experience.

    Find out what skills you’ll need

    You can learn more about what kind of skills employers are looking for by joining local professional groups such as the International Institute for Business Analysis (IIBA) or the Project Management Institute (PMI). There, you can talk to other professionals to learn more about their role in what skills and techniques are born to be successful.

    You can also read books such as the Guide to the Business Analysis Body of Knowledge (BABOK) and listened to podcasts (such as this one). There are many great books, webinars, and training classes you can take to learn more about the role of the business analyst.

    You should also look at business analyst job postings in your area to understand the skills and capabilities employers are looking for. This can be done early on is your exploring the possibility of a career in business analysis. However, you should also do this throughout your career to identify potential gaps in your knowledge and experience and to stay current.

    Looking at job postings within your organization or externally in your local area is a great way to understand the skills required and identify gaps in your experience.

    Filling in the gaps

    Once you’ve identified gaps in your skills and experience, you can seek out opportunities to try new skills and gain experience. This can be done within your organization or by helping charity groups and nonprofit organizations. You can also gain experience by helping out friends who own businesses or volunteering at professional organizations.

    Listen to the full episode to get all of Laura’s tips on starting a career in business analysis and what to do when you land your first BA role.

    http://traffic.libsyn.com/masteringbusinessanalysis/MBA_063__Starting_a_Career_in_Busine.mp3

    Z

    Your Homework

    Take one technique from the BABOK or another business analysis book and apply it in your work or outside your organization to gain practical experience. If you can apply that technique while engaging with a stakeholder, it well do even more to enhance your experience and give you confidence.

    Links mentioned in this episode:

    • Laura’s website, Bridging the Gap
    • How to Start a Business Analyst Career and other books by Laura Brandenburg
    • Laura’s free course on starting a BA career
    Laura Brandenburg

    Laura Brandenburg

    Bridging The Gap

    Laura Brandenburg is an internationally-recognized leader known for helping mid-career professionals start business analysis careers. Laura brings more than a decade of experience as a full-time business analyst to help you find transferable BA skills, expand your experience, and start your business analyst career with confidence. Laura is also the author of How to Start a Business Analyst Career.

    • X
    • LinkedIn

    Thank you for listening to the program

    To get more valuable content to enhance your skills and advance your career, you can subscribe on iTunes.

    Also, reviews on iTunes are highly appreciated! I read each review and it helps keep me motivated to continue to bring you valuable content each week.

    The post MBA063: Starting a Career in Business Analysis appeared first on Mastering Business Analysis.


    MBA062: Peer Reviews for Better Requirements Mar 08, 2016
    Show notes

    In this episode, you’ll find out why peer reviews are so valuable, how they can improve the quality of your requirements, and much more.

    

    After listening to this episode, you'll understand:

    • Why peer reviews are important for improving requirements quality
    • How peer reviews can reduce cost
    • How to implement different types of peer reviews
    • Why some peer review initiatives fail and what to do about it
    

    Show Notes

    A Peer Review is a way to improve quality of work products through having individuals in the group review the product and provide feedback.

    A Peer Review can be applied to requirements documents, software code, prototypes, wireframes, technical documents, or anything else for which quality is important.

    The added benefit of a Peer Review is that it can help spread knowledge within your group. This is possible because the creator of the work product shares information with the review participants as part of the process. As a result, you share knowledge about upcoming product changes and may discover effective practices.

    Because the cost of a defect discovered late in the development cycle is much more costly than something found in the analysis phase, peer reviews can improve quality in the beginning stages and save organizations time and money.

    Click Here to Get Your Free Guide to Getting Started with Peer Reviews

    No One Size Fits All

    There’s no one right way to perform a Peer Review. The type of Peer Review you use depends on your specific needs and the type of feedback that will help you improve the quality of your work product.

    Types of Peer Reviews range from quick, ad hoc reviews to formal inspections. For requirements documents, I have found that an approach between formal inspections and walkthroughs provided the biggest benefit.

    Role-Based Peer Reviews

    ​A Role-Based Walkthrough is a review in which meeting attendees take of different roles such as tester, developer, sponsor, and various stakeholders. The author then walks through the document and attendees provide feedback based on their assumed role.

    ​This type of walkthrough would be done before reviewing the document with the project team and can be done early in development before the document is complete. This allows the author to make changes early in the process to avoid rework and delays due to further analysis.

    Listen to the full episode to learn the benefits of peer reviews, how to avoid common problems, and start a peer review program.

    http://traffic.libsyn.com/masteringbusinessanalysis/MBA_062__Peer_Reviews_for_Better_Req.mp3

    Z

    Your Homework

    1. Find ways to conduct brief peer reviews to improve quality and spread knowledge.
    2. If you don’t have a peer review process in your organization, consider starting one. The guide to Getting Started with Peer Reviews can help.

    Links mentioned in this episode:

    • Click Here to Get Your Free Guide to Getting Started with Peer Reviews

    Thank you for listening to the program

    To get more valuable content to enhance your skills and advance your career, you can subscribe on iTunes.

    Also, reviews on iTunes are highly appreciated! I read each review and it helps keep me motivated to continue to bring you valuable content each week.

    Click the image below to get your free guide.

    The post MBA062: Peer Reviews for Better Requirements appeared first on Mastering Business Analysis.


    MBA061: Overcoming Roadblocks to Success on Complex Projects Mar 01, 2016
    Show notes

    In this episode, David Nimmo shares some strategies to help us overcome common roadblocks to success on complex projects.

    

    After listening to this episode, you'll understand:

    • Why projects are becoming more complex
    • What to do if you are pressured to create a full design/requirements upfront
    • How to overcome analysis paralysis
    

    Show Notes

    The pace of business is moving faster and projects are getting more complex. With the push for more speed and added complexity, we often find ourselves hitting roadblocks limiting our ability to be successful on projects. The challenge is to find the right way do things to help business and technology teams to achieve success together.

    Roadblock: Big Design Upfront

    One common roadblock is the push to have everything to lock all of the details in upfront in order to mitigate risk. Ironically, identifying all of the details upfront may actually lead to increased risk over more adaptive methods.

    Even if we identified everything correctly upfront, by the time the project solution is delivered, the business need, environment, or technology may have changed. The solution may no longer be fit for purpose.

    We need to try to work with more adaptive and flexible approaches, both with requirements and contracts. Outcome oriented contracts allow the flexibility to adapt the approach while still meeting the goal or expected outcome of the project.

    Beyond flexibility in the contract, using the 80/20 rule (Pareto principle) can help you deliver the most valuable items early. Usually 80% of the value can come from 20% of the requirements. Understanding what that valuable 20% is and focusing on delivering that portion early will allow you to deliver the most valuable capabilities early and then work on the remainder of the deliverables.

    Using the 80/20 approach delivers value for the business and allows us to learn and adapt along the way. Breaking large efforts into phases or iterations allows you to deliver value early and adapt to changes.

    To find the critical 20%, it’s often best to use a collaborative approach and understand what’s important to each stakeholder and technology teams. Having agreement and a common understanding of priorities will provide focus and clarity.

    Roadblock: Analysis Paralysis

    We often find ourselves in a state of analysis paralysis; continuing research and analysis activities without moving to the next step. There are several reasons for this including the desire to ensure high quality in the analysis activities. We don’t want any missing or incorrect requirements, so we work to keep digging and never move to action.

    To combat analysis paralysis, use time boxing. Set a specific time limit (e.g., one month) for analysis work. This forces focus in analysis activities and means that you will complete what’s critical and delay some non-critical activities. It also encourages appropriate risk taking.

    Nothing important or worthwhile was done without risk.

    Cynefin Framework

    The Cynefin framework allows you to categorize your project and understand the actions that are appropriate for that category. Categories include Simple, Complex, Complicated, and Chaotic and the framework includes suggested approaches to address those categories.

    Listen to the full episode to hear all of David’s tips and suggestions for overcoming chaos on projects.

    http://traffic.libsyn.com/masteringbusinessanalysis/MBA_061.mp3

    Z

    Your Homework

    Don’t be held back by chaos, complexity, or uncertainty. Make a decision and take the next step forward. If you’re unsure which way to go, seek help from peers, mentors, coaches, etc.

    Links mentioned in this episode:

    • David’s Website, NeoViz
    • Contest for David’s book launch
    • David’s book, Chaos to Success
    David Nimmo

    David Nimmo

    Executive Consultant & Lead Innovator, NeoViz

    David Nimmo has over 20 years’ IT and business consulting experience, about two-thirds of which was with IBM, where he led a community of over 400 Business Analysts in career and skill development. He has spoken to audiences at conferences in Australia and the US on topics including high performance leadership, agile, and innovative project success methodologies.

    • X
    • LinkedIn
    Chaos to Success

    David Nimmo’s book “Chaos to Success!” outlines innovative strategies you can use for creating clarity and progress for complex projects. The book includes information on several roadblocks you may encounter on your projects and strategies to overcome them.

    The book is now available on Amazon.

    Thank you for listening to the program

    To get more valuable content to enhance your skills and advance your career, you can subscribe on iTunes.

    Also, reviews on iTunes are highly appreciated! I read each review and it helps keep me motivated to continue to bring you valuable content each week.

    The post MBA061: Overcoming Roadblocks to Success on Complex Projects appeared first on Mastering Business Analysis.


    MBA060: Business Architecture and Business Analysis Feb 23, 2016
    Show notes

    In this episode, Daniel Lambert helps us to understand what Business Architecture is, how it differs from Business Analysis, and the value it can bring to an organization.

    

    After listening to this episode, you'll understand:

    • What Business Architecture is
    • How Business Architecture differs from Business Analysis
    • How a BA can get value from Business Architecture
    • What a Business Analyst needs to do to become a Business Architect
    

    Show Notes

    Business Architecture is more of a model than a method. It gives you a snapshot of your organization to better understand it’s capabilities, products, and how it delivers value.

    Often, Business Architecture is documented via a series of maps (value stream maps, strategy maps, etc.). It’s used to get an accurate picture of your company so that product and IT leaders can extract opportunities and create initiatives. It also allows you to build epics and user stories that tie back to opportunities and capabilities of the origination.

    You’ll be able to see elements in the business architecture model and be able to grasp the full picture and be more accurate in requirements and avoid redundancies.

    When we look at the top reasons for project failure (missing requirements, unrealistic expectations, etc.), knowledge and application of Business Architecture can help address these issues.

    Business Analysts can use the Business Architecture model to help define your requirements or User Stories. Linking your requirements to the architecture helps to find errors, unneeded requirements, and omissions. Additionally, understanding organizational capabilities can help accurately frame expectations.

    The Business Architect and the Business Analyst

    Business Architects main focus is at the organizational level and understanding the capabilities, market, products, and how value is delivered to customers. The Business Architect does not focus on delivery, but the information that they develop can lead to projects and ensuring alignment with organizational capabilities.

    They’re all about planning and generally not at all about delivery and execution. That’s where the Business Analyst comes in.

    You can think of a Business Architect as a scaled up version of a Business Analyst.

    • Business Architect: Understands and creates maps and models to represent the organization’s capabilities, delivery of value, products and services, etc.
    • Business Analyst: Understands value of their project/initiative and focuses on business needs and solution delivery. Ensures alignment of their projects and requirements to business strategy and business architecture.
    • Enterprise Architect: Understands and helps define the roadmap for the technology used by an organization. May lack business acumen.
    • Solutions Analyst: Understands requirements created by the Business Analyst and devises solutions that meet the requirements while aligning to the organization’s technology roadmap.

    The BA Career Path

    The Business Architect can be described as a Business Analyst with a more strategic, higher level focus. As such, the Architect role may be on the career path for the Business Analyst.

    Often, the Business Architect reports to the Director of Business Architecture under the CIO. However, because they have a business focus, it may be more effective to report up through the COO instead of technology.

    To learn more about the Business Architect role, you can join the Business Architecture Guild. They created the Guide to the Business Architecture Body of Knowledge (BIZBOK), which you can use to learn more about creating and using the maps and models that make up business architecture.

    You can (and should) also seek out the Business Architect in your organization to learn more about what they do.

    Listen to the full episode to hear all of Dan’s tips and advice.

    http://traffic.libsyn.com/masteringbusinessanalysis/MBA_060.mp3

    Z

    Your Homework

    Find out about the Business Architecture information in your organization and use it to enhance your ability to link requirements and solutions to the organization’s strategy and capabilities.

    If there is no Business Architecture information in your organization, it represents your opportunity to add more value and advance your career.

    Links mentioned in this episode:

    • Business Architecture Guild
    • Read the introduction to the BIZBOK Guide
    • Daniel’s article on BA Times
    Daniel Lambert

    Daniel Lambert

    Vice President at Benchmark Consulting

    Daniel Lambert has over 25 years of experience in IT. His company’s software, IRIS Business Architect, enables the rapid creation of Business Architecture meta models and allows for collaboration by making it easy to share the Business Architects’ work. He recently wrote an article on Business Analysts and Business Architecture for Business Analyst Times.

    • LinkedIn

    Thank you for listening to the program

    To get more valuable content to enhance your skills and advance your career, you can subscribe on iTunes.

    Also, reviews on iTunes are highly appreciated! I read each review and it helps keep me motivated to continue to bring you valuable content each week.

    The post MBA060: Business Architecture and Business Analysis appeared first on Mastering Business Analysis.


    MBA059: Problem Solving for Business Analysts Feb 16, 2016
    Show notes

    In this episode, Matt Fishbeck shares a six step problem solving framework that can help you to address the right problem and come up with the best solution for your organization and customers.

    

    After listening to this episode, you'll understand:

    • Why the skill of problem is so critical
    • How to apply a 6 step problem solving framework
    • How to apply problem solving techniques
    

    Show Notes

    As business analysis professionals and change agents, one of our most important skills is problem solving. Problems present an opportunity to bring value to our customers and organization. Without the crucial skill of problem solving, we’re limited in our contribution to the organization as well as career growth. Many people conduct problem solving intuitively simply by “thinking” without pausing to consider what the underlying process and mechanism for problem solving is. Problem solving is a discipline; a science of applying logical and analytical techniques to identify the underlying cause and recommend solutions that address the root cause. Matt’s Recommended 6 Stage Problem Solving Approach The problem solving approach that Matt uses is a simple six stage process. The staged do not need to be completed sequentially; the individual stages may repeat and be completed in iterations. The stages consist of:
    1. Defining the problem statement
    2. Defining scope
    3. Elicit information & resolving ambiguity
    4. Identifying associations and relationships
    5. Root cause analysis
    6. Solution proposal

    The Problem Solving Process Start by creating the problem statement. The problem statement is a well-defined statement or question to frame the context. After you have a clear and unambiguous problem statement, define the scope of the effort. The scope definition is probably the most important stage since it basically whether or not the problem can be solved satisfactorily. Scope is defined to apply constraints to the domain of consideration. When we have scope we know what to consider and what not to consider. Therefore, all possible solutions are directly dependant on the information within the scope. Once the scope is defined, you can move on to eliciting information & resolving ambiguity. Perform a stakeholder analysis and elicit information from all known stakeholders/sources as a basis for investigation. You can use workshops, focus groups, interviews, document analysis, and other approaches to elicit information. When we elicit information, we try to remove ambiguity as ambiguity represents the unknown, liability, and risk. To reduce ambiguity, we need to consider the taxonomy of ambiguity to provide a frame of reference to how we will resolve it. Ambiguity may be:

    • Missing information
    • Incorrect information
    • Duplicate information
    • Conflicting information
    • Incomplete information

    The above provide a basis to ask questions concerning all information that is within scope, to challenge this information to be reliable and suitable for use. Context diagrams and domain diagram can help resolve ambiguity. Next, we identify associations and relationships to organize the information so we can derive meaning from it. Information needs to be structured, aligned, and associated that provides an additional level of meaning. This is the basis for traceability. The linking of concepts. It’s not just solely used for requirements. Once we thoroughly understand the information, we can move on to performing a root cause analysis. A root cause analysis helps you to understand the underlying cause of the problem so you can address it instead of addressing a symptom of a greater issue. There are many techniques for root cause analysis including 5 Whys and Fishbone diagrams. Now that we understand the real root cause, we can propose solutions that will address that root cause. When identifying proposed solutions, consider the scope, constraints, and relative cost and value of each option. Problem solving is not some illusive black art; it’s an analytical process that can be broken down, quantified, and analyzed to identify the root cause to give rise to a viable solution. Listen to the full episode to hear all of Matt’s examples and tips for problem solving.

    http://traffic.libsyn.com/masteringbusinessanalysis/MBA_059.mp3

    Z

    Your Homework

    1. Begin applying Matt’s six-stage problem solving approach. Often, the most difficult part of problem solving is knowing where to start.
    2. Start learning the root cause analysis techniques in the Guide to the Business Analysis Body of Knowledge (BABOK). The techniques will give you more tools to help in your problem solving efforts.

    Links mentioned in this episode:

    • Matt’s Problem Solving article on ModernAnalyst.com
    Matt Fishbeck

    Matt Fishbeck

    Senior Business Analyst and Writer

    Matt Fishbeck is a Senior Business Analyst and a thought leader in Business Analysis. He takes an active interest in Business Architecture, Enterprise Architecture, and Change Management in addition to helping run a Business Transformation meetup. Matt has written numerous insightful articles for ModernAnalyst to enhance the skills and knowledge of business analysis professionals.
    • X
    • LinkedIn

    Thank you for listening to the program

    To get more valuable content to enhance your skills and advance your career, you can subscribe on iTunes. Also, reviews on iTunes are highly appreciated! I read each review and it helps keep me motivated to continue to bring you valuable content each week.

    The post MBA059: Problem Solving for Business Analysts appeared first on Mastering Business Analysis.


    MBA058: Reusable Discovery Testing Feb 09, 2016
    Show notes

    In this episode, Mark Des Biens shares an approach to reuse requirements and accelerate requirements elicitation.

    

    After listening to this episode, you'll understand:

    • Why it takes so long to elicit requirements
    • How to use a hypothesis to better understand customer needs
    • How to build a repository of requirements and tests to accelerate requirements discovery
    

    Show Notes

    One of the most frequent complaints about requirements elicitation for a new feature or capability is that it takes too long. In addition, you need to repeat the analysis for additional features or future projects.

    The reason why it takes so long is because we need to get the requirements right and we only have one chance to do it. In Agile, having only one chance is not as much of a driver, but the need for speed is greater.

    Reusable Discovery Testing

    Imagine being able to have a thorough understanding of your customer’s needs and wants even before you begin a project and having a repository of tested requirements from which to pull. Reusable discovery testing may allow you to reduce the time needed to elicit requirements by up to 60% by identifying new channels for collecting information, capturing the results of discussions with stakeholders, and reusing information.

    To get started with reusable discovery testing, begin with questions for stakeholders and customers related to your current objectives (project or feature) and broaden your questions for facets outside of your immediate objective. Perhaps an understanding of the roadmap or future state of the product will help you identify questions and hypotheses to ask and test.

    Ask these additional questions to expand the amount of data you’re collecting. Instead of asking a few focused, closed-end questions, ask stakeholders broad, open ended questions that expand beyond the current feature or project.

    Think of your questions as hypotheses that you’re trying to test. This can be related to preferences (customers prefer dark backgrounds), needs, and wants. This gives you a better understanding of your customers and what solutions may satisfy their needs.

    The number of hypotheses (tests) grows organically and becomes more of a conversation with the product owner and ultimately, customers. The key is to not only ask about customer preferences, but also ask why to understand what’s important to them.

    You can test your hypothesis by asking customers directly, by building prototypes (high or low fidelity), focus groups, and split testing. Split A/B testing is a great way in a digital setting to quickly understand customer preferences based on real data. Developers may attach old tests to new requirements instead of needing to re-document or come up with new acceptance criteria.

    The data collected could also lead to new features and capabilities of the product. The information can also lead to more fully developed personas.

    This approach can help you reduce elicitation time by decreasing the amount of documentation needed and give the team a head start on the process.

    Listen to the full episode to learn how to get started with reusable discovery testing.

    http://traffic.libsyn.com/masteringbusinessanalysis/MBA_058.mp3

    Z

    Your Homework

    Start documenting what you’re doing and the questions you’re asking. Use the answers as a starting point to ask new questions and build a repository/list.

    Links mentioned in this episode:

    • Mark’s Blog: a12p.blogspot.com
    • VersionOne
    Mark Des Biens

    Mark Des Biens

    Solutions Engineer, VersionOne

    Mark Des Biens is a solutions engineer and implementation consultant at VersionOne. Mark has more than 20 years of project experience and has worked with dozens of companies looking to improve their enterprise agility. He has been a ScrumMaster and agile program manager, and is one of the founding members of the Midwest Agile Community Meetup group.

    • X

    Thank you for listening to the program

    To get more valuable content to enhance your skills and advance your career, you can subscribe on iTunes. Also, reviews on iTunes are highly appreciated! I read each review and it helps keep me motivated to continue to bring you valuable content each week.

    The post MBA058: Reusable Discovery Testing appeared first on Mastering Business Analysis.


    MBA057: The 6 Stakeholders You’ll Meet in Project Hell Feb 02, 2016
    Show notes

    In this episode, Vince Mirabelli introduces us to the six worst types of stakeholders and shows us what to do if you have one of these stakeholders on your project.

    

    After listening to this episode, you'll understand:

    • What the six worst types of stakeholders are
    • What to do if you have one of these stakeholders on your project
    • How to perform a stakeholder analysis that works
    

    Show Notes

    A stakeholder can singlehandedly make or break a project and there are some that are . . . less than cooperative. People will behave in a way that promotes their own self-interest and sometimes that runs counter to what you’re trying to achieve in your work. You’ll need to manage those people differently than that stand to benefit from what you’re trying to do.

    There are six worst-of-the-worst types of stakeholder of which you should be aware and know how to engage and interact for best possible results.

    Stakeholder #6: The Psychic

    The Psychic is a stakeholder who knows (or at least thinks they know) what will happen and what needs to happen on the project. They sometimes jump to conclusions about the solution and could sometimes take you down the wrong path.

    You’ll likely encounter The Psychic right away at the beginning of the project. They may be a very experienced person who tries to dictate what should happen based on their experience or they may be someone who is very “by the book” on how things should be done.

    To deal with The Psychic, keep them engaged. Take their comments into consideration and help them to understand that their ideas have some merit and we want to explore other ideas as well.

    Stakeholder #5:Mr./Miss Resister

    The Resister is someone who wants to keep the status quo and dislikes any kind of change. They can be across a spectrum of mild resistance to outright withholding information and taking action to make a change effort unsuccessful. The two types of Resisters that are most problematic are those who resist outright and those who are two-faced. Two-faced Resisters are stakeholders who communicate their support to you, but withhold needed information and do not cooperate..

    To deal with the Resister, have a solid change management process in place and engage them in that process. Keep them involved and in support of the change.

    Make the change easier for them by breaking it down into smaller pieces or calling it a tweak or enhancement instead of a change. Help them to understand why we’re making the change and what’s in it for them.

    Stakeholder #4: The Career Climber

    The Career Climber is someone who wants to get ahead and often work to prove their value. This could even be someone on your team. There’s nothing wrong with being a Career Climber, unless it’s at the expense of the project.

    The Career Climber may undermine you, the project, and the team if it means getting ahead. You may get doubletalk from them; they say positive things to you, but negatively about you or the project to others.

    To deal with The Career Climber, figure out what they want and what’s important to them. Perhaps you can involve them in some way that gets them what they’re looking for such as face time with the leadership team. You can also have them own a piece of the project and take accountability.

    Stakeholder #3: Mr./Miss Emergency

    For this stakeholder, everything is an emergency. Mr./Miss Emergency can derail your project at the last minute. They feel that they’re not ready and any defect should bring the project to a halt.

    Mr./Miss Emergency may also withhold information, thereby causing the emergency. It may be a lack of engagement or purposeful withholding of information.

    You can handle Mr./Miss Emergency keep them engaged and get someone of equal or higher level who is more level headed to have a casual conversation with them about their concerns and interaction (after having that conversation with them yourself, of course). Leverage your stakeholders – especially those who strongly support you.

    Stakeholder #2: The Bulldozer

    The Bulldozer is often the most overtly disruptive and aware of what they’re doing. They often don’t have good intentions or they’re unaware of what they’re doing.

    Their actions may include yelling, throwing things, or inappropriately belittling you and the team. They really want to be heard.

    The Bulldozer likes to have an audience. To deal with them, give them an audience, but one of your choosing. Build an audience with those who support you and the project (especially stakeholders at or above The Bulldozer’s level). This makes The Bulldozer hesitant to act out when they know the support you have from those above them.

    Stakeholder #1: Conrad Hilton

    Conrad Hilton refers to the personification of a character as portrayed in the show Mad Men. Conrad would share his requirements and the team would create something that meets the requirements, but upon delivery, Conrad would tell the team that it wasn’t what he wanted.

    His famous line is “You gave me what I asked for, but not what I wanted”.

    This stakeholder doesn’t know what they want, has difficulty articulating what they want, or will just never be satisfied. Sometimes this stakeholder is your sponsor.

    With this type of stakeholder, you need to find a balance in how often you interact with them. Determine what works best to feel that they are engaged and to give feedback. The rapid feedback loops often used in Agile environments will help to make sure you’re building the right solution will also help.

    Awareness of the different types of stakeholders and knowledge of how to engage and deal with difficult stakeholders will help you in your interactions.

    Listen to the full episode to hear all of Vince’s advice on dealing with stakeholders.

    http://traffic.libsyn.com/masteringbusinessanalysis/MBA_057.mp3

    Z

    Your Homework

    Create a three-dimensional stakeholder map (2x2x4) to be aware of power, influence, and level of support for you and the project. For the support dimension, identify your Key Supporters, Ambassadors, Critics, and Key Detractors and use that information to leverage your stakeholders as needed.

    Links mentioned in this episode:

    • Vince’s Podcast in iTunes
    • Vince’s presentation deck from BA World
    • Global Project Synergy Website
    Vincent Mirabelli, CBAP, PMP, MBB

    Vincent Mirabelli, CBAP, PMP, MBB

    Principal at GPS Group

    Vincent works with clients in the fields of project leadership, business analysis and Lean Six Sigma. He has many years of direct senior-level experience in various aspects of project life, including Project Management, Business Analysis, Business Process Improvement, and Enterprise Planning. Vince has successfully instructed and trained hundreds of managers, executives and project practitioner professionals to improve their understanding of project methodologies.

    Thank you for listening to the program

    To get more valuable content to enhance your skills and advance your career, you can subscribe on iTunes.

    Also, reviews on iTunes are highly appreciated! I read each review and it helps keep me motivated to continue to bring you valuable content each week.

    The post MBA057: The 6 Stakeholders You’ll Meet in Project Hell appeared first on Mastering Business Analysis.


    Previous 1 20 21 22 23 24 28 Next

    Related Podcasts

    Making Sense with Sam Harris

    1

    Making Sense with Sam Harris Education
    Grammar Girl

    2

    Grammar Girl Education
    Good Life Project

    3

    Good Life Project Education
    Explain It to Me

    4

    Explain It to Me Education
    Team Never Quit

    5

    Team Never Quit Comedy
    Optimal Living Daily – Personal Development and Self-Improvement

    6

    Optimal Living Daily – Personal Development and Self-Improvement Alternative Health
    footer-logo

    Contact Us

    Toll Free: 844-670-7747

    Links

    • Home
    • Top Charts
    • Networks
    • Apps
    • Independents Podcasts
    • Podcast Advertising
    • Podcast News
    • Contact Us
    • About Us
    • Analytics & Insights

    Stay Connected

      Privacy, Terms of Use & Our Code of Ethics Protecting Content Creators Copyrights