<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Angela Wick — BA-Squared, LLC on Medium]]></title>
        <description><![CDATA[Stories by Angela Wick — BA-Squared, LLC on Medium]]></description>
        <link>https://medium.com/@ba-squared?source=rss-64bd13358666------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*o_oMek7n15V5hZRdo2Wv3A.jpeg</url>
            <title>Stories by Angela Wick — BA-Squared, LLC on Medium</title>
            <link>https://medium.com/@ba-squared?source=rss-64bd13358666------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 11:27:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ba-squared/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Positioning The BA Role For Value In Your Organizations]]></title>
            <link>https://ba-squared.medium.com/positioning-the-ba-role-for-value-in-your-organizations-7eb2387ae73?source=rss-64bd13358666------2</link>
            <guid isPermaLink="false">https://medium.com/p/7eb2387ae73</guid>
            <category><![CDATA[agile-coaching]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[business-analytics]]></category>
            <category><![CDATA[business-analysis]]></category>
            <dc:creator><![CDATA[Angela Wick — BA-Squared, LLC]]></dc:creator>
            <pubDate>Tue, 09 Feb 2021 21:19:24 GMT</pubDate>
            <atom:updated>2021-02-09T21:19:24.396Z</atom:updated>
            <content:encoded><![CDATA[<h3>Everything BAs Do Involve Three Things</h3><p>We all know how valuable business analysis is to organizations. As complex as our work is it all boils down to:</p><ul><li>Solving Problems</li><li>Enabling Change</li><li>Making Good Decisions</li></ul><p>Problem-solving, change, and decisions are everyone’s business! Not just the BAs! Exactly! BAs help teams solve problems, enable change and make decisions. In many organizations, the role and title of the BA have been limited to a small system scope and writing requirements for project teams. Yet “business analysis” as a practice, set of skills and techniques goes so much deeper.</p><p>If we widen the lens and look at how organizations and teams identify, prioritize and solve problems; prepare for and provoke (or prevent) change, and make decisions (big and small) about the future state, we see the business analysis touches EVERYTHING! These critical pieces of every team and organization are all about people, workflows, processes, customer experience, systems, data, policies, vendors, partners… and most importantly, now they all connect and impact one another.</p><p>In the past, the BA role or title in many organizations tried to assume a context. For example, BAs work on preparing development teams for work to update a system and preparing the business/operations teams to accept the system changes. This is quite a narrow definition of what business analysis is as a whole and could stifle true results as organizations move more into integrated models of evolving, business models that enable agility, and digital models that put the focus on the customer experience.</p><h3>Rethinking the BACoE</h3><p>Organizations must look more broadly at how business analysis is done to enable the future of the organization. This means that a BA Center of Excellence, Community of Practice, BA Team, PMO, or whatever the organizational entity is that manages Business Analysis practices (and perhaps also the people performing this work) needs to be integrated within the organization as well.</p><p>In the past, many organizations have developed Centers of Excellence, Centers of Practice, and Communities for Business Analysis and BAs. These organizations had goals of making practices more consistent, building standards for BAs to follow, training, and building BA competencies/skills. These centers of excellence/practice/community have been primarily built on a traditional/waterfall IT systems context. Parts of this remain valid and other parts do not and these communities are struggling. They are struggling to show their value and struggling to find their way in an increasingly agile world where there isn’t a clear answer on how to transform the BA Practice into an Agile BA Practice.</p><p>If we are looking to build more agile BA practices and show the BA value, we need to rethink the purpose of a BA Center of Excellence/Practice/Community. We need to rethink the idea that business analysis is a phase or a stand-alone service. Business analysis needs to be an integrated practice. It needs to be integrated with other disciplines and practices to be taken seriously and show the value. The BA Center of Excellence/Practice/Community needs to be a collaborative force with the strategic transformations happening in the organization. Agile, Digital, Cloud, DevOps, Customer Experience, Process Engineering; the BA practice needs to integrate and align with these. We can no longer ask that these initiatives follow a BA process or practice we have set out and followed “our” requirements practice. We need to integrate business analysis into these processes and frameworks.</p><h3>What Does An Integrated BA Practice Mean?</h3><p>Integrating the analysis and requirements practices into these other frameworks is no easy task. It requires that we rethink what is a “standard” practice. It’s not about all projects following the same set of techniques and templates for requirements. What this means:</p><ul><li>Having a mindset and an analysis approach that is flexible to the needs of each team and project.</li><li>Developing an approach using a toolbox of techniques and <a href="https://www.ba-squared.com/blog/the-top-10-business-analysis-skills-for-2020-and-beyond/">skilling the BA team to be empowered to choose the right technique</a> at the right time for the needed purpose.</li><li>Ensuring BAs know what effective analysis looks like, and feels like as part of the team, rather than focus on them knowing a template, process, and set of artifacts.</li><li>Developing a practice that enables a set of generally accepted techniques and approaches that align with Agile, Digital, Process, Data, DevOps, Cyber Security, Package/Cloud Software, Customer Experience, etc.</li><li>The BA Practice Leader/Manager spends much of the time connecting with and collaborating with other discipline leaders to align practices rather than talking other teams into accepting a defined BA practice.</li><li>This likely means retooling, re-skilling, and reinventing what skills your BAs need, have, and work on improving.</li></ul><h3>Steps To Take Now</h3><ol><li>Start meeting with other discipline leaders (Agile, QA, DevOps, Digital, CX, Process, etc..) ask them what their pain points are, and link to how analysis practices can help them be better at what they do. Learn and understand their practices and processes and where requirements and analysis to weave into them. Try to avoid the temptation to talk them into following your ideal BA practice. It’s not about getting buy-in to “do requirements right”, it is about getting traction on using analysis skills and practices in an integrated fashion throughout the organization to elevate business outcomes.</li><li>Work with other discipline leaders on some experiments to see how BAs can partner with them to make them better at what they do.</li></ol><p>Yes, that’s right! How can BAs make these other groups better at what they do? This is the million-dollar question that will drive value for the BA role and make the BA Practice an integrated practice.</p><p>We are here to help you along in this journey. Are you ready to integrate your practice and start building value for the BA Role in your organization? Here are two things you can do right now:</p><ul><li><a href="http://www.ba-cube.com/enterprise"><strong>Learn more about BA-Cube.com Enterprise for teams here!</strong></a></li><li><a href="https://www.ba-cube.com/live-events/"><strong>Register for the next BA Manager and Practice Leader Chat on February 25th — BA Skills for 2021</strong></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7eb2387ae73" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Four Ways Great Business Analysts Can Start The New Year Right!]]></title>
            <link>https://ba-squared.medium.com/four-ways-great-business-analysts-can-start-the-new-year-right-9504ed0a9ba0?source=rss-64bd13358666------2</link>
            <guid isPermaLink="false">https://medium.com/p/9504ed0a9ba0</guid>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[business-analyst]]></category>
            <category><![CDATA[agile-development]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[business-data]]></category>
            <dc:creator><![CDATA[Angela Wick — BA-Squared, LLC]]></dc:creator>
            <pubDate>Mon, 11 Jan 2021 21:51:40 GMT</pubDate>
            <atom:updated>2021-01-11T21:51:40.159Z</atom:updated>
            <content:encoded><![CDATA[<h3>Review, Renew, and Reconnect in 2021!</h3><p>Don’t let the new year sneak up on you. Now is the perfect time to follow these four simple ways to start the new year off right, and take charge of what you are getting out of your career and life.</p><h3>Take some time to plan your year!</h3><p>I know this sounds funny, but just like product and project planning, we need to have a vision and intention for the year. Without a dedicated plan, everyone else’s vision and priorities will rule your time and energy. By mid-year, this may leave you feeling lost and without focus, inspiration, or direction.</p><p>A bit of planning can help you serve others while looking out for yourself! What to plan? Ask yourself some powerful questions and create a plan! Journal and reflect on questions like:</p><ul><li>What Type of BA (or business professional, product person, leader, analyst) do I want to be?</li><li>Who do you admire that exemplifies the professional you want to be? What qualities do you admire?</li><li>What skill gaps do you need to fill in to be who you want to be?</li><li>What behaviors do you need to stop, start, and continue to go in the right direction?</li><li>What actions will you take in the near, mid, and long term in 2021 to go in the right direction?</li></ul><p>Need more inspiration? I created a <a href="https://www.ba-cube.com/courses/you-2-0-transformation-challenge-who-do-you-want-to-be/">You 2.0 — Transform Yourself Class</a>, on my BA-Cube.com platform that will help you go much deeper and get your mojo back!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*Z51fsVOLZn2Vd75W.png" /></figure><h3>Renew Your Commitment to Continuous Learning</h3><p>If you are not learning, you are not growing! And learning is an evolution, not a one-time event. Business analysis is a complex and advanced skill set that cannot be learned overnight. It takes practice with each part many times in different contexts, situations, and varying complexity levels to become really good. An intentional mindset and intentional behaviors to continuously learn and improve are what sets the best apart. Learning every day, trying new things every day, and reflecting on what is working and what isn’t is a growth mindset with includes <a href="http://ba-cube.com/">continuous learning at its core</a>.</p><h3>Reset to Your Purpose!</h3><p>Take some time to reflect on what your role is. The Business Analysis role can easily be misunderstood by others and by BAs themselves. Especially when others misunderstand your role and ask for things that do not fit the role. This happens a lot to BAs especially as we impress stakeholders and show we can listen, understand, and solve their problems. So, the trick becomes “taming the beast”; understanding our role and setting the right boundaries to help others understand how we go about helping them without them dictating to us how we do analysis. So, take some time to reset to what your purpose is and how to have a constructive dialog about this with the team and stakeholders. When it seems like they are telling us what to do or even how to do analysis, try to take a step back and understand the intent of what they are needing. They likely have an intent that is difficult to articulate. For example, developers needing “more detail in the requirements” often actually need more context (which ironically is not the detail we think they are asking for). When a business stakeholder asks for a document to review, they might really be looking to better understand how things connect to one another.</p><p>When we know our purpose we can listen differently to these requests from the team and stakeholders, we can follow good analysis and collaboration practices to meet everyone’s needs in a more efficient and effective way!</p><h3>Reconnect With Others</h3><p>2020 wreaked havoc on our professional relationships, the water cooler and elevator chit chat we may have secretly disliked before we now realize was a critical part of the building and maintaining relationships with team members, business partners, and stakeholders. Being all virtual has tested our relationship building skills or perhaps has deleted them altogether. No matter where you feel your professional relationships have gone in 2020 make a commitment to reignite them in 2021.</p><p>Try these steps to get started:</p><ul><li>List the key relationships you need for your project work and your career.</li><li>Make a plan to connect and reach out. It could be a morning “zoom video coffee”, or my favorite, a “walking meeting” where both get out and take a walk casually connecting while getting some movement and fresh air! Just schedule a half hour to reconnect and chat about what is happening in their worlds, and I think you will be surprised how much others want to connect in a different way too!</li><li>Meet with your boss and set your intentions, get their support. Your 1:1 meetings with your boss likely started to feel different being 100% remote in 2020. Take some time to reflect and prep a bit more for your first few in 2021. Plan to discuss your purpose, goals, and learning for the year. Bring your boss into your annual planning from your point of view, not just the development plan you both have to check off the list. Taking time to reflect and prep for this is a gift to yourself!</li></ul><p>I sincerely hope these tips help you make the best year of your career. For more helpful resources to grow your skillsets and career head over to our <a href="https://www.ba-squared.com/resources/">resources page for downloads</a>and check the blog for more articles on similar topics.</p><p>Cheers!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9504ed0a9ba0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Write Good User Stories — An Aggregate of User Story Articles]]></title>
            <link>https://ba-squared.medium.com/how-to-write-good-user-stories-an-aggregate-of-user-story-articles-2065984321c9?source=rss-64bd13358666------2</link>
            <guid isPermaLink="false">https://medium.com/p/2065984321c9</guid>
            <category><![CDATA[product-owner]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[requirements]]></category>
            <category><![CDATA[user-stories]]></category>
            <category><![CDATA[business-analysis]]></category>
            <dc:creator><![CDATA[Angela Wick — BA-Squared, LLC]]></dc:creator>
            <pubDate>Wed, 09 Dec 2020 00:57:26 GMT</pubDate>
            <atom:updated>2020-12-09T00:57:26.816Z</atom:updated>
            <content:encoded><![CDATA[<h3>How To Write Good User Stories — An Aggregate of User Story Articles</h3><h3>Struggling project? Maybe it’s your user stories!</h3><p><strong>Are you on a sinking ship? </strong>If your agile project is struggling to stay above water, it’s possible you have holes in your user stories! Do a quick user story inspection. Do you see any of these warning signs?</p><p><strong>1. Inside Out User Stories</strong>: Do your user stories focus inside out (technology, then user) or outside in (user then technology)? When I coach agile teams, I often see user stories organized by technology component instead of user value. A piece of technology, all by itself, does not typically provide value to the user, especially in our complex integrated environments.</p><p>If applications (a.k.a. stand-alone systems or components of systems) are integrated, then user stories should be integrated. Why? It’s all about user value! When a user makes an online purchase, they do not see separate applications. They browse items, make a purchase, pay, and receive items. <strong>Users do not get value from the web page alone, the product database alone, or the payment processor alone — the user gets value from the integrated experience.</strong> Value from a user perspective comes from integrated user stories vs. single applications.</p><p><strong>2. User Stories Focus on Project Team Tasks</strong>: Again, this approach is not user-focused, it’s development team-focused. When user stories or story sets describe a list of team tasks, they lose their power. If your user stories have names like “code profile page” or “write SQL for DB call” or “map data for credit card validation,” your project might be in trouble.</p><p><strong>Teams need to operate from an outside-in perspective–focusing on the user and what they need. </strong>Team tasks are different than user stories. They may be linked to one another to keep organized, but these team tasks are NOT the user stories.</p><p><strong>3. Huge User Stories: </strong>If your user stories cannot be developed in the planned iteration, they are too big. <strong>SLICE THEM!</strong> But be careful how you slice them. Take note of warning signs #1 and #2–slice user stories by value, not by team tasks or applications. <strong>The entire user experience and all exceptions do not need to be in the same story</strong>. For example, A story about creating a user profile can be sliced into multiple stories. Slice them based on the valuable pieces of data that make up the profile, instead of the application components the profile touches.</p><p><strong>Bailout your sinking ship!</strong></p><h3>Why Agile Teams Need More Than User Stories To Build Great Products</h3><h3>A Tale of Two Teams</h3><h3>Let’s take a look at backlog refinement from two approaches:</h3><h4>Team A</h4><p>A customer provides the team with feedback on their website ordering process and says “I want a button on my email receipt for my order to “view shipping details”. The team prioritizes this and gets to work. They build it quickly in a sprint and release it. Then, weeks later they get feedback to add shipping details to the “My Orders” page. The team thinks okay, let’s get it done, and does it in a sprint and releases. Along with six other seemingly small requests related to shipping information in the next three months. The team has taken requests from the backlog, prioritized them, implemented them, and is doing great agile work right? But, there really isn’t much analysis happening here.</p><h4>Team B</h4><p>Looks at their backlog more holistically and analyze the user problems, observe users, talks to users and analyze the bigger picture of what the users are trying to accomplish. They do this continuously and iteratively, not all in a phase. They deeply understand the users and user problems and discover the user is frustrated by packages arriving when they are not able to be there, and the user wants to update the shipping information after they see the expected arrival date. It could be things like, reroute the package, or add special instructions to leave at the back door. In response, they ideate, analyze the current user workflows and determine a solution to solve the problem; they also find the 18 requests related to this process in the backlog. They analyze and refine the backlog to split out the solution into a few experiments and iterations to learn if their solution is working to solve the problem or not. They learn as they incrementally deliver parts of the solution to users, and continue to refine the backlog as they learn. They are analyzing a holistic backlog with a user problem in mind to solve. They are doing analysis!</p><h3>Agile doesn’t mean skipping the analysis!</h3><ul><li>Team A, never really solved the problem, made the user experience more frustrating without realizing it, and had 15 more requests related to the same problem in the next two months.</li><li>Team B, the competition, solved the problem by focusing on the user problem and analysis of it, rather than working on a list of requests.</li></ul><p>When we skip the analysis (Team A) we are essentially repeating the same pattern that brought us to use agile from the start. Right, agile is supposed to help us build higher quality software that is more relevant to users and faster? Typically, many teams and organizations were frustrated with slow progress on projects. Requirements and Analysis took too long and progress was only seen when the software was built. Therefore, it made sense that agile would “solve the problems”. Historically, the challenges were: a) requirements and analysis took too long, and b) when the product was delivered it wasn’t the right product users needed. Consequently, something has been very flawed with requirements and analysis processes for a long time in many organizations. In transitioning to agile ways of working, let’s not get rid of analysis, however, let’s fix it so that it does not slow teams down, it’s not a phase to be waiting on, and it’s not a one and done process. <strong>Ideally, the analysis should be lightweight, continuous, and user-centered in order to work and leverage the benefits of agile.</strong></p><h3>When teams build great products they develop some common patterns.</h3><ul><li>They deeply understand their users’ goals, pain points, and opportunities.</li><li>They are open to looking at different solutions in order to solve the users’ goals.</li><li>They understand the users’ goals and behaviors within a larger context than the product itself.</li></ul><h3>User Story Efficacy</h3><p>User Stories are intended to be a placeholder for a conversation, and these are conversations about users, their goals, and the bigger context in which users need and use our products. User Stories are not a list of technical action items that the team trudges through to claim they are “getting work done” and being efficient. Teams that are only using user stories as a “to-do” list are missing most of the true benefits of what they are all about and are likely to miss identifying the other analysis that needs to happen in order to build successful products users/customers love.</p><p>User Stories are a placeholder for a future conversation. This leaves substantial analysis incomplete. The acceptance criteria for a user story is a large part of the analysis, but there is more. I am not advocating for big upfront analysis phases and processes, rather more of an iterative, lightweight, and ongoing analysis so that teams can continuously learn about the users and their needs in order to effectively prioritize the backlog and innovate. Even for products and teams working through enhancement and defects lists, understanding the users and their requests deeply and continuously are critical to team efficiency and effectiveness.</p><h3>What does good analysis look like for new and existing products?</h3><ul><li>A holistic backlog that is analyzed and prioritized against a user’s problems/goals, not a list of requests that have come into the team.</li><li>Using lightweight visual models as team assets (hung on the wall or virtual wall) to continuously discuss user scenarios. (like <a href="http://miro.com/">Miro</a> or <a href="http://mural.co/">Mural</a>) Models like: user story maps, user-focused process flows, sequence and state diagrams, user-centered process models, customer journey maps, decision/logic tables, data flow diagrams, etc…</li><li>Frequently observing customers and users in order to understand what triggers them to use your product, understand their emotions and pains before, during, and after a product interaction.</li><li>Bringing the team deep conversations about the users, scenarios, user context, and user pain.</li><li>Prioritizing the teams work based on desired user behaviors and goals within a product</li><li>Analyzing the backlog holistically and aligning it to higher goals, rather than item-for-item as individual requests.</li><li>Finding small experiments to try out that tell the team if they are on the right track to solve the user problem.</li></ul><p>In conclusion, without analysis, it’s easy for teams to build uninspiring products that end up with lots of defects, enhancements, and users that just don’t like the product. Why just build it fast, when you can build the right thing fast with the agile analysis done well?</p><p>Let’s get back to doing analysis well; continuous, fast, and building great products!</p><h3>User Stories: Your First Step Should Always Be Back</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/232/0*XF0N_7HLOxoRQyZN.png" /><figcaption>Click here to access Pathway 9 on BA-Cube to start your User Story learning journey.</figcaption></figure><p>Have you ever played an outfield position in baseball or softball? As an outfielder, your primary responsibility is catching pop flies.</p><p>When you hear the crack of the bat, there’s a moment of panic as you try to figure out where the ball is headed. For young players, their first instinct is always to run forward, which usually leads to the ball flying over their head and the batter advancing several bases.<br>When I played softball, my coach had a mantra for outfielders, “Your first step should always be back!” The coach asked the outfielders to take a quick step back, gauge the ball’s trajectory, and then choose their approach.</p><p>Our backlogs are filled with hundreds of pop flies. And to build better user stories, our first step should always be back. We need to step back, check our sources, and analyze the big picture before we decide how to proceed.</p><h3>Where Do All These Pop Flies Come From?</h3><p>When the backlog items come flying at you, it’s important to take a step back and figure out where they are coming from. Are your stakeholders like methodical ace pitchers or are they wild and erratic? Does the product owner swing at anything or do they evaluate each pitch to see if it’s worth a swing?</p><p>Most backlogs are filled with a random mix of enhancement requests, defects, and ideas submitted by a random mix of stakeholders. If BAs work the backlog as is, without discovery and analysis, the team will struggle. Delivery will be slow, teams will build the wrong things and customers will be frustrated. BAs will be bogged down by a never-ending backlog of more requests and missed requirements.</p><p>Existing backlogs need to be aligned to strategic priorities. BAs need to step back and look at how backlog items connect and how they align with organizational goals. Ideally, BAs analyze and transform these submitted backlog ideas into better user stories that give stakeholders and end-users what they really need versus what they think they need.</p><h3>Work With Your Pitcher And Batter</h3><p>After you step back and really examine the backlog of pop flies, it’s time to tame your wild pitchers and help your batter develop a more selective swing. The discovery process engages project leaders and stakeholders to develop a shared understanding of needs and priorities. It’s all about getting the team thinking and talking.</p><p>Ideally, and good practices are for BAs to use multiple techniques to help teams discover what’s possible and solve problems. The most effective discovery sessions help teams generate ideas, evolve, and innovate. They include collaborative elicitation experiences that inspire meaningful dialog between stakeholders.</p><p>Just sitting around a table and talking isn’t enough — build engaging activities, prepare thought-provoking questions, get people moving by building visual models with sticky notes or drawing on whiteboards, try gamestorming, etc.</p><h3>Go Moneyball</h3><p>As the team moves through the discovery process, it’s important for BAs to make time for Moneyball.</p><p>Do you remember Moneyball? Adapted from a book of the same name, the popular 2011 movie tells the story of a famous baseball guru who stepped back, analyzed the game, and changed the way organizations build winning baseball teams.</p><p>This is the job of every BA. “Go Moneyball” on the backlog and user stories! Analyze the results of the discovery sessions to reveal gaps, make connections, and define the real problems.</p><p>BAs can’t skip analysis. This BA thinking time, outside of the discovery sessions, is where BAs really boost the value they provide. When BAs analyze processes, data, and people, they find impacts and gaps in known requirements and ultimately deliver better solutions. This is the time to pull out your analysis models and techniques to help you think and analyze.</p><h3>Getting The WIN!</h3><p>When BAs take a step back, create engaging discovery activities, and make time for analysis, teams are much more likely to get the win. But remember you don’t just move through these steps once. You don’t just look at the backlog, do one discovery session, then analyze and go — it’s an iterative process.</p><p>BAs repeat the elicitation cycle over and over as they dig deeper into details. You’re really playing ball when you find ways to experiment with and test what you’ve learned from discovery and analysis.</p><p>Good user stories and good requirements in general, always come back to the basics of business analysis and making sure we advocate for the elicitation and analysis pieces of our BA approach. Don’t just chase after every pop fly that comes your way. Make sure your first step is back so you can get the perspective you need to help your organization win.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2065984321c9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Remote Work Is Here To Stay, How Should My Goals Change?]]></title>
            <link>https://ba-squared.medium.com/remote-work-is-here-to-stay-how-should-my-goals-change-189db5c32472?source=rss-64bd13358666------2</link>
            <guid isPermaLink="false">https://medium.com/p/189db5c32472</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[goal-setting]]></category>
            <category><![CDATA[remote-work]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[business-analyst]]></category>
            <dc:creator><![CDATA[Angela Wick — BA-Squared, LLC]]></dc:creator>
            <pubDate>Mon, 02 Nov 2020 19:15:12 GMT</pubDate>
            <atom:updated>2020-11-02T19:15:12.086Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Note: This blog post is an update to an original post from 2019</em><strong><em>: </em></strong><em>I</em><a href="https://www.ba-squared.com/blog/"><em>t’s getting hot in here! Are you feeling the heat as we move into the second half of the year?</em></a></p><h3>Current Scenarios</h3><p>Remote work has given everyone something that used to be lacking, the most valuable commodity that exists, more TIME. What do we do with this time? We have made commitments to ourselves, if I had more time I would? When I have more time I will? And still many of us are facing the challenge of too much to do and too little time because we are homeschooling children, managing a team remotely, or are still trying to get comfortable being at home instead of the office. Still, our projects do require us to put one fire out and another one, maybe even bigger, takes its place.</p><p>Whether too much or too little, we still have to define, track, and achieve our goals as BAs and POs with the time provided. Perhaps getting certified was on your 2020 list and we are approaching November fast. Or maybe this was the year you were going to be promoted to management or leadership and it was stalled because of Covid. Guess what? They still matter! And a new challenge has been created, you have to be your own advocate. YOU have to make it happen. But first, how have the goals changed? What will the goals look like for 2021 with the new normal? Maybe that manager/leader goal changed because performing remotely is not the conventional scenario we once worked in. So, below are some ways to make time to tackle the goals we set at the beginning of the year and some ways to start the process for next year.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*45nnCUjMFCHkw2ZvISbqFA.png" /><figcaption>Make a plan to set your goals for 2021 early.</figcaption></figure><h3>Questions To Ask Yourself</h3><p>Being honest with yourself about your goals can be challenging. Sometimes it’s a matter of too many options. It’s hard to summon the energy for long term goals when the present fires are so demanding. We know that we have to If you are off track, don’t beat yourself up, get curious, and ask yourself a few good questions:</p><ul><li>Do I still want to achieve these goals?</li><li>Will my career benefit from these goals?</li><li>What am I willing to give up to achieve these goals?</li><li>Am I being true to myself and my own needs for continuous learning and growth?</li></ul><p>If you look deep enough, you’ll find plenty of things that should be stopped, put on hold, or not done at all.</p><h3>Try this Approach!</h3><p>Using your current to-do list, mark each item: done, progressing on track, not started, or behind. For the “not started” or “behind” items ask yourself:</p><ul><li>Has something changed to make this no longer valid as a goal?</li><li>Why does it keep getting de-prioritized? And, Am I okay with this?</li><li>What can I do to change the situation?</li><li>Who can I talk to in order to get support for what I think needs to change in priorities?</li><li>And last, what action can I take to change how my year will end if the current path isn’t looking good to meet my goals?</li></ul><p>Turn down the heat by removing all the deadwood. Then, get focused on what’s most important to accelerate your personal growth and delight your customers.</p><h3>Commit to Amping Up Your Collaboration!</h3><ul><li>Using remote tools to make your meetings and collaboration more effective like <a href="https://miro.com/">Miro</a> or <a href="https://www.mural.co/">Mural</a></li><li>Getting into facilitating more collaborative remote meeting modes</li><li>Refining the purpose and objectives of meetings to be more clear</li><li>Building relationships with “walking meetings” and “virtual coffee meetings” which I prefer walking! ;-)</li></ul><p>Commit to time blocks to get your solo thinking and deep thinking work done. Planning your day, week, month to include:</p><ul><li>Be honest about the time you need for your own deep thinking and work</li><li>Block off 2–4 hour time blocks, or a day per week, more if needed to focus and truly dig deep to get the hard but important stuff done</li></ul><p>Make a commitment to health and wellness as they apply to your new needs in a remote work environment. These can include a combination of the following:</p><ul><li>physical well being (sleep, nutrition, movement, and health)</li><li>emotional well being (people, pets, nature)</li><li>spiritual well being (meditation, community, giving)</li></ul><h3>Tools To Start or Continue The Goal Setting Process</h3><ol><li><a href="https://www.ba-cube.com/where-to-start-your-ba-cube-journey/">Pathways</a> — Guides to Start the Learning Journey, <a href="https://www.ba-squared.com/blog/introducing-pathways-ready-set-start/">read the blog post here</a>, and <a href="https://www.ba-cube.com/where-to-start-your-ba-cube-journey/">watch the video here</a>.</li><li><a href="https://www.surveymonkey.com/r/BA-CubeAgileBAQuiz">Agile BA Quiz</a> — Start Where You Are, <a href="https://www.surveymonkey.com/r/BA-CubeAgileBAQuiz">Take the Quiz here</a>. Or Join BA-Cube.com and do our full <a href="https://www.ba-cube.com/courses/ba-po-skills-matrix/">185 Skills — Skill Inventory!</a></li><li>Use the <a href="https://online.flowpaper.com/778f0740/bascatalogsummer20LinksFinal4/#page=1">BA-Cube.com Catalog</a> to chart your course to goals achievement.</li><li>Consider the Upscale Elite 2021 <a href="https://www.ba-cube.com/pricing2/">BA-Cube.com Membership</a> -BA-Cube Annual Everything, + IC-Agile Product Owner Class and Certification, plus User Story Workshop Class live online User Story and IC Agile APO class offered quarterly in 2021. Email us at Info@BA-Squared.com to get this power pack bundle!</li></ol><p>For additional inspiration outside of the industry. Check out more articles about remote work and goal setting here:</p><ul><li><a href="https://thriveglobal.com/stories/how-to-set-meaningful-professional-goals-as-remote-worker/">How to Set Meaningful Professional Goals as a Remote Worker</a></li><li><a href="https://www.forbes.com/sites/forbeshumanresourcescouncil/2020/01/29/four-strategies-for-setting-measurable-goals-in-a-remote-work-environment/#3f1e085e3014">Four Strategies for Setting Measurable Goals In A Remote Work Environment</a></li><li><a href="https://hbr.org/2020/07/does-your-company-have-a-long-term-plan-for-remote-work">Does Your Company Have A Long-Term Plan for Remote Work?</a></li><li><a href="https://medium.com/@remotewrkguides/goal-setting-works-heres-why-9b8db6269f2a">Goal Setting Works Here’s Why</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=189db5c32472" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BAs and POs: Are You Asking the Right Questions?]]></title>
            <link>https://ba-squared.medium.com/bas-and-pos-are-you-asking-the-right-questions-c78c9cb8a13?source=rss-64bd13358666------2</link>
            <guid isPermaLink="false">https://medium.com/p/c78c9cb8a13</guid>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-owner]]></category>
            <category><![CDATA[business-analyst]]></category>
            <category><![CDATA[requirements]]></category>
            <dc:creator><![CDATA[Angela Wick — BA-Squared, LLC]]></dc:creator>
            <pubDate>Fri, 25 Sep 2020 20:40:09 GMT</pubDate>
            <atom:updated>2020-09-25T20:40:09.857Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/735/1*QwNynCzcxMEXFbJKdaz0bA.png" /></figure><p><em>Note: This blog post is an update to a previous blog post </em><a href="https://www.ba-squared.com/blog/5-high-impact-questions-every-ba-using/"><em>Five High-Impact Questions Every BA Should Be Using</em></a><em>. It’s been updated to address how we are working right now.</em></p><h3>The Current Situation</h3><p>Let’s face it, we are under so much deadline pressure that it seems like we don’t have time to ask thought-provoking questions, model, or even think about the problem we are actually trying to solve. Are you really putting energy into providing options and alternatives while strategically selecting the right solution to solve the actual problem? It’s often more of a “FIX THIS NOW … and WITH THIS SOLUTION” sort of order-taking scenario.</p><p>Let’s take a moment to rethink what this deadline-driven, solution demanding, just get it done mentality is doing that challenges our training and experience in business analysis.</p><ul><li>Creating more problems for customers since we are not backing up to see the customer point of view, we are too focused on a fix which means we miss key aspects of context and the real problem to solve.</li><li>Creating the wrong solution leads to process, data, and technical debt. This is when we develop processes that are simply another version of the same process or procedure happening elsewhere, creating inconsistencies, and making matters worse for the customer or another team. We also create process debt in that when we want to make a future change it takes longer to implement due to so many places in the org performing the same process multiple ways. We create data debt the same way and then have “bad data” or poor data quality coming in from multiple disparate processes, then we try to use AI, data analytics, and machine learning and get burned because the data inputs are not the quality needed to meet the goal of such automation. And, technical debt that literally imprisons most of the organization into maintaining software and updating constantly where the code base is so coupled together with band-aids that nothing can get done without needing a ridiculous amount of resources from the entire tech stack and regression testing, documentation, and handoffs between teams.</li></ul><p>Ok, back to “re: we asking the right questions” and deadlines. I think I went off into a dream, I mean nightmare, that you all can relate to… I am back now.</p><h3>Reality “Bites”</h3><p>In reality, our business leaders want outcomes and results, and their requests are expressing the pain of not getting results at any reasonable speed. It is a self-defeating cycle of, their frustration in not getting results, so they try to come up with a solution to be more clear, and a louder voice to get it completed sooner. Again, they don’t really want THAT SOLUTION faster, they want RESULTS faster. Getting the results means asking the right questions to truly solve the right problem with the least amount of work and not creating the process, data, and technical debt… all of which lead to “customer debt”. “Customer debt” is when we build experiences through our process, data, and technology that disenfranchise our customers such that their positive experiences with us dwindle and we have a lot of work to do to reverse the negatives and bring them more positives before they leave us for the competition.</p><p>So, the next time you get a new request, perhaps a technical need, defect fix, process change, and it comes to you loaded with an urgent deadline and pre-defined solution; take a few moments and think about the powerful high impact questions you can ask that can actually help everyone get a shared understanding of the problem and customer impact, then work with the team to identify a few potential solutions to solve the problem and what the smallest, fastest thing that you can do to solve the problem and make real progress towards the customer result. This is prioritizing OUTCOMES over OUTPUTS! Business leaders will favor this approach far more than the exact solution they demanded that won’t create a business result in the end.</p><p>Success or failure often hinges on the questions we ask throughout the project lifecycle. It sounds a bit dramatic, but I’ve witnessed it many times — a single, thought-provoking question that changed the trajectory of a conversation, opened a floodgate of new ideas, or magically simplified a complex problem. Great business analysts fill their toolbox with high-impact questions! BAs use these questions strategically.</p><p>They figure out the right way to ask the question and the right way to gather the answers. They also consider the best time, place, and audience for each question. What is the definition of high-impact questions? Consider the following regarding high-impact questions:</p><ul><li>Are difficult to answer</li><li>Create moments of silence</li><li>Inspire responses like, “Hmmmm, let me think about that…”</li><li>Stir up emotions and politics</li><li>Spark analysis</li><li>Encourage stakeholders to provide context, solve problems, make good decisions</li><li>Generate deep, meaningful, interactive discussions that spawn high-value systems, processes, and products</li></ul><h3>Five Excellent High-Impact Questions</h3><p><strong>Tell me about your pain points and challenges with the system/process/product.</strong></p><p>Yes, I know this is not in the form of a question, but this phrasing indicates your interest in details and deep discussion instead of a short, off-the-cuff list. Starting from a place of pain gives people a chance to get their frustrations on the table right away. It inspires storytelling that gives context to stakeholder concerns and creates a shared understanding of each stakeholder’s priorities.</p><p><strong>If this system, product, the process worked as good as it could, what would that look like?</strong></p><p>This question approaches pain points and challenges from a positive angle and promotes problem-solving. Stakeholders will reveal their solution priorities and their definition of success. Use this question to brainstorm enhancements, features, or to diffuse disagreements about priorities, needs, or decisions.</p><p><strong>What are the top 3 things you would change?</strong></p><p>This question can be used in multiple ways throughout the project lifecycle. You can use it in discussions about systems, features, products, or processes, or you can use it to focus on internal processes and issues. This question works in the initial stages of the project when you are defining needs, and is equally useful during a retrospective or “lessons learned” discussion. It also works well evaluating how a current or newly implemented solution is working regardless of if changes are being asked for.</p><p>Asking users to limit their change list to 3 items, forces stakeholders to prioritize and focus on what’s most important. Be sure to spend time diving into the why for each item. When stakeholders reveal their top 3 things and explain why, you will begin to understand their values, priorities, and pain points. You’ll also begin to see how each stakeholder is connected.</p><p><strong>What things would you make sure not to change?</strong></p><p>This question works well when you need your team to focus on the positive. It reveals what each stakeholder appreciates about the current process, system, or product. You begin to understand stakeholder values and priorities. You discover stakeholder fears and define innovation boundaries. Digging into the why of each “please don’t change this” item, will uncover stories (requirements in context) of what’s working well and might spark ideas for enhancements or new products/processes/systems. You might also find conflict here…things in this list might also be in the top three that others want to change, which generates good discussion.</p><p><strong>If the project or enhancement does not happen, what impact would that have for you?</strong></p><p>This question, when discussed in a group setting, pulls each stakeholder out of their silo. They begin to discover gaps in their understanding of the big picture. As the stakeholders reveal their needs. Some may discover they do not need to actively participate in the project. Others may discover they underestimated their impact. This question often generates meaningful examples and scenarios that stick in people’s minds much longer than words in a giant requirements document.</p><h3>Benefits Of High-Impact Questions</h3><p>High-impact questions provide multiple benefits that tip the project balance to success. Here are just a few:</p><ul><li>Silence: High-impact questions allow the stakeholder or group to think, go back in their mind, come back and be with a space in their mind to really process thoughts and come to conclusions. Silence helps us get better requirements that are better thought out. It reduces the risk of changing requirements by giving stakeholders time to dive below the surface requirements earlier in the project.</li><li>Trust: High-impact questions build strong relationships with stakeholders and users. Deeper dialog makes them feel connected and understood, which creates trust and boosts morale.</li><li>Ownership: High-impact questions help our stakeholders own their involvement in the solution. Rather than cast blame or incite conflict, high-impact questions help stakeholders communicate and articulate the real problem they want to solve.</li></ul><h3>Be Strategic</h3><p>To maximize the benefits of high-impact questions, use them strategically. Consider the following:</p><ul><li>Why are you using the question? What do you hope it reveals? How will it help your team boost end-user value?</li><li>Who should be answering the question? All stakeholders or just a subset? Users or management?</li><li>How will you ask the question and how will you gather the answers? One on one, small group, large group? Do you need to allow opportunities for introverts by using surveys or individual brainstorming on sticky notes, then sharing with the large group?</li><li>Can you use the questions to help stakeholders focus on the end user’s perspective rather than the team’s perspective?</li><li>If you are in a group when you ask these questions, take the time to observe body language. Who is agreeing with the speaker, who is disagreeing, who looks angry or frustrated? What does body language reveal about your stakeholders’ needs, values, and priorities?</li></ul><p>High-impact questions encourage teams to talk early and often — minimizing the risk of identifying expensive, show-stopping issues late the project. Use them strategically to help your team build the right solutions, faster! Test one of these questions in your next elicitation session and let me know what happens, or share your favorite high-impact questions with <a href="https://www.linkedin.com/in/angelawickcbap/">me on LinkedIn.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c78c9cb8a13" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is a Modern BA?]]></title>
            <link>https://ba-squared.medium.com/what-is-a-modern-ba-f070d9c853a8?source=rss-64bd13358666------2</link>
            <guid isPermaLink="false">https://medium.com/p/f070d9c853a8</guid>
            <category><![CDATA[agile-transformation]]></category>
            <category><![CDATA[modern-agile]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[business-analytics]]></category>
            <dc:creator><![CDATA[Angela Wick — BA-Squared, LLC]]></dc:creator>
            <pubDate>Wed, 19 Aug 2020 20:18:10 GMT</pubDate>
            <atom:updated>2020-08-19T20:18:10.398Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bR5Vmg4L6UiL77DUeL7iFw.jpeg" /></figure><h3>The Definition of a Modern BA</h3><p>A Modern BA is a BA who leads a group through a problem solving and solution process with the customer/user at the center of the analysis, knowing that all other details will follow. A deeper dive into what constitutes a Modern BA is a bit of a longer listicle. A Modern BA:</p><ul><li><strong>Acts</strong> as if the highest value of their role is to make the customer’s interactions with the organization/product/service better, and incorporates this into everything they do!</li><li><strong>Enables</strong> a combination of relationship, influence, and analytical skills to guide a group through making users/customers interactions with the organization/product/service better, all from the customer’s point of view.</li><li><strong>Uses</strong> incremental and experimental processes to learn more about the customer and their needs as the team works on solutions.</li><li><strong>Understands</strong> and behaves as if meetings and documents are simply tools to help stakeholders and teams solve problems, not the job of the BA.</li><li><strong>Owns</strong> the problem solving and analysis process while making good use of everyone’s time, adding value to stakeholders and team members’ time with a shared sense of moving forward.</li></ul><h3>The Do’s and Don’ts of a Modern BA</h3><p>Along with this deeper dive into what makes up a Modern BA, there are some guidelines to follow. These are called the DO’s and DON’Ts of Modern BAs.</p><p><a href="https://www.ba-squared.com/blog/what-is-a-modern-ba/">What is a Modern BA? | BA-Squared</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sOmzJDBu4nnYws1aMUIUiw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L7CbQmucBpJddaI69m9Fkg.png" /></figure><h3>What the Leaders and Managers Know</h3><p>If you feel others see your role and what you do as more aligned to the “DONT” columns, <strong>be the change and show them another way</strong>, keep sticking to the intent of satisfying the needs of the users and understanding the problem over all else.</p><p>We have asked BA Managers and Practice Leaders all over the globe what their best performing BAs do, and we have seen it in our 2019 State of Agile Analysis Study, and in my coaching, consulting and training work.</p><p>Download the full report <a href="https://www.ba-squared.com/report/">here</a> <a href="https://www.ba-squared.com/report/">.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f070d9c853a8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Top 10 Business Analysis Skills For 2020 and Beyond]]></title>
            <link>https://ba-squared.medium.com/the-top-10-business-analysis-skills-for-2020-and-beyond-df9cf40b441?source=rss-64bd13358666------2</link>
            <guid isPermaLink="false">https://medium.com/p/df9cf40b441</guid>
            <category><![CDATA[ba-training-online]]></category>
            <category><![CDATA[product-owner]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[business-analyst]]></category>
            <category><![CDATA[business-analysis]]></category>
            <dc:creator><![CDATA[Angela Wick — BA-Squared, LLC]]></dc:creator>
            <pubDate>Mon, 20 Jul 2020 19:50:58 GMT</pubDate>
            <atom:updated>2020-07-20T19:50:58.085Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/735/1*AgXdba8GK2wc2_nLgjFyVQ.png" /></figure><h3>Business Analysis Skills from 2012 to 2020</h3><p>In 2012 I wrote a blog for the <a href="https://www.batimes.com/angela-wick/the-top-10-business-analysis-skills-for-2012.html">BA Times</a> on the top 10 skills for BAs. It’s time to see how this has evolved and our roles have become more valuable and essential as a result! To begin, a clarification on the BA role from then to now:</p><ul><li>In 2012 I called the BA as “A broker of information, getting big picture details from a variety of people, groups, executives, subject matter experts, vendors, technical resources, etc . . .”</li><li>In 2020, I am updating this definition to “A catalyst of problem-solving and effective decision making; facilitating problem-solving and decision making on desired strategic, operations, customer experience, and systematic changes and aspects of how organizations serve their customers and operate at all levels.”</li></ul><p>In 2012, I stated that the following are the key drivers of business analysis in organizations, and this has NOT changed! These focus areas help organizations pivot quickly and drive their digital transformations to better compete and serve customers.</p><ul><li>Business Agility</li><li>Innovation</li><li>Engagement of stakeholders to drive agility and innovation</li></ul><p>The needed skills to meet these trends remain much the same! Read on to see how I have modernized the lens in which we see these skills.</p><h3>Top 10 Skills for BAs</h3><p><strong>1) Conceptual Modeling Skills To Drive Deep Conversations</strong></p><p>Engage your stakeholders with more meaningful dialog! Conceptual Modeling of the customer and business view of the problem and solution has always been a critical tool to help bring business, technology, and delivery groups together in delivering great products and solutions. These are not the technical architecture and data context diagrams, we are talking here about customer experience design and business design. Technical and data diagrams have their place, but the critical skill I am seeing as a gap in BA skill sets is the customer and business view (vs. technical view) of the problem and solution scope, this will be critical to engaging stakeholders and setting the stage for innovation. <strong>In 2020, we see an even greater need to ensure this can be done in a remote/virtual environment; this means upskilling your remote BA skills.</strong> Remote BA skills include learning to collaborate in a virtual modeling environment and facilitating online meetings where virtual modeling tools are used for the purpose of getting deep conversations going.</p><p><strong>2) Communicating Details and Concepts</strong></p><p>Similar to the conceptual modeling skills is communicating various levels of detail appropriate to the audience. Again, it is about the conversations BAs are having, at all levels. And these conversations are for the purpose of facilitating problem-solving and great customer/user experiences. These are not conversations to confirm what should be written in a spec document. Where I see the gap today is that details are not organized to be digestible and understandable to many audiences and there may be a lack of conceptual and context to accompany the details. Without the concept and context information, the details — even when well organized — may not be understood to get the needed conversations from the team and stakeholders.</p><p><strong>3) Curiosity</strong></p><p>How curious are you as a BA? This has always been a critical skill for BAs. Ensuring curiosity in finding the root cause of the problem or opportunity, getting the right audience, usage, context, purpose understood by everyone requires a strong level of curiosity. Curiosity is critical for BAs wanting to build competency and skills in the world of mobile apps, cloud computing, digital, and continuing agile practices. Curiosity will make some of the unknowns of today easier to work within, a curious mindset will take BAs into communicating the unknown and help organizations innovate.</p><p><strong>4) Decomposing the Abstract into Details</strong></p><p>I have to call this out separately from Conceptual Modeling and Communicating Details and Concepts. The same themes are in play yet executed a bit differently and in different scenarios. Decomposing the abstract into details is also referred to as “critical thinking” and sometimes “system thinking”; taking something large, ambiguous, and abstract and breaking into smaller pieces, patterns, and views. It is about helping others see the details and big picture from different perspectives, helping stakeholders with varying points of view and priorities see where their details and others fit into the bigger picture. This is especially true for Agile BAs where defining increments of “feedback-able” work for the team, user story splitting, and user story mapping become some key techniques for BAs to master. The important piece here is that this decomposition is from a user perspective, not a system perspective.</p><p><strong>5) Mentoring and Coaching</strong></p><p>As the BA role becomes increasingly more valued in organizations, two things will happen: 1) Organizations will need a career path for Sr. BAs, and 2) Organizations will need to develop internal strategies to develop more talent in the BA role and Sr. level skill set. Mentoring and coaching skills are key for Sr. BAs in both of these strategies. <strong>Mentoring and coaching done by Sr. BAs will develop leadership competencies in the Sr. BAs while developing BA competencies in new or more inexperienced BAs in the organization.</strong> Senior BAs who have the opportunity to mentor and coach will develop further leadership competencies needed to elevate the competencies of the BA team as a whole.</p><p><strong>6) Communicating Risks</strong></p><p>Everything about the risk to BAs is about the risk to the customer! A BA needs to focus on risks to the customer and the value customers get from the products, services, and solutions. BAs are in a prime position to see the details and big picture view, and see the customer perspectives, identifying cybersecurity risks, data risks, and of course the user experience risks of the new process or solution making the customer experience worse than the previous one! I find that BAs have an intuitive sense of this, but often struggle to communicate the risk in a way that gets leadership attention. In order to get leadership attention, BAs will need to develop skills in communicating the true customer and business impact of the risk. This means going beyond communicating in terms of the features and functionalities of the processor software and going beyond that, there is not enough time for requirements to be done right. For example, when the functionality of a point of sale application has a requirements conflict in the process of accepting payment from customers, the focus needs to turn to the impact of the conflict on the customer and customer service representative’s ability to serve the customers and the customer experience vs. the technical details at risk of the requirement. In the heat of requirements and design details, we often let the details drive risk discussions and never get to the bottom line impacts that can really propel leaders to make the right decisions.</p><p><strong>7) Meeting Facilitation &amp; Leveraging the “parking lot”</strong></p><p>Are you running your meetings or are meetings and stakeholders running you? Do you truly have a clear purpose and objective for the meeting? Are you making good use of everyone’s time? Are you owning the meeting and the objective? Many BAs get into tough situations in requirements meetings and feel that other agendas and personalities are driving their meetings astray. Using a “parking lot” (simple visual list of items that do not fit into the meeting objective to be followed up on or scheduled into another meeting) to manage and control the meeting agenda, content, level of detail and difficult personalities is a key strategy. Most importantly, make sure that the parking lot is visible (in a virtual board the group sees during your remote meeting). Having the parking lot in your notebook or on your laptop does not show others that you have their ideas and concerns captured to discuss at a later time. <strong>Be empowered to take control of your meetings!</strong></p><p><strong>8) Change Management</strong></p><p>Embracing the BA role as an agent of change will continue to show the value the BA role brings to the organization. The BA role is about bringing the most value possible in a solution to address customer value and business change. The role of a change agent in the BA is critical to ensuring all impacted parties are ready for the changes needed to accept the solution. Understanding how changes and solutions impact the stakeholders’ operations, processes, attitudes, and behaviors is a key skill in maximizing the success of the new solution and the business value it brings.</p><p><strong>9) Asking WHY?</strong></p><p>I love the word “Why”, but hate to use it. My challenge to readers of this blog is to help one another find ways to ask “Why”. Many times using the word “Why” can come across as offensive to the other person, it can seem defensive and the other may wonder <em>why </em>(no pun intended) you are asking. Finding different ways to ask “why” can alleviate this dilemma. My favorite ways to ask “Why?”: Tell me more about what is behind the need for ABC? What does success look like? What would happen if this project does not get implemented? What are your favorite ways to ask why?</p><p><strong>10) Remote Meeting Collaboration</strong></p><p>BAs need to lead stakeholders to a deeper level of engagement. In a remote work world, this means completely ramping up how we engage others in our remote meetings. Conference calls are no longer about voice only, or voice + video. Now, it is about the tools you engage everyone to use during a call! Tools that allow creative brainstorming, group modeling, groups drawing mockups together online, voting on priorities online, and virtual sticky notes to facilitate powerful conversations with various points of view. Tools that show a transparent backlog, let the group do user story mapping together online, user story writing workshops online, and ideate together while all working remote!</p><p>No matter what type of BA, no matter what the industry, these skills in 2020 will set your teams up for deeper engagement, innovation, and agility.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df9cf40b441" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile Teams Need More Than User Stories To Build Great Products | BA-Squared]]></title>
            <link>https://ba-squared.medium.com/agile-teams-need-more-than-user-stories-to-build-great-products-ba-squared-2602d1a293b4?source=rss-64bd13358666------2</link>
            <guid isPermaLink="false">https://medium.com/p/2602d1a293b4</guid>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Angela Wick — BA-Squared, LLC]]></dc:creator>
            <pubDate>Tue, 30 Jun 2020 16:21:37 GMT</pubDate>
            <atom:updated>2020-07-08T22:15:27.622Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*y3LGc6Q1DN6fkuJm.jpg" /></figure><h3>Let’s take a look at backlog refinement from two approaches:</h3><p>A customer provides the team with feedback on their website ordering process and says “I want a button on my email receipt for my order to “view shipping details”. The team prioritizes this and gets to work. They build it quickly in a sprint and release it. Then, weeks later they get feedback to add shipping details to the “My Orders” page. The team thinks okay, let’s get it done, and does it in a sprint and releases. Along with six other seemingly small requests related to shipping information in the next three months. The team has taken requests from the backlog, prioritized them, implemented them, and is doing great agile work right? But, there really isn’t much analysis happening here.</p><p>Looks at their backlog more holistically and analyzes the user problems, observes users, talks to users, and analyzes the bigger picture of what the users are trying to accomplish. They do this continuously and iteratively, not all in a phase. They deeply understand the users and user problems and discover the user is frustrated by packages arriving when they are not able to be there, and the user wants to update the shipping information after they see the expected arrival date. It could be things like, reroute the package, or add special instructions to leave at the back door. In response, they ideate, analyze the current user workflows and determine a solution to solve the problem; they also find the 18 requests related to this process in the backlog. They analyze and refine the backlog to split out the solution into a few experiments and iterations to learn if their solution is working to solve the problem or not. They learn as they incrementally deliver parts of the solution to users, and continue to refine the backlog as they learn. They are analyzing a holistic backlog with a user problem in mind to solve. They are doing analysis!</p><h3>Agile doesn’t mean skipping the analysis!</h3><ul><li>Team A, never really solved the problem, made the user experience more frustrating without realizing it, and had 15 more requests related to the same problem in the next two months.</li><li>Team B, the competition, solved the problem by focusing on the user problem and analysis of it, rather than working on a list of requests.</li></ul><p>When we skip the analysis (Team A) we are essentially repeating the same pattern that brought us to use agile from the start. Right, agile is supposed to help us build higher quality software that is more relevant to users and faster? Typically, many teams and organizations were frustrated with slow progress on projects. Requirements and Analysis took too long and progress was only seen when the software was built. Therefore, it made sense that agile would “solve the problems”. Historically, the challenges were: a) requirements and analysis took too long, and b) when the product was delivered it wasn’t the right product users needed. Consequently, something has been very flawed with requirements and analysis processes for a long time in many organizations. In transitioning to agile ways of working, let’s not get rid of analysis, however, let’s fix it so that it does not slow teams down, it’s not a phase to be waiting on, and it’s not a one and done process. <strong>Ideally, the analysis should be lightweight, continuous, and user-centered in order to work and leverage the benefits of agile.</strong></p><h3>When teams build great products they develop some common patterns.</h3><ul><li>They deeply understand their users’ goals, pain points, and opportunities.</li><li>They are open to looking at different solutions in order to solve the users’ goals.</li><li>They understand the users’ goals and behaviors within a larger context than the product itself.</li></ul><h3>User Story Efficacy</h3><p>User Stories are intended to be a placeholder for a conversation, and these are conversations about users, their goals, and the bigger context in which users need and use our products. User Stories are not a list of technical action items that the team trudges through to claim they are “getting work done” and being efficient. Teams that are only using user stories as a “to-do” list are missing most of the true benefits of what they are all about and are likely to miss identifying the other analysis that needs to happen in order to build successful products users/customers love.</p><p>User Stories are a placeholder for a future conversation. This leaves substantial analysis incomplete. The acceptance criteria for a user story is a large part of the analysis, but there is more. I am not advocating for big upfront analysis phases and processes, rather more of an iterative, lightweight, and ongoing analysis so that teams can continuously learn about the users and their needs in order to effectively prioritize the backlog and innovate. Even for products and teams working through enhancement and defects lists, understanding the users and their requests deeply and continuously are critical to team efficiency and effectiveness.</p><h3>What does good analysis look like for new and existing products?</h3><ul><li>A holistic backlog that is analyzed and prioritized against a user’s problems/goals, not a list of requests that have come into the team.</li><li>Using lightweight visual models as team assets (hung on the wall or virtual wall) to continuously discuss user scenarios. (like or ) Models like: user story maps, user-focused process flows, sequence and state diagrams, user-centered process models, customer journey maps, decision/logic tables, data flow diagrams, etc…</li><li>Frequently observing customers and users in order to understand what triggers them to use your product, understand their emotions and pains before, during, and after a product interaction.</li><li>Bringing the team deep conversations about the users, scenarios, user context, and user pain.</li><li>Prioritizing the teams work based on desired user behaviors and goals within a product</li><li>Analyzing the backlog holistically and aligning it to higher goals, rather than item-for-item as individual requests.</li><li>Finding small experiments to try out that tell the team if they are on the right track to solve the user problem.</li></ul><p>In conclusion, without analysis, it’s easy for teams to build uninspiring products that end up with lots of defects, enhancements, and users that just don’t like the product. Why just build it fast, when you can build the right thing fast with agile analysis done well?</p><p>Let’s get back to doing analysis well; continuous, fast, and building great products!</p><p><em>Originally published at </em><a href="https://www.ba-squared.com/blog/agile-teams-need-more-than-user-stories-to-build-great-products/"><em>https://www.ba-squared.com</em></a><em> on June 30, 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2602d1a293b4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Velocity & User Stories — Too Many Teams Are Looking At It Wrong!]]></title>
            <link>https://ba-squared.medium.com/velocity-user-stories-too-many-teams-are-looking-at-it-wrong-b06f466f9b12?source=rss-64bd13358666------2</link>
            <guid isPermaLink="false">https://medium.com/p/b06f466f9b12</guid>
            <category><![CDATA[user-stories]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[product-owner]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Angela Wick — BA-Squared, LLC]]></dc:creator>
            <pubDate>Mon, 15 Jun 2020 18:15:30 GMT</pubDate>
            <atom:updated>2020-06-15T18:15:30.587Z</atom:updated>
            <content:encoded><![CDATA[<h3>Velocity &amp; User Stories — Too Many Teams Are Looking At It Wrong!</h3><h3>Velocity — What Does It Really Mean?</h3><p>Ask just about any agile team what metrics they track and “velocity” comes out. Teams rally around increasing their velocity, focusing on speed and hanging their team successes on this metric. Additionally, many teams report their velocity increase to leadership claiming agile success! Some may even go as far as comparing and benchmarking against other teams. For the former, I challenge this approach with the following question: What results are actually being delivered? How can you link this to the organization’s strategy? Other teams use it as a data point, a measurement that provides some information on their team processes, trends, and where they might look to continuously improve. A single data point that when looked at with other information might provide some insight into the team’s continuous improvement.</p><h3>Reframing Velocity for Agile Teams</h3><p>Alternatively, I want to provide another lens on what velocity can mean to teams and one that I have found really resonates with executives as organizations measure whether or not agile is really making a difference and delivering more agility to the organization. Predominantly, It’s about using velocity as a means to get closer to value delivered, rather than simply a speed metric. After all delivering software fast does not equal delivering software that is valuable or meaningful and advancing organizational results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*VwI8Gl6cGu0hG6yd.png" /><figcaption>Scrum, Inc. definition of Velocity.</figcaption></figure><p>I’ll start with a baseline definition of Velocity. Scrum, Inc. defines it as Velocity is a measure of the amount of work a Team can tackle during a single Sprint and is the key metric in Scrum. Velocity is calculated at the end of the Sprint by totaling the Points for all fully completed<a href="https://www.scruminc.com/independent-user-stories/"> User Stories</a>. The Agile Alliance defines velocity as At the end of each iteration, the team adds up effort <a href="http://guide.agilealliance.org/guide/nuts.html">estimates</a> associated with <a href="http://guide.agilealliance.org/guide/stories.html">user stories</a> that were <a href="http://guide.agilealliance.org/guide/sashimi.html">completed</a> during that iteration. This total is called velocity.</p><p>Like many concepts when teams start to move in an agile direction, the basic definitions become meanings all their own. Additionally, creating a team’s own definition of things can at times be very productive and other times be an unconscious step towards an anti-pattern. An anti-pattern is when we do something that seems logical at the time but creates results counter to the bigger picture goals. This often happened when teams try to become more agile, yet adapt their practices because they have found a “unique” aspect they find themselves in that call for an adaption to the practice. What the teams do not realize is that the adaption seems logical, but goes against the very agile values that create results. Therefore, agile teams should adopt practices to fit their own context, but too many to do while compromising the values that an agile approach is built upon, and many do not realize they are compromising their results, but claim they are “being flexible” and “self-organizing”. These are also agile natured principals! But are they to their own detriment?</p><h3>Velocity and User Story Connection</h3><p>For Velocity, many teams miss the user story part of the definition. Some teams are calling all work items completed user stories and claim improvements in team velocity, yet the way the team is using user stories may be incorrect and compromising the idea of “team improvement and success” as viewed by others and executives. Many teams are focused on points and the pointing process to help velocity, however, in this blog, I want to address the User Story part of the velocity equation. Using user stories as they are intended to be done brings a different view of velocity.</p><p>Think of velocity for a moment as a measurement of how often the team is getting user feedback on real working software the team is working on. When we look at the agile values and principles it is all about “working software”, “continuous delivery” and “getting feedback from real users”. This does not mean getting feedback from a downstream team dependent on a piece of software. Many teams are simply creating software, continuously, but it is NOT working software that a user could provide feedback on for many iterations/sprints. It may be a piece that then goes to another team and after many teams touch it (all counting velocity for their own piece) they may be able to get some real user feedback. Therefore, if executives and customers deserve accurate reporting on how fast software is being built, how is this a true measurement of velocity? It’s not! If a user cannot give feedback, then it is not DONE, and we should not count it as velocity.</p><h3>Feedback Velocity</h3><p>To help with this, I will often call it “feedback velocity” not to be confused with a “poor definition” of velocity that may already be in practice. By looking at how often the team is getting feedback on working software, from end-users; the team can more accurately reflect how fast they are delivering working software and connect better with executives on reporting the pace of software development. Whereas measuring velocity on a part that is dependent on other parts to get user feedback is not an accurate measurement of true velocity.</p><p>Let’s ask ourselves for a moment, How long are teams really willing to work without knowing they are on track from a user goal perspective? More often the feedback will strongly correlate to the value delivered by the team. This creates less pain in architecture rework and allows for changing requirements. Working without user feedback increases the risk that the infrastructure, architecture, and data structures created need to be rethought through. It’s detrimental for a team to tell a business leader after the software is complete that what they really needed would require a completely different architecture or infrastructure! The rework is often too expensive and business teams and customers are forced to “live with it”.</p><h3>User Story Quality</h3><p>Now back to user stories. If User Stories are the unit that is measured for Velocity, then we better have this input done right! User Stories are something many teams struggle with in order to make this critical input to velocity a meaningful measurement. Below I’ve outlined some user story anti-patterns that cause velocity measurements to go awry:</p><ul><li>User Stories written as tasks to be assigned to a team member</li><li>User Stories that are a piece of working software, not something that you could show a user and receive feedback on.</li><li>User Stories are not “releasable” on their own. A team and PO can choose when to release them and wait, but they should be releasable as a unit of work on its own.</li></ul><p>What User Stories should be:</p><ul><li>A user goal/action that we want to implement or improve (the story is about THE USER, not the system or a component of a system, a phase, another team, or a team member.</li><li>A unit of work, representing a user action/goal that is “demo-able” to end-users for feedback</li><li>A unit of work that the team works on, not an individual</li></ul><p>When these characteristics are met, the team can truly rally success around real, working software, that they can receive feedback on. They can release whenever they want and obtain feedback as often as they want on exactly what they are working on. This is what VELOCITY is all about!</p><p>In conclusion, if your team or organization is employing user stories incorrectly, then you are also likely not reporting velocity correctly. You are at risk for your executive team to question your “success”. Do they see value delivered to your customers faster?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b06f466f9b12" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Top Professional Skills Today — How You Can Leverage Them as a Modern BA!]]></title>
            <link>https://ba-squared.medium.com/the-top-professional-skills-today-how-you-can-leverage-them-as-a-modern-ba-96db0b59ac67?source=rss-64bd13358666------2</link>
            <guid isPermaLink="false">https://medium.com/p/96db0b59ac67</guid>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[business-analyst]]></category>
            <category><![CDATA[business-analyst-training]]></category>
            <dc:creator><![CDATA[Angela Wick — BA-Squared, LLC]]></dc:creator>
            <pubDate>Wed, 03 Jun 2020 19:49:31 GMT</pubDate>
            <atom:updated>2020-06-03T19:49:31.927Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Top Professional Skills Today — How You Can Leverage Them as a Modern BA!</h3><h3>Being a Business Analyst is a great career choice!</h3><p>When you prioritize continuous learning and growth, you will learn skills that will let you take your career in a multitude of directions. Much of the success is dependent on one’s personal drive, motivation, and accountability. However, creating a consistent practice of outlining and defining action items that can attribute to leveling up on skills will help track your progress and bring you opportunities as a BA and far beyond. You will be put on the most challenging projects, the most innovative, and build leadership skills that can catapult careers.</p><p>Earlier this year LinkedIn <a href="https://learning.linkedin.com/blog/top-skills/the-skills-companies-need-most-in-2020and-how-to-learn-them">posted the most in-demand skills for 2020</a>, and Business Analysis was the biggest mover, it went up ten spots to #6! And, being a BA isn’t just about Business Analysis, there are other skills on this list that help BAs thrive and advance as well. Successful careers are made of a combination of soft and hard skills. According to the 2020 skills report by LinkedIn earlier this year:</p><ul><li>The top SOFT skills companies need include <strong>CREATIVITY</strong>, <strong>PERSUASION</strong>, <strong>COLLABORATION,</strong> and <strong>ADAPTABILITY</strong>.</li><li>The top HARD skills companies need include <strong>CLOUD COMPUTING</strong>, <strong>ARTIFICIAL INTELLIGENCE,</strong> and <strong>ANALYTICAL REASONING</strong>.</li></ul><p><strong>Creativity.</strong> People will generally come right out say, “I’m not creative!” Alternatively, they will say, “I’m a visual person!” This is not what is meant by creativity, particularly in the BA realm. What it truly means is creativity in terms of how you deliver information. What tools are you using to accommodate all levels of creativity in others? Including people you manage or people to whom you report, or even stakeholders. Recently, I created a few new resources that help with creative brainstorming. Specifically, an <a href="https://www.ba-cube.com/wp-content/uploads/2020/03/EmpathyMap2.pdf">empathy mapping guide to foster understanding</a> between team members.</p><p><strong>Persuasion</strong> not control. This is a big one, help others make decisions by helping them understand how or why they feel a certain way about something. The key here is to keep going once you come to a decision that is not the one you want from that person. Understanding where they are coming from is important in seeing the potential to change one’s mind. Two distinctive resources to build those persuasive skills are the Building Relationships series, <a href="https://www.ba-cube.com/wp-content/uploads/2019/01/BuildingRelationships-TheMindset.pdf">The Mindset</a>, and the <a href="https://www.ba-cube.com/wp-content/uploads/2019/01/BuildingRelationships-TheMeetUp.pdf">Meet Up</a>.</p><p><strong>Collaboration</strong>. Definitely a soft skill. You know when you see it or feel it. It’s a flow, a consensus, and freedom to collaborate that works for everyone. As BAs we want people to show up that is a sure sign of being collaborative. It seems like such a small thing but showing up is the biggest thing. Check out this resource template on <a href="https://www.ba-cube.com/wp-content/uploads/2019/02/Kupe-4-Ways-to-Engage-Stakeholders.pdf">Ways to Engage Stakeholders</a> for some great ideas on fostering collaboration. How can you change your approach and be more collaborative?</p><p><strong>Adaptability.</strong> This is just a fancy word for flexibility. Are you flexible? When circumstances change how do you react? How did you react in March when most likely you went from being in the office all the time to working remotely? Did you adapt quickly or slowly? Adaptability is a hidden superpower that all BAs should tap into. When we are flexible we are approachable, negotiable, and more fun to work with. In my <a href="https://www.ba-cube.com/wp-content/uploads/2018/08/LeadersGuide-to-InterviewingBAs-1.pdf">Leaders Guide to Interviewing BAs</a>, information on how to find out if someone is adaptable is included.</p><h3>Now let’s talk about those hard skills. By hard, it is not meant to be difficult. It is meant to be tangible. You can touch, see, and feel it.</h3><p><strong>Cloud Computing</strong>. Well duh? It seems like an obvious one for BAs. Doing requirements usually takes care of this aspect of a software project. Given the ubiquity of cloud computing, BAS must be prepared for the cloud and understand how it affects their roles. As a valuable problem solvers within all organizations, BAs help streamline and optimize business processes for deployment in the cloud. With that come all the decisions of how, when, and why to go to the cloud. Check out this new video on decision-making using the <a href="https://www.ba-cube.com/ba-cube-resources/">Cynefin model, a conceptual framework.</a></p><p><strong>Artificial Intelligence</strong>. In today’s world, this will only become more important. After witnessing the Space X launch this weekend, we can see how far this goes in technology and exploration. Also, with cybersecurity being such a hot topic. Artificial intelligence (AI) and machine learning (ML) are playing an increasing role in cybersecurity, with security tools analyzing data from millions of cyber incidents, and using it to identify potential threats. The demand for BAs to understand and respond to this increasing demand is paramount. <a href="https://us02web.zoom.us/meeting/register/tZIpd-iqrTouGtENOO9mvdg46y2JktTtPQPy">On June 11, I will be doing a mentoring chat around Cyber Security and AI. I hope you can sit in on the discussion.</a></p><p><strong>Analytical Reasoning</strong>. As BAs, we traffic so much information to others and ourselves. Constantly assessing what is important and what is noise. Analytical reasoning is a key underlying competency for a strong BA. Strong analytical skills transform a BA from an “order taker” to a true collaborative partner for all stakeholders. There is more to analytical thinking than just “being smart”; it takes the correct BA approach. This is where BAs are born. What I like to call Straight Up BA. <a href="https://online.flowpaper.com/778f0740/bascatalogvinteractive/#page=1">View the category in our catalog for a complete listing of resources</a>.</p><h3>In closing, all it really takes is a strong commitment to continuous learning.</h3><p>Be inspired by the resources I’ve offered above. It does require a membership to <a href="http://ba-cube.com/">BA-Cube.com</a> if you are not one already. Try one now and see how this platform can assist you in achieving your career goals. The 14-day free trial includes FULL ACCESS to everything discussed in this article. Find opportunities to develop in-demand skills that will help you remain relevant and deliver solutions that exceed expectations. Tell me what you used that made a difference.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=96db0b59ac67" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>