This November I’m returning to the Building Business Capability (BBC) conference in Florida to spend a few days with 1200 business analysts. I’m looking forward to talking to other practitioners to hear about the experiences, the things they’re working on, and the challenges they’ve overcome.
I also have the opportunity to present a half-day workshop and breakout session and take part in a panel discussion about product ownership. The two sessions are ones I’ve delivered before, but the content should be fresh based on all of my experiences with my current day gig. Hopefully, I can use that experience to provide some good information to the people who attend those sessions.
In this week’s newsletter, I’ve included links to the sessions I’m presenting, links to a couple of episodes of the Mastering Business Analysis podcast where I talk about the content from those sessions, and a video where I explore the product owner role.
If you’re a business analyst and are looking for a conference to attend before the end of the year, you may want to consider going to the BBC conference.
If you’re already planning on going to BBC, let me know and we can try and meet up sometime during the conference.
7 Things Business Analysts need to know about agile
Agile. Scrum. Lean. SAFe.
Buzzwords to be certain, and also powerful ideas that have changed the landscape in which you and most other business analysts find yourselves today. How can you position yourself to be effective and ultimately successful in this environment?
View this presentation find out seven things business analysts need to know about agile and how you can use that knowledge to thrive as a business analyst.
You’ll learn what an agile mindset is and how you can adopt one. You’ll find out how you can apply analysis practices you already use in a way that will make you the business analyst that all your teams will want to work with. You’ll find out about the roles that business analysts can play in agile environment and select the one that is the best fit for you.
Whether you are an agile advocate in your organization or you’ve had agile “done to you,” view this presentation to find out how to be the most agile business analyst you can be.
What you need to know about agile on the Mastering Business Analysis podcast
After listening to this episode, you’ll understand:
- Why Agile alone won’t get you better, faster, and cheaper
- How a Business Analyst can play a valuable role in Agile
- Why you shouldn’t focus on writing User Stories (and where you should focus)
Build shared understanding with example mapping
One of the primary responsibilities of business analysts, product owners, and all other product people is to build and maintain a shared understanding of the outcome your team seeks to deliver. Conversations are an effective way to build that shared understanding.
You may find yourself wondering who should be included in those conversations, when do you have these conversations, what should you talk about, and how do you remember what you said?
View this presentation to learn more about example mapping, a technique that helps you structure your conversations and build a shared understanding.
You’ll learn how to determine the right people to include in your conversations when the best time is to have those conversations, how to structure those conversations, and how to remember what you said.
Example mapping on the Mastering Business Analysis podcast
One of the big challenges in organizations transforming to Agile ways of working is shifting from doing Agile (following certain practices and events) and bring Agile (adopting an Agile mindset and living the values).
Without the right mindset, your team and organization will never reap all of the benefits of Agile.
In addition to dispelling some of the myths and misconceptions about agile, in this conversation with Dave Saboe I discuss a great technique in his session, How to Build Shared Understanding with Example Mapping.
Example mapping is a great way to structure a conversation in a way that people with diverse knowledge can develop a shared understanding. You can use this powerful approach before you build anything; when you’re fleshing out features and stories.
Examining the Product Owner Role
As with everything else related to agile, the nature of the Product Owner role, and whether it is needed at all, depends a great deal on context. As teams discover this, it leads to some common questions:
- What do Product Owners Really Do?
- Do we even need Product Owners?
In this session, I examine the Product Owner role and attempt to answer the above questions. By the end of the session, you’ll have more insight into the Product Owner role and how it applies (or not) to your situation. This includes an understanding of common organizational models for product owners (including what part of the organization they fit in), how to determine appropriate product ownership responsibilities for your situation, and whether you need Product Owners to have successful product ownership.