Laura Brandenburg explores the path to success in a business analysis career. Tips, strategies for progression, self-assessment, and best opportunities.
Understand what is an MVP (Minimum Viable Product), the difference from a Minimum Marketable Product, Prototypes, Proof of Concept, and Proof of Value.
Discover the pivotal role of business analysts in deciphering core issues, aligning technology solutions, and driving organizational success.
Discover the crucial role of requirements in software development. Karl Wiegers shares insights on their importance, clear communication, and agile practices for success.
Stefan Bossuwé and Ines Vanlangendonck discuss the topic of sustainability requirements and how that may be applied in a BA perspective.
Heather Mylan-Mains presents business analysis as a critical component of any organization that seeks to thrive in a constantly change.
Keith Ellis presents the value of Business Analysis (BA) for Human Resources (HR) professionals to be nimble and responsive to change.
Linda Parker and Julia Newell share their experiences related to the value of volunteering and provide practical tips on how you can make a difference in your BA community.
Keith Ellis states that an organization can implement agile methodologies, but that does not guarantee that it will be nimble.
Kathy Berkidge explains how incorporating mindfulness into the workday can lead to a more productive and fulfilling career.
In my second interview with Chat GPT Assistant, we could see some practical examples of it working together with a Business Analyst.
Based on laboratory studies, Trent Leopold, a neuroscientist and business analysis expert, shares some takeaways that Neuroscience offers to Business Analysts.
Amanda Zurn shares her experience as a Certified Business Analysis Professional (IIBA-CBAP) and a Certified Business Architect (BA Guild Certified).
Barbara Carkenord explains the most valuable features of REQM tools and how they can improve a Business Analyst’s productivity.
Terry Baresh explains what cybersecurity is and relates it with the job of a Business Analyst in a project.
Igor Arkhipov tells us how the role of the BA is actually diverse and currently changing and makes some predictions of what we may see in the next 5-10 years ahead.
Ron Ross argues that basic knowledge has been neglected and it is the key to communicating more effectively and engaging stakeholders with the least ambiguity possible.
Sasha Aganova presents the biggest challenge in a business transformation and what are the main disciplines to deal with it.
Roger Burlton explains how Architecture helps us to collect, connect and correct the various dots of a business.
Grant Wright and Paddy Dhanda show how visual thinking may be available for anyone to communicate better and interact in a more creative and funny way.
Jamie Champagne provides some guidance for business and data people to collaborate for informed decision-making.
Judy tells stories about change projects and how stakeholders should be approached to engage and commit to change.
Scott Bennett provides some tips from his experience as a BA Manager to make people develop their skills with the help of others in the team.
Mark Smalley shows how the analysis of the value stream must be expanded to include the point of value realization by the user.
Indy Mitra explains that Business Analysts should be considered as controls to mitigate risks and enhance the chance to get better benefits from business initiatives.
Ryan Folster compares the production of a TV series with incremental product development and presents some lessons we may learn from Friends.
Keith Ellis presents the key competencies to become a data-driven organization.
Delvin Fletcher, CEO of the International Institute of Business Analysis (IIBA), explains why the BA Mindset is important, and what else one needs to help a business get better outcomes.
Karl Wiegers tells the most important lesson he learned after fifty years working in software development.
Filip Hendrickx provides very useful tips to transform organizations in a way that change may persist.
Juande Santander-Vela explains how safe is being used to build software in a large-scale world project.
Andrej Guštin tells the story of data storytelling and shows how BAs can understand their audience to show the context behind data.
Scott Ambler, VP of Disciplined Agile at PMI, explains that there are many good options for a business analyst in an agile environment.
Barbara Carkenord expands the horizon for Business Analysis professionals showing how they may apply BA skills at different organizational levels.
Ian Spence shows how a team can learn and adapt Scrum using game cards.
Alexander Belin explains the difference between digital and regular transformations and advises BAs on the challenge they must deal with.
Ivar Jacobson presents The Essence of Software Engineering to describe Methods and Practices based on common ground.
Ivar Jacobson tells some of the craziest things he has noticed after 50 years of working with methods and frameworks.
LN Mishra tells some steps to grow as a business professional. Any business professional.
Yulia Kosarenko explains how a BA mindset targets the motivation of any professional to look for better business outcomes.
Karl Wiegers presents some principles and lessons anyone can use to design better products.
Jared Gorai lists the main benefits of being an IIBA associated member.
Amy Ruddell provides great tips to be accepted and became a successful speaker at the greatest professional conferences.
The master of Happy Projects, Roland Gareis, presents projects as temporary social systems to achieve unique results.
Angela Wick challenges the myth that there is no BA on agile teams.
Briana Ertanin explains how the business analyst is evolving to a C-Level role in Australia and invites the community to be part of this change.
Keith Ellis tells us about how Business Analysis is expanding and creating new opportunities for many professionals.
Debra Paul explains how a service view can guide the development of a BA professional.
Paddy Dhanda and Grant Wright show you how to put visual thinking into practice.
Dr. Penny Pullan shares some tips to plan an effective workshop.
Could we define a single specific value proposition for Business Analysis? Debra Paul doesn’t think so.
Gladys Lam illustrates the difference between business requirements and business rules with a simple and practical example from home.
Christina Lovelock explains how to define and organize Business Analysis as a structured service in an organization, giving clarity about the role of BAs.
Kevin Brennan explains the difference between business analyst, product manager and product owner.
Vince Mirabelli defines the contribution of each discipline to reach better business outcomes.
Howard Podeswa explains the meaning and how to use Acceptance Criterias in a Software Development life-cycle based on an Agile Approach.
Adrian Reed explains the necessity of answering WHY? and WHAT? before defining HOW? And, despite there is not a single order for that, there must be an alignment to put projects on track.
Alain Arseneault explains why Business Analysis must be done at a Strategic level to guide better business decisions.
Vince Mirabelli explains the value of Enterprise Analysis and how it must be pursued by any professional in an organization.
Howard Podeswa points four different techniques to help us to create stories that could be passed to the development team.