Maps, Models, & Specs... how they connect

Connecting Story Mapping, Domain Modelling, & Spec by Example using a scenario based approach.

The Story Map was used to illustrate the system sequence of events. The Domain Model was used as a common glossary of interrelated concepts normalizing language. Spec by Example illustrated the Scenario across the Story Map events, using common language of the domains, with the variables of the scenario

 
13 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

Using one relatable yet deep Example through a story map, domain model & scenario Spec By Example.

Structurally I will define the use of each technique, then using the example layer, and build each map, model, and spec in front of the audience, practically showing how to connect the dots.

Learning Outcome

Understanding how 3 advanced techniques can be connected and provide a rich shared knowledge for complex systems.

Target Audience

Advanced Agile Coaches

Prerequisite

  • Practical experience with Story Maps
  • Practical or at least some understanding of Domain Modeling
  • Practical or at least some understanding of Specification By Example (BDD)
schedule Submitted 4 months ago

Comments Subscribe to Comments

comment Comment on this Proposal

  • Liked Declan Whelan
    keyboard_arrow_down

    Declan Whelan - Technical Debt is a Systemic Problem - Not a Personal Failing

    Declan Whelan
    Declan Whelan
    Agile Coach
    Leanintuit
    schedule 3 months ago
    Sold Out!
    60 Mins
    Talk
    Intermediate

    You often hear technical debt described as a personal failing. Why didn't you code with greater rigor? By creating technical debt, how could you have made life harder on people working in the code? More often than not, technical debt is the result of bigger, systemic problems.
    Chances are, you're not a bad person. You didn't want this to happen. It's the system, not you, that's chiefly responsible.
    In this talk, we will present some of the conclusions from the Agile Alliance's technical debt working group, which has looked into the systemic causes and consequences of technical debt. While marginal amounts of technical debt will always accrue, that does not explain why substantial technical debt is a widespread phenomenon. The organization in which software development teams work is the much bigger culprit. Many systemic causes, such as deadline pressures, under-investment in skills, and even the unwillingness to measure technical debt, conspire to create a growing burden on software professionals, who would otherwise choose not to create this problem if given the opportunity.
    Just as technical debt has systemic causes, the real cost of technical debt lies at the system level. The increasing drag on software innovation has effects not just on individual and team productivity, but on the software value stream, the portfolio, and the organization as a whole. Sometimes, the cost is obvious, such as the valuation of a start-up company's code; other times, the consequences are far more subtle and insidious.
    During this session, we will use the language and methods of systems theory to better come to grips with the causes and consequences of technical debt. Don't worry if systems thinking is unfamiliar — we will cover the basics during the talk. We will also do an exercise in which you will create a simple systems model of your own challenges with technical debt, and discuss how this model should help you shape a plan of action for dealing with technical debt.
    Ultimately, the goal of this session is to give you the tools to better deal with technical debt. Rather than blaming individual developers, you will be able to show the systemic sources of technical debt, and assess the relative value of addressing each of them. Rather than depending on technical measures to convey the costs of technical debt, we will help you to put the costs of technical debt in stark business terms.

  • Liked Sue Johnston
    keyboard_arrow_down

    Sue Johnston - It's Not About The Tools: Facilitating Effective Meetings Across Distance

    40 Mins
    Talk
    Intermediate

    A face-to-face conversation is the most efficient and effective method of conveying information to and within a development team. So states the sixth principle of the Agile Manifesto.

    Reality comes with a big "however." Work-at-home, outsourcing and inter-company partnerships mean that, more and more, we find ourselves n meetings where other participants are not in the same room. They may be around the corner or around the world. Some organizations invest in powerful tools to make this arrangement work well - or, sometimes, not so well. Others make do with audio only. Are we fooling ourselves when we call these events "meetings?" Maybe. Yet they're part of our world, so why not make the most of them?

    In this lively session, you'll examine a proven pattern for facilitation, discover ways to overcome the challenges of virtual meetings and learn techniques that encourage meaningful participation. Most of these require more focus and ingenuity than expense.

    Sue will share some of the techniques she learned as a teleworking pioneer in the '90s and a trainer of coaches, via distance, since 2003. Join us to explore ways you can bring your meetings with remote participants to life and respect everyone's time - including your own.

  • Liked Sue Johnston
    keyboard_arrow_down

    Sue Johnston - Do Your Product Owners Speak A Foreign Language? Techniques for creating shared understanding

    60 Mins
    Talk
    Intermediate

    Effective interactions, between product owners and designers and team members who develop and make those products real, are key to team, product and organizational success. It's reflected in the first value of the Agile Manifesto.

    Still, one of the chief complaints, from both the product side and the dev side, is poor communication. The list of irritants includes: lack of clarity, lack of understanding, lack of time, lack of access, too many meetings, too much jargon, too many badly written user stories and too many people involved.

    Communication isn''t the only obstacle, but it’s a big one - and it can be overcome with no cost or organizational disruption.

    Regardless of the role we play on the team, part of everyone’s job is to create shared understanding. In this session, Marilyn, an experienced product owner and product manager, and Sue, a communication specialist and coach, will share their research about communication gaps in the product-development relationship and approaches that can close the gap.
    Join them to explore tips and ideas to improve communication flow and help teams move from concept to cash.

    NOTE TO TAC TEAM
    Because we are doing some original research on this topic, I would like to include a co-presenter, Marilyn Powers, PEng, who, at the time of posting, is not yet on confengine. Info about her is available at https://www.linkedin.com/in/marilynpowers

    Here is more biographical info about Marilyn:
    Marilyn has more than 10 years experience bringing products and services to market as a Product Manager. As a licensed professional engineer, she has experience working in a variety of fields, from manufacturing to operations to simulation to SAAS software. Currently, Marilyn is a Product Manager at D2L, a leading Ed-tech company, where she works closely with Product Owners, Dev teams, Designers, Senior Leaders and many other stakeholders to deliver quality software tools to educational institutions and corporations who value learning and development. Her expertise is creating shared understanding between diverse groups, be it external customer advisory groups or internal stakeholders.

    Previous presentations or workshops
    Marilyn has presented at a variety of conferences over the past 20 years, the career highlight of which was a live demo on the main stage keynote at the D2L Fusion 2016 conference. Other conference presentations included Online Learning Conference ( New Orleans, LA 2017), Fusion (2015, 2016), Learning Impact Leadership Institute (San Antonio, TX 2016), Industrial Engineering Student Conference (Kitchener, 2016), ModSim World Canada (Montreal, 2010), Montreal Neurological Institute Day (Montreal, 2009), McGill University invited speaker on Haptics (Montreal, 2006). Prior to these presentations, Marilyn was an Instructor of Engineering at Mount Royal University in Calgary, AB.

  • 40 Mins
    Talk
    Intermediate

    Although self-organizing teams are crucial to carrying out a successful Agile transformation, organizations that implement Agile at scale invariably realize that the introduction of such teams forces the organization to re-engineer numerous aspects of its operating philosophy. In particular, various management layers are often removed. The individuals in these layers are routinely re-purposed or laid off.

    This talk highlights the approaches I used as an Agilist in various organizations to help people in different roles on their journey of transitioning into the world of Agile. Specifically, the talk will focus on 5 key roles: Project Managers, Product Managers, BA Managers, Development Managers, and QA Managers. It will provide insight into how managers can effectively transition to some of the new Agile roles, or redefine their existing role to effectively fit in an Agile world.

    The emphasis in this talk is on pragmatic strategies for managers that are struggling to find their place in this new Agile world. Armed with these strategies, participants will be able to effectively adapt to the Agile transformation, as well as discover potential new career paths for themselves and for the individuals reporting to them.

  • Liked Daniel Doiron
    keyboard_arrow_down

    Daniel Doiron - OKALOA FLOW LAB

    Daniel Doiron
    Daniel Doiron
    President
    Agile Agonist
    schedule 5 months ago
    Sold Out!
    90 Mins
    Workshop
    Intermediate

    Agility is a mindset. It is not a set of practices that can be installed. But how do you get out of the practices trap, especially when you have to mobilize not just software development and IT teams but the entire organization towards business agility where value is created through meaningful work? How do you engage business teams, users and customers? How do you enable higher levels of collaboration, not just within teams but also across teams? In other words, how do you get individuals, teams and even the entire organization into a flow state where everybody is doing the right thing at the right time by having the right conversations? Rational explanations and models of agility will only go so far. To be truly effective, the agile mindset needs to be experienced, which is exactly the purpose of the new and thought provoking Okaloa Flowlab simulation by Patrick Steyaert, one of agile's better scientific mind.

    Through simulating a conventional work environment that reflects a mechanistic mindset characterized by a focus on resource efficiency, command and control and specialist workers, participants experience which roadblocks need to be overcome. As the team is taking its first baby steps into agile, they will experiment (in 2 or 3 rounds) with policies and practices (e.g. pull of work, cadences, limiting WIP) that enable collaboration, get the team into flow, and allow an agile mindset to emerge. Weaved into the simulations they will discover the fundamental difference between resource efficiency and flow efficiency.

    Participants will step into the simulator after a brief explanation of the rules.

  • Liked Scott Ambler
    keyboard_arrow_down

    Scott Ambler - The Executive’s Guide to Disciplined Agile: Business Agility for Established Enterprises

    60 Mins
    Talk
    Intermediate

    An agile enterprise increases value through effective execution and delivery in a timely and reactive manner. Such organizations do this by streamlining the flow of information, ideas, decision making, and work throughout the overall business process all the while improving the quality of the process and business outcomes.   This talk describes, step-by-step, how to evolve from today’s vision of agile software development to a truly disciplined agile enterprise. It briefly examines the state of mainstream agile software development and argues for the need for a more disciplined approach to agile delivery that provides a solid foundation from which to scale. We then explore what it means to scale disciplined agile strategies tactically at the project/product level. We then work through what it means to strategically scale across your IT organization as a whole and discover what a Disciplined DevOps strategy looks like in practice. Your Disciplined Agile IT strategy, along with a lean business strategy, are key enablers of a full-fledged disciplined agile enterprise. The talk ends with advice for how to make this challenging organizational transition.

  • Liked toddcharron
    keyboard_arrow_down

    toddcharron - I'd Buy That For A Dollar

    60 Mins
    Talk
    Beginner

    What happens if we build it and they don’t come?

    Building features no one cares about is not only bad because the feature isn’t getting used, but is also a wasted opportunity that could have been used to build something truly valuable for your customers.

    But how would we know?

    In many companies, features get prioritized by the HiPPO principle (Highest Paid Person’s Opinion). As it turns out, this is often not the most effective way to prioritize your backlog.

    But if not this, then what?

    In this workshop we explore what value is, how to talk about it, and how we might measure the value we have achieved.

  • Liked Johanne Boyd
    keyboard_arrow_down

    Johanne Boyd / Carlo Rosales - Why can't the business be agile too? How ADP is incorporating business Agile practices to keep up with technology

    40 Mins
    Talk
    Beginner

    Does your business struggle to catch up and understand the technical deliverables from your Sprint Reviews? Is there unnecessary re-work and scope creep because requirements are not properly described by the business? ADP has sought to address these issues by incorporating business Agile practices to keep up with technology. The result? Clearer requirements, strong engagement during Sprint Reviews and a collaborative solution with business readiness aligning with technical deliverables. Join our session to find out more!!

  • Liked Steve Zhang
    keyboard_arrow_down

    Steve Zhang - The Joy Of Functional Programming

    Steve Zhang
    Steve Zhang
    Development Practice Coach
    Scotiabank
    schedule 4 months ago
    Sold Out!
    60 Mins
    Talk
    Intermediate

    The popularity of Functional Programming is booming! Are you still wondering what all of the fuss is about? Come to this session and find out! This is an introduction to the power of functional programming. It covers functional programming's basic concepts, and shows you how functional programming will make software simple, elegant, easy to test, and lead to cleaner code. I will share my experiences learning, so you can avoid some of the pitfalls. So if you enjoy coding, love clean code, then you should start learning Functional Programming right now.

  • Liked Mishkin Berteig
    keyboard_arrow_down

    Mishkin Berteig / David Sabine - JIRA is the Worst Possible Choice

    90 Mins
    Workshop
    Intermediate

    A rant, with evidence, on why electronic tools in general, and JIRA in particular, are anti-Agile. Participants will use the Agile Manifesto to evaluate the electronic tools they are currently familiar with. JIRA is used as a case study.

    NOTE: Scrum asks us to have courage. The Agile Manifesto asks us to value individuals and interactions over processes and tools. I hope the organizing committee will consider this proposal despite the risk that it might offend some tool vendors. If we can't speak freely about our experiences with tools, we will fail as a community.

  • Liked Dave Dame
    keyboard_arrow_down

    Dave Dame / Aaron Sampson, PMI-ACP, ITILv3, SMC - Design Thinking for Organizational Change

    40 Mins
    Talk
    Beginner

    We all know how people use design thinking to create better products and deliver delightful experiences to our users. However, design thinking can be an excellent tool to use for organizational change. In the case of organizational change, our product is the change that we are trying to drive, and our customers are those people who are impacted (internally and externally) and have to live with that change. In the same way that design thinking puts the user front-and-centre for products, it can be used to put people in the organization front-and-centre. In this talk we will discuss how design thinking works and, as a case study, how we have applied it at Scotiabank to help drive adoption of the Bank’s NPS customer insights into building solutions that serve our customers. In that program, previous internal processes were ineffective in pushing relevant data to delivery teams at the right time. Using a Lean or Agile approach would have provided some benefit, but taking a design thinking approach uncovered an array of useful insights to make the whole process more purposeful. Learn from this example to explore how you might incorporate design thinking to drive greater effectiveness and relevance for your team’s body of work.

  • Liked James Gifford
    keyboard_arrow_down

    James Gifford - Descaling the Enterprise Instead of Scaling Agility

    90 Mins
    Workshop
    Intermediate

    In spite of all of the nuanced discussions, debates and frequent diatribes, scaling agile is about one thing: getting large groups of teams to deliver value in an organized fashion while maintaining empathy, rapport, trust, safety, and ownership across the enterprise. During this session, we will explore the case study of the Value Steam Container, looking at organization design, challenges and success. Focusing in on topics ranging from

    • Organization designs used by WL Gore, The Dunbar number

    • Delivery Triads - Product, Delivery, Technical Excellence

    • Venture capital style funding

    • Focusing on business value

    The second half of the session is a workshop focused on creating a Value Stream Container and resource based on team funding 

  • Liked James Gifford
    keyboard_arrow_down

    James Gifford - 5 Metrics to Create Safety and High Performing Teams

    60 Mins
    Talk
    Intermediate

    Description:

    I see that a lot of organizations use metrics in inappropriate ways to measure teams. At the heart of these metrics, nine times out of ten, are velocity and story points. These metrics lead to a lot of mistrust, fear, and bad technical practices. This talk will focus on shifting the focus to diagnostic metrics.

     Before shifting focus to diagnostic metrics, we need to understand what inappropriate metrics are. When questioning teams about why their velocity was lower from one sprint to another, teams are more likely to inflate their estimates to avoid questions in the future. This is one of my scenarios. We will explore this case and my other top-ten based on the 165 teams I have interacted with. Focusing on one metric does not provide a balanced view of the team.

    For balance, I promote five metrics. The combination of metrics balances each other. These five metrics are lead time, quality, happiness, agile maturity, and business value. Focusing on these five metric areas can be used as a diagnostic tool to help teams grow and support coaching. During the session, we will use my Excel-based tool and visual model to simulate this balance.

    When you push shorter lead times (how fast) on a team with a lower agile maturity, the first thing to change is quality, followed by happiness and then the delivery of value. Conversely, if a team focuses on TDD, the first thing to change is quality, followed by agile maturity, reduction in lead time, and increased delivery of value.  

    Teaching teams to harness data in a positive way will help them to flourish.

  • Liked thomasjeffrey
    keyboard_arrow_down

    thomasjeffrey - Scaling Agile without the scaling framework

    thomasjeffrey
    thomasjeffrey
    President
    Agile By Design
    schedule 3 months ago
    Sold Out!
    60 Mins
    Talk
    Advanced

    Increasingly Agile adoption has focused on how to operate larger enterprises with agility, and run larger and larger initiatives, at scale.

    In many cases, organizations have turned to explicit agile scaling frameworks to address their needs to coordinate increasingly larger efforts to deliver value in a way of that does not sacrifice feedback and self organization . Often these frameworks attempt to address the complexity that comes with large scale by adding extra process and procedure. Prescriptive advice is prescribed in the form of additional roles, stages, gates, and methods. This approach to scaling bears more than a little similarity to the heavy weight methods of the past, but in this case merging agile terminology with much of the same framework bloat and bureaucracy we have seen in the past.

    As a a result adoptees struggle to understand how to fit these frameworks to their context, and seasoned coaches struggle to wrestle out the good bits.

    During this session I will discuss a different approach to scaling agile, one that places an emphasis on both mindset and practice. I'll pay particular attention to the topic of leadership, organizational design, and the role management has to play in designing a system of work that allows larger efforts to work with an agile mindset without being forced into a one size fits all process framework.

    A key part of the discussion will be to showcase how core agile methods and techniques can be extended and expanded to successfully manage coordinated agile deployments that range from hundreds to thousands of FTEs. I'll present these techniques by using real examples of agile deployments I have been a part of during my work with ScotiaBank's agile journey.

    Key Scaling Practices covered will include:
    - The design components required to structure your organization based on demand
    - How to continuously de-scale your organization
    - "Get Out Of the Boardroom" style governance and leadership
    - Operational cadences and Impediment Escalation Flow
    - Managing the flow of value at the Business Technology Asset level
    - Moving the conversation from stories to domains
    - Streamlining finance and budgeting to align to the agile mindset

    I hope to illustrate ways that both management and knowledge workers can select techniques that allow them to scale agile as needed to support ever larger initiatives without succumbing to a one size fits all framework that does not adapt constant change.

  • Liked Taimur Mohammad
    keyboard_arrow_down

    Taimur Mohammad - Delighting the Customer at the First Point of Interaction

    Taimur Mohammad
    Taimur Mohammad
    Coach
    Agile By Design
    schedule 3 months ago
    Sold Out!
    40 Mins
    Experience Report
    Intermediate

    The first interaction with a prospective customer often makes or breaks the sale. In today’s age of instantly obtaining products and application at the touch of a button (e.g. mobile apps), the last thing that customers expect is a long, complicated process. Truly delighting the customer requires moving towards instant gratification. How do you re-organize traditionally separate business and technology groups so that the focus is on delighting the customer?

    A group within a leading financial institution identified this as a goal and looked at lean-agile principles and practices to rapidly iterate on delighting the customer and bringing business & technology processes seamlessly together. While delivery was set up using what we’ve come to as good lean-agile principles and practices, how the product backlog was managed provided the rapid feedback, innovation and pivot/pursuits required to truly delight the customers.

    In building the product backlog a number of practices were introduced to make it dynamic and ever evolving.

    • Kanban connected the customer to the product backlog which connected to the delivery engine
    • Product metrics and cost of delay were used to create hypotheses to prioritize MVPs
    • Rapid feedback through various customer and proxy customer interactions were leveraged to feed the customer backlog
    • Monthly releases ensured a constant flow of new features to enhance the customer’s experience
    • Story decomposition ensured the customers feedback was being directly communicated with the delivery team

    The result? While the client is still on its journey the results have been overwhelmingly positive. Key metrics indicate greater customer satisfactions, increased speed to completion and simplified internal processes.

    In this talk we’ll discuss how we’ve taken various product management related practices and stitched them together to connect the customer to the delivery engine. We’ll provide practical examples that we’ve seen work in our experience and engage in a discussion with the group to connect their questions to our examples.

  • Liked Paul J. Heidema
    keyboard_arrow_down

    Paul J. Heidema / Iaroslav Torbin - Think Agile Retrospectives are Boring? Think Again: Let's Create a Whole New Set of Activities

    90 Mins
    Workshop
    Beginner

    Last year, I was at an Agility Day in New Jersey for my company (ADP). During this day of fun, we uncovered and created new ways of improving retrospectives and new retrospective activities.

    You don't have to always do "Start, Stop, Continue" or "Pluses and Deltas". There are plenty of activities that are more creative and more joyful for teams and groups!

    In this workshop, we will follow a powerful technique to brainstorm ideas, filter down to the best ones, and then try them out on each other to uncover new and more effective retrospective activities. Come prepared to contribute to a new group of retrospectives!

    Gamestorming - Divergent Emergent Convergent

    We will go through a divergent process, and emergent process, and a convergent process in creating our new retrospective techniques. These and other powerful techniques will be utilized from the book Gamestorming to harness the power of the participants to create powerful and useful retrospective activities.

  • Shawn Button
    Shawn Button
    Agile Coach
    Leanintuit
    schedule 3 months ago
    Sold Out!
    60 Mins
    Talk
    Beginner

    We are about launch our latest feature to the eager public, when suddenly we get the call all developers dread: The Site is down! Our business is pressuring us to quickly come back up, but we can’t even find the problem! We pick up the red phone and call Karen, "The Site Whisperer." She calmly spends five minutes typing, and announces that she found the problem, and everything is back to normal. Where would we be without Karen? How can we get these skills on the rest of the team, so anyone can work the magic she does?

    It turns out that troubleshooting is a learnable skill. Join Shawn as he explores the Science of Troubleshooting. This workshop will examine what is happening during effective problem solving. It will examine types of scientific reasoning, and explore how we are using them to solve problems, sometimes without even realizing what we are doing! Participants will see how, by using scientific reasoning and experiments to build and test hypotheses, they can greatly increase the effectiveness of their troubleshooting and debugging. By making the process explicit even consummate problem solvers can improve how they approach and solve problems. Using the awareness gained attendees can guide others to improve their problem-solving skills.

  • Liked Taimur Mohammad
    keyboard_arrow_down

    Taimur Mohammad / Sean Deschamps - Surviving Disruption with Agile: Innovate or Die

    40 Mins
    Experience Report
    Intermediate

    Lean-Agile is easily & often associated with customer centric products and solution. The “customer facing” nature of the product allows for thin slicing, feedback and iteration which in turn leads to greater business agility and customer satisfaction. While there have been many exceptional case studies that demonstrate this, applying lean-agile to non-customer facing solutions has often been dismissed. Why is this? The risk is too high to thin slice? There’s no way to get customer feedback? There’s no way to deliver using iterative approaches?

    Over the last 16 months a group within a leading financial services client was brought to a cross roads. Their traditionally stable market was on the verge of being disrupted due to emerging innovation and competition from smaller, more nimble competitors. They knew to operate the same way would result in significant losses in market share over the next decade. To survive, they had to lead the innovation. Change was becoming the norm, and their focus shifted from being solely focused on final solutions, to also re-thinking how they got to these solutions.

    Enter lean & agile principles and practices. Initially dismissed because this client’s business model operated as the backbone of the institution. Much of the work they did was in facilitating payment origination and transaction settlement systems. Applying lean & agile required some significant tailoring.

    In this talk we will discuss this client’s journey, how they changed the entire culture within the organization to focus on survival through agility. We’ll discuss how common lean-agile principles and practices can be applied and tailored to support transforming legacy eco-systems with back-end facing solutions where the concept of a real life "customer" is quite foreign. We'll visit our experiences in encouraging the transparency that is synonymous with an agile approach and how that fostered better partnerships and trust across many groups. We’ll explore how a culture of learning has established early wins for the client and set them on a path towards leading innovation, agility and empowered being first to market.

  • Liked Tyler Motherwell
    keyboard_arrow_down

    Tyler Motherwell - Divide And Conquer

    40 Mins
    Experience Report
    Intermediate

    Conway’s Law tells us that the products an organization produces will mirror the communication structures within themselves. Many organizations struggle to organize in a way that facilitates both agility and bringing quality products to market. However, this is a problem that exists, not just within IT, but across the entire enterprise. Imagine you’re the (somewhat mythical/revered) business. How do you organize yourselves in this brave new world? Many of the common patterns (systems, application/application layer) that we commonly apply in technology aren’t good fits.

    In this session, you will learn how to use a structured method to organize your most important resource (your people) around your most important goals. Additionally, you will learn about team types outside of your typical cross-functional team! We will use an actual industry case study to help illustrate usage, as well as give inspiration to how you might do the same in your organization

  • Liked Sam Tabbara
    keyboard_arrow_down

    Sam Tabbara - How to transform culture in large enterprises

    Sam Tabbara
    Sam Tabbara
    Senior Consultant
    Agile By Design
    schedule 4 months ago
    Sold Out!
    40 Mins
    Experience Report
    Intermediate

    Most important factors in any Agile transformation are the ability to react and change quickly, which are most often associated with startups than large enterprises. To really win and transform an organization there are core elements that need to be mastered and executed at the culture level. We will cover these elements and provide you real use cases where transformations both succeeded and failed to meet their potential to prove the relationship.