<?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 Ryan Jones on Medium]]></title>
        <description><![CDATA[Stories by Ryan Jones on Medium]]></description>
        <link>https://medium.com/@ryanjjones10?source=rss-fb33a25f7249------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*puPY93egvV2owfN_cKuKEA.jpeg</url>
            <title>Stories by Ryan Jones on Medium</title>
            <link>https://medium.com/@ryanjjones10?source=rss-fb33a25f7249------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 13:13:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ryanjjones10/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[Your Personal Finances…Simplified]]></title>
            <link>https://medium.com/@ryanjjones10/your-personal-finances-simplified-cb04dd48cf38?source=rss-fb33a25f7249------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb04dd48cf38</guid>
            <category><![CDATA[saving]]></category>
            <category><![CDATA[investment]]></category>
            <category><![CDATA[personal-finance]]></category>
            <category><![CDATA[financial-planning]]></category>
            <category><![CDATA[retirment]]></category>
            <dc:creator><![CDATA[Ryan Jones]]></dc:creator>
            <pubDate>Fri, 24 Jul 2020 18:30:16 GMT</pubDate>
            <atom:updated>2020-07-29T17:34:00.632Z</atom:updated>
            <content:encoded><![CDATA[<p>Creating a sustainable and resilient financial life while making your money work for you is easier than many think.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*kfRZk0VwrIfvy3x3VFYclg.jpeg" /></figure><h3>Background</h3><p>I grew up in a financially focused family, went to school for finance, and then worked at Goldman Sachs managing multi-asset class portfolios on discretion for accounts in the $25mm-$500mm range. As a result, I didn’t realize how much this information is not widespread until I left the financial sector.</p><p>Personal finance is not something that is broadly taught and also not an area that excites the majority of the population. As such, while the rules are powerful, many have never used them. I hope this post can help set the foundation for many in achieving financial independence.</p><h3>The Buckets</h3><p>When thinking about the main aspects of your personal finances, they tend to fall into five main buckets: Checking, Savings, Retirement, Investments, and Debt. These buckets are all interrelated and money flows across them over time. As in the picture above, think about the buckets as glasses and your money as champagne filling up one glass before moving to the other. The important part is to know when to move money to each bucket and how to make sure that you have a big enough safety net that you do not end up harming yourself in tough times.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MLfoLyke9DmUQyexlvUpBQ.png" /></figure><p>To provide a real-life example to each of the rules below, we will use a <a href="https://en.wikipedia.org/wiki/Persona_(user_experience)">persona</a> that we call <strong>Carol</strong>. Here is Carol’s income and expenses, which is all you need to know about your own situation to implement the rules:</p><p><strong><em>Salary: $80,000 a year = $6,666 per month pre-tax and $4,733 post-tax</em></strong></p><p><strong><em>Expenses: $3,500 a month on average over six months with $2,400 as fixed monthly expenses (rent, utilities, etc)</em></strong></p><h3>The Rules</h3><h4><strong>1. Start With Your Checking Account</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*SW0mPqt2QiO-w8PwIjJ3zQ.png" /></figure><p>Your checking account is your spending account. This is where your salary (income) comes in and the account that you should be paying out from for all your expenses. With money coming in and out of this account throughout the month, you should not expect a return (close to 0%) on the money here. As a result, you should keep the least amount of cash in here as possible. Many people don’t realize that having too much cash can actually be a bad thing as that money is just sitting there and not making you more money.</p><p><strong>The Rule:</strong> Keep 1 month as a minimum and 1.5 months as a maximum of your expenses in your checking account.</p><p><strong>Example:</strong> For Carol, our persona, this means that she should keep $3,500 (1 month of expenses) to $5,250 (1.5 months) in her checking account but no more than that. Some people will use their fixed expenses to determine the amount as you will have to pay those if something goes wrong but it is good to have the buffer of your total average expenses.</p><h4><strong>2. Build Up Your Savings</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/572/1*fGnEVHk7XGiM2BhL4iWzfA.jpeg" /></figure><p>Once you have 1.5 months of expenses of cash in your checking account, you can start adding to your savings account. Your savings account is meant for rainy day funds (you lose your job, have unforeseen expenses, etc.). Many people talk about starting a retirement account as soon as possible, which you should, but not before you have enough in your savings account. The reason is that if you fall on hard times, the last thing you want to do is pull funds out of your retirement account to live as you can incur high fees, potentially destroying decades worth of work.</p><p>As mentioned, the rule for your savings account is for your rainy day funds so if you have any big expenses coming up that you know about (buying a car, motorcycle, new fridge, etc.), you should add that amount on top of what the rule is.</p><p>Also, since this money is not flowing in and out of the account like your checking account, you should expect a return on your money. As of 2020, you should be getting at paid at least 0.5%-1.5% in interest annually.</p><p><strong>The Rule:</strong> Keep a minimum of 3 months and a maximum of 6 months of expenses of cash in your savings account.</p><p><strong>Example:</strong> For Carol, this means that she should have $10,500 ($3,500 x 3) to $21,000 ($3,500 x 6) in her savings account.</p><h4><strong>3. Let’s Prep For Retirement</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/735/1*cC27IJarJ9ANo8bDM1WMlg.jpeg" /></figure><p>Once you have your safety net created (checking and savings) then you can start investing in your retirement. One of the most powerful tools around for your finances is <a href="https://www.investopedia.com/terms/c/compoundinterest.asp">compound interest</a>. Retirement accounts have incredible benefits of deferring taxes allowing you to compound the returns to grow your nest egg even faster. You also have the opportunity to take on more risk because of the long time horizon (~30+ years), which in turn, should result in greater returns (5–8% annualized).</p><p>When it comes to retirement accounts, for many, you have access to a 401k through work and then can set up a separate IRA. By the time you retire, the goal is to get to 10–12x your annual salary in your retirement account (so if you make $100k a year, you should have $1–1.2mm by the time you retire). To get there, you need to at least have a contribution rate of 10% from your income and keep fully invested. There is a limit though of how much you can put into your 401k ($19k as of 2020) and IRA ($6k as of 2020 if you’re under 50) so depending on your salary you will need to change the contribution rate.</p><p>If you’re curious around investments for your retirement accounts, <a href="https://www.linkedin.com/pulse/one-simple-trick-maximize-your-401k-ryan-jones/">here is an article talking about it</a>.</p><p><strong>The Rule:</strong> Make sure you have enough in Checking and Savings, then start your retirement account and try to max them out over the year. At a minimum try to reach a 10% contribution rate.</p><p><strong>Example:</strong> For Carol, if she can max out her 401k at $19k a year, that would be great but that can be hard with her income so at least a 10% contribution rate ($8,000 a year pre-tax) is a good start.</p><h4><strong>4. Put That Money To Work In Investments</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*tqzieguEKgFxxCjsqOu41A.gif" /></figure><p>You are now at the point where you have enough in your checking account, savings account, and are maxing out your retirement accounts. At this point, you are ready to start investing. The time horizon for traditional investing is much shorter than your retirement but you should think of not touching those funds for at least five years. A best practice when starting to invest is to wait until you have $2,000 to start with. This is enough to obtain diversification with a multi-asset class portfolio through most of the offerings out there. With this, you should expect 4–5% annualized returns after fees if you are younger (20s/30s) with a high risk tolerance.</p><p><strong>The Rule:</strong> Once you have $2,000 after filling up your Checking, Savings, and Retirement buckets, and you don’t need those funds for at least five years, you should open an investment account and constantly contribute to it.</p><p><strong>Example:</strong> For Carol, after she has increased her salary and has maxed out her 401k/IRA she starts contributing $200 a month into her investment account after $2,000 as an initial investment.</p><h4><strong>5. Debt</strong></h4><p>Debt is last as it is multifaceted. It is also a very powerful tool for the wealthy. Many tend to put debt=bad, which is not true. High-interest rate debt is bad while low-interest-rate debt can be helpful. The wealthy actually use debt to make more money, which they call leverage. An example of this is an individual who takes $100 and invests that in the stock market. If they make 5% then they would make $5 giving them a 5% return. However, if they use debt, they could borrow another $100 at a very low-interest rate (say 1%) and with that same 5% return, they now made $10 but only used $100 of their own money so their return, after fees is close to 9% ($10 on $100 = 10% — 1% fee = 9%) instead of the original 5%.</p><p>The rule of thumb for debt is that you should pay off any debt that has an interest rate higher than 4% and do that as fast as possible. This means, pay off that higher interest debt even before building up savings. High-interest debt will keep you from progressing and put you in a never-ending cycle of financial instability. Once you hit 4% or lower, you should pay that debt down over time depending on what you’re using the debt for. The reason that 4% is the magic number is that with investments, you should expect to make 4–5% so sometimes those funds are better used to make you money over time. An example is that if your debt is 3% but your investments are making 5% then you are making 2% a year by keeping the debt.</p><p><strong>The Rule:</strong> Pay off any debt over 4% APR (interest rate) as fast as possible, even before building other buckets, unless that debt is directly tied to an investment that you are using for a greater return. Anything 4% or lower, pay that down over time and build out your buckets.</p><h3>Final Words</h3><p>If you follow these simple rules for your personal finances, you will end up in a healthy place when you retire, during economic downturns, and make your money work for you over the long term. Let me know if you have any questions!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb04dd48cf38" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[So You Want To Be A Product Manager?]]></title>
            <link>https://medium.com/@ryanjjones10/so-you-want-to-be-a-product-manager-df0537d30694?source=rss-fb33a25f7249------2</link>
            <guid isPermaLink="false">https://medium.com/p/df0537d30694</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Ryan Jones]]></dc:creator>
            <pubDate>Tue, 30 Jun 2020 18:33:34 GMT</pubDate>
            <atom:updated>2020-07-01T15:42:07.012Z</atom:updated>
            <content:encoded><![CDATA[<p>It has been a while (years!) since I last wrote about being a Product Manager (PM) and after reading <a href="https://www.amazon.com/INSPIRED-Create-Tech-Products-Customers/dp/1119387507/ref=tmm_hrd_swatch_0?_encoding=UTF8&amp;qid=1590166786&amp;sr=8-1">Marty Cagan’s Inspired (Second Edition)</a>, it was a healthy reminder of what makes great PMs. At least, what are some core skills that can set the foundation to become a great PM.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PxHh71xAbHhvWnGNHOx9bg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@_zachreiner_?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Zach Reiner</a> on <a href="https://unsplash.com/s/photos/strong-foundation?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3><strong>Brief Background:</strong></h3><p>I started as a PM five years ago (I can’t believe it has been that long!) after doing a startup (where I had no idea what I was doing) and before that, helping manage $5B at Goldman Sachs (an unreal experience!). Since being a PM I have trained 25+ other PMs, created and launched 50+ applications/services. Over the past couple of years, I have acted as the Product Lead for multiple products. The Product Lead role consisted of building 100+ person product teams from the ground up, driving out the vision/strategy/product across multiple companies (Pivotal, VMware, Microsoft) through joint ventures.</p><h3><strong>The Point:</strong></h3><p>A question that I get asked is, “What makes a great PM and what do I need to do to become a [great] PM?”. As of today, I tend to send people to a series of books that talk through some of the aspects but I wish I had something as a better jumping-off point for them. I intend for this post to be just that. The jumping-off point for people looking to become a PM and/or want to better understand the steps that can help others become a great PM. These are the foundations for what is needed to start on that road towards being a great PM. Refining your PM skillset is never-ending.</p><h3><strong>Summary:</strong></h3><p>Across many years, multiple industries, and various roles, I have not seen such a varied position as a PM. From company to company or even from team to team, the responsibilities and what is defined as a PM can differ. What I’m going to talk through is what I think PMs should have as a foundation to become a great PM, a skill set that is needed to excel in this age, and what we should be expecting out of our PMs. I call this out as I see individuals that are in a position called a Product Manager but are mostly just doing Project Management, Engineering Management, or Release Management.</p><p>The five core pillars of the skill sets that PMs should have are:</p><ol><li>Business + Strategy</li><li>Communication + Influence</li><li>Technical Knowledge</li><li>Data Analysis</li><li>Industry Knowledge</li></ol><p>It is possible to work on each of these pillars while “on the job” but if you manage to gain the various skillsets before starting as a PM, you will be able to excel much faster. Many of these involve some form of “formal” education so the time commitment can be very high. You also don’t have to have these things to be a PM but I think they can separate the average PM from the great PM.</p><p>I’m not going to cover the tactical side or toolsets of PMs. For example, Lean Product Development and User-Centered Design are great models/toolsets to leverage when building products but over time, we will find new, better ways to approach products and you will need to adapt with them or even be the driver for them (they also have a ton of books around them). There are also plenty of articles that talk through the details of how to approach problems and outcomes (for example, how to write user stories or set up distributed teams).</p><h3><strong>Details:</strong></h3><h4><em>1. Business + Strategy</em></h4><p>This is an area that I rarely see people focus on when they talk about Product Management. If you are a PM, you are building out some form of a product for a company of some type. Regardless of if you ware building a product for internal users or external users, there is a business case associated with all of them. Your primary goal is to provide positive outcomes for your customers by solving their problems and in turn, providing positive outcomes for the business.</p><p>As a result, it is important, when PMing a product, to think about the product from the business perspective, especially at the beginning. Who are the customers? What is the size of the market? How do you differentiate? How do you price this? How can you reach profitability and scale? How will the sales team sell this? How does this need to be marketed?</p><p>This doesn’t mean that you need to do the marketing or the sales yourself, but it does make a big difference when you can actively work with those team members on the details and make sure that those aspects are covered for the product. You could make a beautiful product but if your sales team cannot sell it or your marketing team doesn’t have an edge, then that product will likely sit on the shelf.</p><p>The other area where many fail is putting together a cohesive and actionable strategy. You should expect higher level PMs to drive out the vision and strategy for their product/ product teams. Get more users or make the product run faster is not a strategy.</p><p><strong><em>Obtaining This Skill:</em></strong> You need to learn things such as accounting, sales, marketing, and market analysis. Your best method, albeit costly from a time and monetary perspective, is to go to business school. Even doing a one year course can level you up quickly. If not, there are online courses you can take but they won’t have the same immersion that can increase the speed and depth of the learning process. If you are currently in college, add in business courses! For learning more about strategy, I have found the book <a href="https://www.amazon.com/Good-Strategy-Bad-Difference-Matters/dp/0307886239">Good Strategy Bad Strategy</a> to be the best out there.</p><h4><em>2. Communication + Influence</em></h4><p>As a PM, you sit at the intersection of business, design, and engineering. In order to release a product, you also end up interacting with a wide range of positions across the organization (depending on size) and a key component to your success is how you communicate with all of those groups/individuals.</p><p>I’ve been amazed to see how many people miss the point that as a PM, it is necessary to be clear and concise in how you communicate. This means putting all the pertinent data and information at the top of your emails with links out to details for those that are interested. This means making sure that you are prepped for any presentations and that you cater the information to your audience. In the same way that you ask questions during user interviews, in small groups, don’t just talk the whole time. Continue to iterate and probe to determine what information is needed for the audience that you’re speaking with.</p><p>For large organizations, there tends to be many PMs and those PMs can compete for resources (funds, people, time). It is important to make sure that you can influence those making the decisions around resource allocation. Once you know what is most important to those that are making the decisions, you can easily help them make the link to what you and the team are doing.</p><p><strong><em>Obtaining This Skill: </em></strong>When it comes to communication and influence, there are a few different ways to obtain this. If you already in school, there tend to be courses you can take on business communication and public speaking. If not, there are coaches and courses you can take. While on the job, you can find someone that is already doing well in this area and ask them to help mentor/teach you. If it is another PM, there might be an opportunity to pair with this PM on a project.</p><h4>3. Technical Knowledge</h4><p>I’m not saying you need to be a Software Engineer but if you are building software products, as a PM, you should have an understanding of at least the basics. It is similar to when I was at Goldman Sachs. For the analyst class, about half of the individuals majored in Finance. Goldman hired for smart, driven, teachable individuals. However, I noticed that those with a Finance background were able to add value much faster. If you do not understand the fundamentals of the technicals that drive your industry, it will be hard to understand where the risks, limitations, and area of opportunity is.</p><p>Having a technical understanding also increases your ability to effectively communicate with engineers. It can also speed up your ability to iterate as you could take care of small, but time-consuming tasks, yourself (ex. updating text instead of a lot of back and forth) so that engineering can focus on the highest value areas. One of the biggest frustrations for engineers is to work with PMs that have no clue how they work causing consistent turmoil and misunderstandings. You doing some of the “grunt work” wins you major points.</p><p><strong><em>Obtaining This Skill: </em></strong>Depending on the level that you&#39;re looking to learn and how interested you are in the subject would then dictate what option you take. At a minimum, there are online courses or CS 101 type courses that you can take to learn the basics (APIs, database interactions, languages, web app components, etc). If you want to get hands-on, then one of the boot camps are a great way to learn a lot, quickly. For example, I went to <a href="https://www.hackreactor.com/">Hack Reactor</a> and in 3 months, 6 days a week, 12 hours a day, you come out being able to either build or can learn how to build most applications. They do miss some of the “Why” but you can spend extra time researching that during the course.</p><h4>4. Data Analysis</h4><p>The amount of data that you can obtain from a simple web application at this stage is astounding. In order to drive towards value, you need to understand what your customers are doing and what they say versus what they do, can be different. The way to do this is to leverage quantitative data. As a PM, to help make decisions, validate/invalidate ideas, data is key.</p><p>With data becoming more and more of a differentiator, you need to feel comfortable with large amounts of data and synthesizing that data to get the information that you need.</p><p><strong><em>Obtaining This Skill:</em></strong> At this stage, many of the databases are still using SQL so <a href="https://www.codecademy.com/learn/learn-sql">learning how to make SQL requests</a> can be helpful. <a href="https://gopractice.io/">This course by go practice</a> is also a great way to run simulations with real data and how to gain meaningful insights from it.</p><h4>5. Industry Knowledge</h4><p>This is similar to having technical knowledge. If you are a strong PM and have a large toolset, you can get away at the beginning by doing the research and asking the right questions. However, if you want to drive your product, team, company, and industry forward, you need to become a SME (Subject Matter Expert) in the area. A key component to becoming a SME is enjoying the space that you’re in so it is important for you to find an industry that inspires you and makes you want to do additional research, for fun.</p><p><strong><em>Obtaining This Skill:</em></strong> You will, of course, learn this while on the job but you can learn a lot through conferences, networking, and specializing in the area during school/through online courses (ex. being pre-med for going into healthcare).</p><h3><strong>Closing:</strong></h3><p>If you think I’m missing anything, disagree, or have any questions I’d love to hear them. It is an exciting time as the tools that we have as Product Managers continue to grow and evolve.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df0537d30694" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is the Pivotal Process?]]></title>
            <link>https://medium.com/@ryanjjones10/what-is-the-pivotal-process-417fab075f4f?source=rss-fb33a25f7249------2</link>
            <guid isPermaLink="false">https://medium.com/p/417fab075f4f</guid>
            <category><![CDATA[lean-ux]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[extreme-programming]]></category>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Ryan Jones]]></dc:creator>
            <pubDate>Sun, 07 Jan 2018 12:27:21 GMT</pubDate>
            <atom:updated>2018-01-07T12:27:21.365Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/688/0*yZ112iTnmiWiBhL_." /></figure><p>Before moving to<a href="https://pivotal.io/platform"> Pivotal Cloud Foundry</a> I was a Senior Product Manager at <a href="https://pivotal.io/labs">Pivotal Labs</a>, one of the top software consultancy firms in the world. We work with award winning startups to Fortune 10 companies coaching them on how to determine user value and build that value efficiently with software. What is different from most consulting firms is that our clients work alongside us building out products from our office to learn by doing and to also remove them from their current company’s daily processes.</p><p>Once companies and individuals are able to experience the benefit that working in a similar way as Pivotal provides to their businesses, employees and customers, these groups then look for ways to effectively scale that process across the organization. Unfortunately, altering the way companies have built products, some of them for over a century, with hundreds of thousands of employees, is extremely challenging. Having a specific process and series of steps to follow makes enacting change easier to scale as you can provide materials / trainings that are rolled out across the organization. As a result, on a weekly basis I am asked,</p><blockquote>“What is the Pivotal Process? What is the step-by-step approach that we need to take in order to be successful?”</blockquote><p>Unfortunately, if you are to try and copy the Pivotal Process step-by-step, the outcomes that you would expect will not materialize at your organization. To continuously provide value to your users, companies need to create their own process that works within their industry, culture and product lines based off of what I like to call the <strong>The Pivotal Framework (TPF)</strong>, not the Pivotal Process (Note: The Pivotal Framework is something I created and is not officially used throughout Pivotal).</p><p>A process is a systematic series of actions directed to some end (basically following directions step-by-step without questioning it) while a framework is a structure designed to support something, like a process, and is composed of parts joined together. When clients come to work at Pivotal Labs they are exposed to the Pivotal Labs Process. This is what works well for Pivotal Labs based off of the clientele, industry and market. We have a different process for our product group, Pivotal Cloud Foundry, but that process is based off of The Pivotal Framework (TPF).</p><blockquote>“In an environment of uncertainty, following a specific process will almost always end with a subpar outcome. Understanding the WHY behind each part of the framework allows teams to adapt accordingly and continuously provide value to their customers”</blockquote><h4><strong>The Pivotal Framework (TPF)</strong></h4><p>TPF is composed of Values and Principles from Extreme Programming, Lean Product Development and User Centered Design methodologies. Pivotal has then added Practices from these methodologies along with tools to aid teams in utilizing the framework. In the same way with products, it is most important to get the outcomes you want vs the output. TPF strives to focus on the outcomes you are looking for and the output can change.</p><p><strong>Extreme programming (XP)</strong> is the core of the framework that is created from a developer’s point of view instead of the business determining how development teams should work. XP sets the Values for TPF. It is focused on decreasing the time it takes to release software, increase the quality, increase open communication, obtain rapid feedback, simplify architecture and have respect / trust for others. <strong>Further Readings: </strong><a href="https://www.amazon.com/Extreme-Programming-Explained-Embrace-Change/dp/0321278658/ref=sr_1_1?ie=UTF8&amp;qid=1497223610&amp;sr=8-1&amp;keywords=extreme+programming+explained">Extreme Programming</a> and <a href="https://www.amazon.com/Planning-Extreme-Programming-Kent-Beck/dp/0201710919/ref=sr_1_1?s=books&amp;ie=UTF8&amp;qid=1497223630&amp;sr=1-1&amp;keywords=planning+for+extreme+programming">Planning Extreme Programming</a> by Kent Beck are the best resources to gain a more in-depth understanding of XP.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*x_Xrv-ypPkUpw9zI." /></figure><p><strong>Lean Product Development (LPD)</strong> is added onto XP and is focused on decreasing waste as much as possible. This means understanding who your users are, what their problems are, if those problems are worth solving before determining if you have the right solution for that problem. Once you do have the right solution, then it is building the smallest part of the product that is believed to provide the highest user value as fast as possible. <strong>Further Readings:</strong><a href="https://www.amazon.com/Lean-Startup-Entrepreneurs-Continuous-Innovation-ebook/dp/B004J4XGN6/ref=sr_1_1?s=books&amp;ie=UTF8&amp;qid=1497223713&amp;sr=1-1&amp;keywords=the+lean+startup"><strong> </strong>The Lean Startup</a> and books in the Lean series by Eric Ries, which was influenced by<a href="https://steveblank.com/books-for-startups/"> Steve Blank</a> are the best resources to gain a more in depth understanding of Lean Product Development.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*a1q6uBJofkVcl6Dw." /></figure><p><strong>User Centered Design (UCD)</strong> is the other methodology added onto XP and complements LPD extremely well. UCD focuses on consistently understanding the needs, wants and environments of users. <strong>Further Readings:</strong><a href="http://www.talkingtohumans.com/download"><strong> </strong>Talking to Humans</a> by Giff Constable/ Frank Rimalovski and<a href="https://www.amazon.com/gp/product/0989200507/ref=as_li_tf_tl?ie=UTF8&amp;camp=1789&amp;creative=9325&amp;creativeASIN=0989200507&amp;linkCode=as2&amp;tag=wwwsteveblank-20"> The Four Steps to the Epiphany</a> by Steve Blank.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*lfSMvoqEL5S744w5." /></figure><p>The combination of XP, LPD and UCD is extremely powerful because of how well they complement each other in creating value for users quickly, maintaining high quality software and doing it at a sustainable pace. When you work with Pivotal Labs you will see and experience the practices that come with these methodologies that include:</p><ul><li><strong>From XP:</strong> Pair Programming, Test Driven Development (TDD), delaying decisions until the last responsible moment, expecting changes in requirements, frequent communication, small and frequent releases.</li><li><strong>From LPD:</strong> Minimum Viable Product, Continuous Deployment, actionable metrics, pivot or persevere, build-measure-learn cycles, business model canvas</li><li><strong>From UCD:</strong> Personas, workflows, scenarios, information hierarchy, think-make-check cycles, wireframes, mental models, paper prototypes, assumptions, validation.</li></ul><p>These are all easily recognizable but to build your own process you need to leverage the Values and Principles that make up the TPF. Each of the practices map back to these Values and Principles.</p><p><strong>TPF Values (from XP):</strong></p><ul><li>Constant Communication</li><li>Simplicity</li><li>Rapid Feedback</li><li>Courage — speak up about problems and feelings</li><li>Respect — trust and equality</li></ul><p><strong>TPF Principles (from XP, LPD &amp; UCD):</strong></p><ul><li>Constant Feedback — XP: Constant Feedback / Lean: Learn &amp; Improve, Seek Perspective / UCD: The Process is Iterative</li><li>Diverse Team — XP: Diversity with Skills and Perspectives / Lean: Empower the Team, cross functional team, right resources / UCD: Multidisciplinary skills and perspectives</li><li>Small Chunks of User Value — XP: Flow and Baby Steps / Lean: identify the value stream, reduce waste, define value to customer in small chunks / UCD: Address the whole user experience, understand users, involve users throughout the process</li><li>Self-similarity — Use similar structures, don’t start from scratch if you don’t have to</li><li>Humanity — We are humans building products for humans</li><li>Shared Responsibility — across the whole team</li></ul><p>Another concept that is an important part of TPF are <a href="https://www.youtube.com/watch?v=Z_Q4Q8rCVpU">Balanced Teams</a>. A Balanced Team is an <em>autonomous</em> team that has people with a variety of skills and perspectives that support each other towards a shared goal. Many tend to silo the work of building a product. For example, having a PM and/or designer go off and do product validation, then bring in the engineering team. Instead it is crucial to have all groups involved from the start so that each aspect can be thought of throughout the process. It is not limited to PMs, designers and engineers. A Balanced Team can be any discipline that is involved in the product.</p><p>It is important to spend the time to understand why each of the Values and Principles are important and what they each provide to the team, company and product. The details can be found in the books mentioned above.</p><h4><strong>Tools</strong></h4><p>There are a wide range of tools that have now been created to help teams work within The Pivotal Framework. To illustrate this we will go through the high level steps of shipping a product.</p><p><strong>Discovery &amp; Framing:</strong> Determining if there is a problem worth solving, if that problem is the main problem for the users you’re after, if there is a better set of users to go after, if you’re providing the best solution to the problem and then providing the best solution for those users. At the same time understanding technical feasibility, risks, competitive analysis and business benefits.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/166/0*DrvPW97F_UerFN4r." /></figure><ul><li><strong>Tool:</strong> We have our own internal portal that walks through the methodologies, process and additional tools but the closest thing to get insights into this is the book,<a href="https://www.amazon.com/Sprint-Solve-Problems-Test-Ideas-ebook/dp/B010MH1DAQ/ref=sr_1_1?s=digital-text&amp;ie=UTF8&amp;qid=1497224989&amp;sr=1-1&amp;keywords=sprint"> Sprint</a> by Google Ventures. They utilize a similar methodology with their portfolio companies.</li></ul><p><strong>Prioritization of Work: </strong>Once it is determined what we will be building to test that we are on the right track, we will<a href="https://medium.com/product-labs/principles-to-effective-story-writing-the-pivotal-labs-way-76da56031f82"> generate stories</a> for the dev team and designer(s) to work through.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/225/0*9oPFD2DtQjpJlKyo." /></figure><ul><li><strong>Tool:</strong><a href="https://www.pivotaltracker.com/"> Pivotal Tracker</a> is an opinionated backlog management system that enables teams to be extremely focused and follow XP and LPD Principles and Practices.</li></ul><p><strong>Build &amp; Test:</strong> Once stories are prioritized the team can begin designing and building out the application / service. As part of XP, the team writes tests before writing code and once the code is delivered, the PM will do acceptance testing on each individual story.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/288/0*OkZ0QL_xdbfsaQCI." /></figure><ul><li><strong>Tool: </strong><a href="https://spring.io/">Spring</a> provides tools for developers to quickly build common patterns, standup services and applications in distributed systems.</li></ul><p><strong>Continuous Integration:</strong> As with LPD, we strive for short feedback loops to know if we are heading in the right direction. With XP, we want the same thing with our code. As a result, we are continuously integrating as we build out products to make sure we do not leave it to the end before deploying. This is another method for routinely de-risking our products from the technological perspective.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/225/0*O1VyFflxz6O_aj4S." /></figure><ul><li><strong>Tool:</strong><a href="https://concourse.ci/"> Concourse</a> provides teams with a way to set up continuous integration and deployment pipelines. It also has a simple GUI so teams can quickly determine state of their jobs.</li></ul><p><strong>Deployment &amp; Management:</strong> Once the product has been built and tested, the product should be pushed out to customers as soon as possible. Each release can be seen as an opportunity to learn if we are heading in the right direction. We want to make sure that we release early and often with small chunks of user value.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/279/0*ZjcJU2TtkT4Bj061." /></figure><ul><li><strong>Tool:</strong> Pivotal Cloud Foundry is a cloud-native platform for deploying and operating applications at scale. Dev teams can quickly spin-up resources, data services and connect, each with a single command</li></ul><p>There is certainly a lot to take in here so feel free to reach out with any questions!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=417fab075f4f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Samsung Gear 360 Video in Unity 5.4]]></title>
            <link>https://medium.com/cinematicvr/samsung-gear-360-video-in-unity-5-4-with-oculus-rift-6f1b65ed94e9?source=rss-fb33a25f7249------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f1b65ed94e9</guid>
            <category><![CDATA[tutorial]]></category>
            <category><![CDATA[virtual-reality]]></category>
            <category><![CDATA[oculus-rift]]></category>
            <category><![CDATA[360-video]]></category>
            <category><![CDATA[unity]]></category>
            <dc:creator><![CDATA[Ryan Jones]]></dc:creator>
            <pubDate>Thu, 15 Dec 2016 05:24:15 GMT</pubDate>
            <atom:updated>2016-12-15T20:42:43.823Z</atom:updated>
            <content:encoded><![CDATA[<h4>A step-by-step guide to view 360 video with your Oculus Rift</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/649/1*zzrwFYsyROQZaMTQcU6rqQ.png" /></figure><p>It was a pain to figure out for the first time, but there are only a few simple steps to set it up. Thought I would make it easier for others by posting a step by step so others can easily follow. I’ve also added a few areas where I ran into problems and how potential solutions for fixing them.</p><p>The most useful tutorial I found was by <a href="https://livierickson.com/blog/adding-360-video-to-unity/">Liv Erickson</a> so this is mostly building on what Liv already put together. Also, it seems like you can use any 360 video (as long as it is the <a href="https://docs.unity3d.com/Manual/class-MovieTexture.html">correct format</a> and already been stitched) and any hardware that Unity supports. I just had the <a href="http://www.samsung.com/global/galaxy/gear-360/">Gear 360</a> and <a href="https://www.oculus.com/">Rift</a> available to test.</p><p>As Liv mentions, we are going to create a sphere, add a “Material” to it that has a custom Shader and add a script to the sphere.</p><p>Before starting, make sure you have <a href="https://support.apple.com/kb/DL837?locale=en_US">Quicktime Player</a> as Unity uses that to import videos and you could have potential issues if you download the player while Unity is open.</p><p><strong>Start a new Unity project:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YX9Qrg8Em53TOEx3rGhEQA.png" /></figure><h4><strong>Turn on the Oculus SDK:</strong></h4><p>Edit -&gt; Project Settings -&gt; Player -&gt; Other Settings</p><p>Select “Virtual Reality Supported” and it should already have Oculus selected. If not, select the “+” and select it from the list</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S15LY46bqeH2ZYLJcC0VUA.png" /></figure><h4><strong>Create a Sphere and Move Camera:</strong></h4><p>GameObject -&gt; 3D Object -&gt; Sphere</p><p>Change the “Scale” to 20, 20, 20 for X, Y, Z respectively</p><p>Select Your main Camera and for “Position” make it 0, 0, 0 for X, Y, Z respectively, just like your sphere. We want the Camera to be right in the middle.</p><p>Hit Play and test that your camera moves around with your Rift. You shouldn’t see the Sphere as we have not added the Shader to it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zsPc91VgBETx8xcvVSESkQ.png" /></figure><h4><strong>Create “Material” and add the “Shader”:</strong></h4><p>Assets -&gt; Create -&gt; Material and name it (I called it VidMaterial)</p><p>Now, for the Shader go to Assets -&gt; Create-&gt;Shader-&gt;Standard Surface Shader (not Instanced and I called it InvertSphere)</p><p>Double click on the shader so you can change the script, add the following to it and make sure to save it:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ece6bd5b8d02eb5413b22e8ff31da9bd/href">https://medium.com/media/ece6bd5b8d02eb5413b22e8ff31da9bd/href</a></iframe><p>Now select your Material and at the top, for the Shader, select your customer Shader (InvertSphere).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fkF4haXSeoztODbCVy7TPw.png" /></figure><h4><strong>Add Video to Unity and Material:</strong></h4><p>To import your already edited/stitched video go to Assets -&gt; Import New Assets</p><p>This can take a while. It took ~10 minutes for a 1 minute video. Task Manager said Unity Editor was not responding and so I ended the task. It took a while to figure out why it wasn’t importing through other methods. Instead, just wait.</p><p>Once imported, drag the video the the “Base (RGB)” for the Material in the “Texture” area (in the top right).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YB7PXc9o6TKTwRQXABcB5g.png" /></figure><h4><strong>Add the Material to the Sphere:</strong></h4><p>No select the Sphere in your Scene and drag the Material into the Sphere’s Inspector. Your Sphere should now be black.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9qrBwm6qJXR0KpFDIa4kYQ.png" /></figure><h4><strong>Create the Auto Play Script:</strong></h4><p>Now that we have the movie in our Sphere, we need to add the script to auto play it as movies do not start on their own in Unity.</p><p>To create a script go to Assets -&gt; Create -&gt; C# Script</p><p>I named it PlayVideoOnLoad and then double click it and add the following into it:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/851187040e32e156b5be2758762a99e2/href">https://medium.com/media/851187040e32e156b5be2758762a99e2/href</a></iframe><h4><strong>Add the Script to the Sphere:</strong></h4><p>The last step is to add the auto play script to the Sphere. Select the Sphere and drag the script into the inspector.</p><p>You must then select the video in the “Mov Texture” area within the script that you added as a component in the Sphere’s Inspector. You can do that by clicking the small circle on the right of it. It should then looks like this (the Sphere may be black and that is alright, just hit play):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EKP7xEjWo-I1kX8fl1VFzg.png" /></figure><h4>That’s it!</h4><p>Hit play and you should have your 360 video running in your Rift headset. Let me know if you have any questions.</p><p><em>Like</em><strong><em> </em></strong><em>this story? Get more in the </em><a href="http://goo.gl/BGuclj"><em>weekly newsletter</em></a><em> from CinematicVR.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f1b65ed94e9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cinematicvr/samsung-gear-360-video-in-unity-5-4-with-oculus-rift-6f1b65ed94e9">Samsung Gear 360 Video in Unity 5.4</a> was originally published in <a href="https://medium.com/cinematicvr">CinematicVR</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pivotal Tracker Project Template]]></title>
            <link>https://medium.com/product-labs/pivotal-tracker-project-template-acbb244bce10?source=rss-fb33a25f7249------2</link>
            <guid isPermaLink="false">https://medium.com/p/acbb244bce10</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[pivotal-tracker]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Ryan Jones]]></dc:creator>
            <pubDate>Wed, 16 Nov 2016 00:26:13 GMT</pubDate>
            <atom:updated>2016-11-28T16:21:05.136Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TpqBlqD8HWBmXyzunmw9Ng.png" /></figure><p>Here at <a href="https://pivotal.io/labs">Pivotal Labs</a>, a <a href="https://medium.com/product-labs/pivotal-labs-a-very-different-type-of-consultancy-9b47a27f0388#.o3i5t033y">software consultancy company</a>, we are constantly starting new projects. Looking at the blank slate of an empty <a href="https://www.pivotaltracker.com/">Pivotal Tracker</a> can be intimidating. As part of our project kickoff process, we start with a consistent structure.</p><p>The structure includes:</p><ol><li>A PM inbox: An area for Product Managers to place stories that they are working on and for others to add stories for the PM(s) to review before entering them into the backlog. <em>Tip: Use a release marker with up arrows as a divider.</em></li><li>A Dev inbox: Where chores can be stored and prioritized that are then brought into the backlog during Pre-IPM/IPM (Iteration Planning Meeting).</li><li>Feature and Bug Templates: Used as a reminder of what makes a good story. <em>Tip: From the </em><a href="https://medium.com/product-labs/principles-to-effective-story-writing-the-pivotal-labs-way-76da56031f82#.gclkv6jrv"><em>Effective Story Writing</em></a><em> post it includes a </em><a href="https://docs.google.com/document/d/1tDHkfwfZTmxUnVEjsByVI7473mjh2i--kE_EJwd-6SA/edit?usp=sharing"><em>Feature Template</em></a><em> and </em><a href="https://docs.google.com/document/d/1fJh3yRjT2IiGYVfMGxMtGiP2Od-QkPql2lNO4lTj9LQ/edit?usp=sharing"><em>Bug Template</em></a><em>.</em></li><li>Testing URLs: Having a centralized location to store links for testing makes it easy to reference and keep updated instead of storing them in individual stories.</li></ol><p>After your additions your Tracker will now look like the image below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mVgjuFrGIXAYJPOrl-kYjg.png" /></figure><p>While it may not look like much, you no longer have a blank page and have a starting point!</p><p>If you have other tools or structures that work for you, it would be great to hear them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=acbb244bce10" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-labs/pivotal-tracker-project-template-acbb244bce10">Pivotal Tracker Project Template</a> was originally published in <a href="https://medium.com/product-labs">Product Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to set up BLE with Swift 2.2]]></title>
            <link>https://medium.com/@ryanjjones10/how-to-set-up-ble-with-swift-2-2-34bb6f209de2?source=rss-fb33a25f7249------2</link>
            <guid isPermaLink="false">https://medium.com/p/34bb6f209de2</guid>
            <category><![CDATA[bluetooth]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[swift]]></category>
            <dc:creator><![CDATA[Ryan Jones]]></dc:creator>
            <pubDate>Wed, 27 Jul 2016 02:22:14 GMT</pubDate>
            <atom:updated>2016-07-27T02:22:14.090Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*kV_SFHsBzY2WlOD4ZH0Rsg.png" /></figure><p>There is a specific sequence that you need to follow for BLE to work with an iPhone. Apple’s documentation is truncated and does not seem to provide a clear flow for these steps. There are snippets online and you can reference other people’s applications but nothing explains what is happening in each step, that I have seen yet. Hopefully this post can help explain it and keep you from running into the same issues I had. As always, there are different ways of implementing so please let me know if there is a more efficient way to handle something.</p><p><strong>Step 1: Add CoreBluetooth to your application</strong></p><p>First, in order to use Bluetooth you need to add the CoreBluetooth library to your application. To add CoreBluetooth you need to select your parent Xcode file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1015/1*6AtdaVKkoFlLkCNOVzDXrw.png" /></figure><p>In the “Link Binary With Libraries” section click the “+” button, search CoreBluetooth, select and add it.</p><p>Now in your ViewController you need to import CoreBluetooth. Along with “import UIKit” add “import CoreBluetooth”.</p><h4>Step 2: Utilize CBCentral and CBPeripheral from CoreBluetooth</h4><p>From CoreBluetooth you want to use CBCentralManagerDelegate and CBPeripheralDelegate protocols in your class as this will allow you to use the methods the delegate must adopt, allowing you to manage what acts as the central and the peripheral for the Bluetooth connection. After adding CBCentralManagerDelegate and CBPeripheralDelegate to your “ViewController” class, you’ll want to store the delegate’s objects in a variable so you can call the methods of each. It should look like this so far:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9280411da6ceece4604e3e62bfe026f5/href">https://medium.com/media/9280411da6ceece4604e3e62bfe026f5/href</a></iframe><h4>Step 3: Run CBCentralManager</h4><p>Your phone will act as the central. To start your central manager you can place it in the viewDidLoad() function and delegate it to itself. However, I placed this one in its own function (“startManager”) so that we can control when the phone starts its sequence and I will explain the usefulness of this later.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/54288a947424e93f0983546ced1a6017/href">https://medium.com/media/54288a947424e93f0983546ced1a6017/href</a></iframe><h4>Step 4: Check that BLE is on and then start scanning</h4><p>Next, before we can start scanning we need to make sure that bluetooth is powered on for the device. To do so you can use a preset function that is called if the state has been updated and pass in the CBCentralManager object. Once you determine that it is Powered On you can call the function to start scanning (scanForPeripheralsWithServices).</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/91e2c58eb877217dfbf867de85ea9435/href">https://medium.com/media/91e2c58eb877217dfbf867de85ea9435/href</a></iframe><h4>Step 5: Find your BLE device and connect to it</h4><p>To see all available devices (peripherals) to connect with, you can listen for discovered peripherals with didDiscoverPeripheral. If so, it will return each peripheral object, which you can store. Instead of storing each device I focused on just the one I wanted. Once found, you should save that peripheral to a variable to use it later. To connect to the peripheral you found you can use the method connectPeripheral from centralManager and reference the peripheral. I’ve added in the option to notify me if it disconnects.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a239847a8f09655468fc05ea480e85a1/href">https://medium.com/media/a239847a8f09655468fc05ea480e85a1/href</a></iframe><p>Once you connect you will want to stop scanning. It is important to add the centralManager listener didDisconnectPeripheral so you can restart the scanning if it disconnects (this is why I separated the start scan into a separate function).</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/dce1a6afd598271703ab881d6383215b/href">https://medium.com/media/dce1a6afd598271703ab881d6383215b/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ab1d16de4154ed23c714f12cc349149c/href">https://medium.com/media/ab1d16de4154ed23c714f12cc349149c/href</a></iframe><h4>Step 6: Obtain services, characteristics and send value to device</h4><p>Once you are connected to the peripheral you can find its services and characteristics. For a peripheral there can be many services and for a service there can be many characteristics. If you are going to write a value or make changes to anything on the BLE device you will want to make sure you are writing to the correct service or characteristic. For what I was trying to do, I needed to write to a specific characteristic of the service that we had on the BLE device. So now instead of using functions from the centralManager object you are using the functions from the peripheral object you saved. To find the services you can call discoverServices once you are connected. Then to see what the services are on the peripheral you have didDiscoverServices listening.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/84f2a40f28f2fee300b68d2fef104b4d/href">https://medium.com/media/84f2a40f28f2fee300b68d2fef104b4d/href</a></iframe><p>Once discovered, you can call discoverCharacteristics on that service. Having didDiscoverCharacteristicsForService listening will then return with the characteristic object. I cycled through the characteristics to find the one I wanted and from here you can save it in a variable to write to later. Immediately below I have it writing to the characteristic but in the full app have it saved and used later. To write to the peripheral so you can call the method on the peripheral object, writeValue and pass in the encoded value and call out the characteristic that you want to write to.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/64947a90264315f1a2c8d2c38714c78a/href">https://medium.com/media/64947a90264315f1a2c8d2c38714c78a/href</a></iframe><h4>Bonus: RSSI</h4><p>For what I was looking to do with the application I wanted to roughly know how far I was from the device, which the RSSI reading of the peripheral is good for. Apple has depreciated the RSSI functions so you need to create a workaround. To do so I used a timer (Let me know if you find a better way to handle this). When you find the peripheral it will give you the RSSI once and when you connect to the peripheral it will give it to you again. To keep it streaming you need to keep calling that same function. To read the RSSI you can call the function readRSSI on the peripheral object.</p><p>If it read the RSSI then I saved it to a variable to display on my storyboard. The timer then keeps calling the readRSSI function.</p><p>You will want to make sure that you stop reading the RSSI when you disconnect from the peripheral.</p><p>Below is the full application including reading RSSI and writing once the RSSI hits a certain number</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8f85a6d496117521154be338326cc110/href">https://medium.com/media/8f85a6d496117521154be338326cc110/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=34bb6f209de2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Most Important Tool For Entrepreneurs]]></title>
            <link>https://medium.com/product-labs/the-most-important-tool-for-entrepreneurs-f72f9c9b71d5?source=rss-fb33a25f7249------2</link>
            <guid isPermaLink="false">https://medium.com/p/f72f9c9b71d5</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Ryan Jones]]></dc:creator>
            <pubDate>Wed, 08 Jun 2016 20:07:33 GMT</pubDate>
            <atom:updated>2017-05-01T19:24:37.433Z</atom:updated>
            <content:encoded><![CDATA[<h4>Save Time, Money and Yourself from Emotional Distress</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GdJvvdIDcewBWT-LFwAxUw.jpeg" /></figure><p>That tool is conducting user research effectively; something that I wish I fully understood before moving forward on any product idea, let alone starting a company. I’ve only recently come to understand, implement and realize the power of effective user research. Hopefully this post can help those that are in a similar position as I have been in the past, save time, money and decrease the volatility of the emotional roller coaster that all entrepreneurs go through.</p><p>As an entrepreneur you tend to hear high level words of wisdom from others such as, “Go out and talk to users, build a product that users love, find a problem to solve”, but very few actually tell you how to do these things and many don’t actually know how. To solve an actual problem, build a product users love and to continue building valuable features for your users it all comes down to doing user research effectively. The methods for effective user research are unnatural. Without formal training and making a conscious decision to implement these methodologies, you, as an entrepreneur, will inevitably lead the product in the wrong direction.</p><h4><strong>The Steps Towards Effective User Research:</strong></h4><ol><li>There are multiple books, college degrees and research papers focused on effective user research. As a result, it cannot be covered in a &lt;10 min post but the most succinct explanation of effective research that I’ve come across is the book “<a href="https://s3.amazonaws.com/TalkingtoHumans/Talking+to+Humans.pdf">Talking to Humans</a>”. It is free and roughly 60 pages. So you can crank through it in about an hour and save yourself months or years of frustration. To get a glimpse into the process here is a 10 min. <a href="https://vimeo.com/165124895">video of Louis Theroux</a>, a documentarian, using effective user research methodologies to obtain information from interviewees.</li><li>As mentioned, these methodologies are not natural. Before interviewing users, practice with others by doing mock interviews and prepping for them (write up your script, topic maps, etc) with what you learned from <em>Talking to Humans</em>.</li><li>Go out and interview users. Fight against your emotions, natural instincts, remain objective and consciously focus on following the effective user research methodologies. Since you should have a designated note taker during interviews it would help if that person also went through steps one and two so they can provide feedback to you after the interview.</li><li>Iterate on the methodologies to determine what works best for your industry/type of users.</li></ol><h4><strong>Why Is Effective User Research The Most Important Tool?</strong></h4><p>This tool defines the product/service, users, and future enhancements. With a product/service being the heart of any company then effective user research is the best medicine to keep that heart beating. It is also something that you will continue to do no matter what stage your company/product is in. Whether you are just getting started on an idea or are a fortune 500 company with multiple product lines, you should be continuously doing user research.</p><p>Effective user research can not only tell you what to build but also what not to build. For those that have gone through the process of building a product for customers before, you have probably heard a potential customer say, “that product sounds great, we’d love to use that here” and then after development they are slow to adopt. Effective user research saves you from these circumstances so you do not waste your time, money or the stress of the customer not actually adopting the product you built for them.</p><p>The success of a product lies in the research, not in the development. You could build a technically amazing product but if it is a product that brings no value to potential users then it will fail. A recent client drew the diagram below on what he thought the ratio was between research and development for creating a successful product when he first arrived at Pivotal Labs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/559/0*FBULJ8H0CF0PW6hc." /></figure><p>After a few months working with us, he quickly realized that it is mostly determined by research and re-drew the circles. He has now gone back to his company pioneering the way he and his company builds software.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/555/0*yN_RCpDUv3gyvL2z." /></figure><p>In terms of saving time and money, here at Pivotal Labs we build teams composed of designers, product managers and developers. The slowest portion is the actual development. As we push for for fast feedback loops to save time, which in turn save money, the designers and product managers can move quickly to do research before a line of code is even written.</p><h4><strong>Break Down Your Research Into Three Parts:</strong></h4><p>You will see this breakdown in the book but wanted to call it out on a high level as this is where I see most entrepreneurs fail. These forms of effective user research are used for new products or features. Once out in user’s hands it is important to incorporate analytics into the decisions. It is important to always think about what stage you are in with a product or feature. Below are the three ways you should approach your user research along with some best practices. Most entrepreneurs skip to stage 2, validation, missing the most crucial step to determine if there is even a problem that needs solving.</p><ol><li><strong>Exploratory — What are the problems/needs of the user?</strong></li></ol><p>The goal of the exploratory interviews is to gain empathy. If you understand the user’s world, their needs and workflows you can make really great decisions about what to build for them.</p><p>Most business or product ideas stem from noticing a problem and coming up with a potential solution for that problem. Most people do not take a step back to really understand if that is a problem worth solving, if the solution you have is the best solution and even if there needs to be a solution.</p><p>Many make the mistake of mentioning their product in this phase. DO NOT MENTION YOUR PRODUCT. You are here to understand what problems people have, their current solutions and any hacks they are doing to solve their problem.</p><p><strong>Dos:</strong></p><ul><li>Understand the biggest risk to your product</li><li>Prepare a script before hand to get at those risks</li><li>Elicit stories that describe past behaviors (Examples: “ Tell me about the last time you …”, “Tell me about the best time..”)</li><li>Have at least one dedicated note-taker</li><li>Record what the customer says, not what you think it implies</li><li>Listen much more than you talk</li><li>Be comfortable with uncomfortable pauses</li><li>Try to follow up important answers with “Why” and “How”</li><li>If there is a hack, ask them to tell you about it</li><li>Ask “If you could wave a magic wand to fix this problem, what would you have happen?”</li></ul><p><strong>Don’t:</strong></p><ul><li>Don’t talk about or sell your solution</li><li>Don’t ask your customer what they want</li><li>Don’t Interview multiple people at the same time</li><li>Don’t ask Yes or No questions</li><li>Don’t get biased by one person’s feedback. You need multiple customers saying the same thing.</li><li>Don’t use surveys!</li></ul><p><strong>2. Validation — Does our solution/idea solve their problems?</strong></p><p>At this stage you can show potential users the designs of the product. However, it is important to not guide or bias the user. You can provide context as to where they are sitting within the application but you should not give insight to what is exactly on the page. You can then ask questions such as:</p><ul><li>What do you see here?</li><li>What do you think would happen if you clicked that button or scrolled over this area?</li><li>What would you do next from here?</li><li>Why is that</li><li>If you had a magic wand to add anything or to change the experience what would you do with it?</li></ul><p>During these sessions it is important for them to think out loud and provide rationale for everything that they do.</p><p><strong>3. Usability — Can they use the solution?</strong></p><p>Usability tests measure a user’s ability to complete tasks. Each of these tasks have a specific goal with effectiveness, efficiency, satisfaction and emotional responses identified in a specified context of use. Tests are conducted in a usability lab, which consists of two parts: the test room and the observation room. Tests can be conducted with live websites, apps or different forms of prototypes (ex. <a href="https://www.invisionapp.com/">invision app</a>).</p><p>It is important to let them struggle if they are having issues with the application to see how they respond. If they are absolutely stuck then you can help them through to the next task.</p><p>Similar to validation it is important to take them though tasks but this time focused on flows, speed and general ease of use. An example of a task would be, could you please scan a bag onto the plane with the device? vs. Hit the scan button then mark the bag into the pit of the plane that it needs to go to, now go back to the other screen to scan it again. You want to make sure it is intuitive or if there is a better flow. Once in production it can be very helpful to watch over the user’s shoulder to see how they interact with the product.</p><h4><strong>Practice Practice Practice</strong></h4><p>As mentioned, implementation of doing user research effectively is not easy and takes time. I urge you to practice with others, try different methods with users and refine your craft. It must be a conscious decision to use the principles and fight against what feels natural. This tool can give you a competitive advantage against your competitors and ensure that you are heading in the right direction while others may not.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f72f9c9b71d5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-labs/the-most-important-tool-for-entrepreneurs-f72f9c9b71d5">The Most Important Tool For Entrepreneurs</a> was originally published in <a href="https://medium.com/product-labs">Product Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Principles To Effective Story Writing: The Pivotal Labs Way]]></title>
            <link>https://medium.com/product-labs/principles-to-effective-story-writing-the-pivotal-labs-way-76da56031f82?source=rss-fb33a25f7249------2</link>
            <guid isPermaLink="false">https://medium.com/p/76da56031f82</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[lean]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Ryan Jones]]></dc:creator>
            <pubDate>Thu, 24 Mar 2016 16:22:19 GMT</pubDate>
            <atom:updated>2017-05-01T20:14:04.978Z</atom:updated>
            <content:encoded><![CDATA[<p>By <a href="https://medium.com/u/fb33a25f7249">Ryan Jones</a> (Product Manager) &amp; <a href="https://medium.com/u/9d1f28aee290">Pablo Schuhmacher</a> (Product Manager)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8kiD5IgprKNNqQljCjY4GA.png" /></figure><p>Different teams across projects and companies have different styles of story writing. Ultimately, it is up to you and the team to figure out what is most effective given the goals and context of the project. However, the core principles that guide our story writing here at Pivotal Labs can be used regardless of style or variation in either process or syntax. While the differing views on the “best way” to write stories can make it difficult to determine the most effective approach, there are a few core principles that guide our story writing. In this post, we’ll explore the three most common types of stories that you can create in Pivotal Tracker and the core principles that inform how we write stories.</p><p><strong>Story Writing: Guiding Principles</strong></p><p>First and foremost, stories are placeholders for further conversations and context on conversations already had. We write stories to address a feature, bug, or chore, and then we discuss those stories — usually with our engineering team — to surface any lack of clarity or concern around delivering the story in question. Because of this, stories do not need to include every little detail, but should be a reminder of what was talked about and include everything at a high level.</p><p>It is also important to remember that stories should state the <em>what</em>, not the <em>how</em> (e.g., “Improve search response by 15 seconds” vs. “Do not perform a full-table indexing on every database update”). Stories are not meant to be technically prescriptive; that is, they do not need to specify any information on how exactly your engineering team could implement the functionality in question. Stories clarify the reason for the functionality and what specifically that functionality is.</p><p>All stories should follow the <a href="https://en.wikipedia.org/wiki/INVEST_(mnemonic)">INVEST model</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/688/0*4gw0gpoOZZ0z3M8K." /></figure><p><strong>Different Types of Stories:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/74/1*uyTfG2GtI5zNUwZHS536Cg.png" /></figure><p><strong>Features/User Stories:</strong> Feature stories are designed to explain the who, what, and why of the smallest incremental feature that can be added to a product that delivers user value. Feature stories are pointed by the development team and are estimated by complexity rather than by the time it will take to complete the feature. They are written from the user’s perspective and act as lightweight requirements documentation for a development team. Following the INVEST model, they should be independent and create clear value to the user. For example, each button should be added in conjunction with a feature instead of having a story that creates a row of buttons that are not connected to features. While features and user stories are often used interchangeably, for the sake of clarity — and to be consistent with Tracker’s naming conventions — we will refer to this kind of story only as a <em>feature story</em> throughout the rest of this post.</p><p>Feature stories should include several things:</p><ul><li>Title: The title should be short, descriptive, and include the specific user/persona. For example, the user/persona should either be the specific type of user (e.g., editor) or the <a href="https://en.wikipedia.org/wiki/Persona_(user_experience)">persona name</a> (e.g., Jill) rather than just “user.” This also works for users that are not people but systems (e.g., “Purchasing API”).</li><li>Business case: Who wants the functionality, why, and to what end? This is incorporated so that everyone on the team understands why the feature is being added. If you cannot think of a reason, then it’s worth reassessing if the feature should be included. The business case also allows others on the team to think if there is a better user experience than the one provided.</li><li>Acceptance criteria: This defines what you will walk through to make sure that the story is completed. Developers working on the story should also walk through the acceptance criteria before delivering. At Pivotal, our beginning template for acceptance criteria is written in the <a href="http://docs.behat.org/en/v3.0/guides/1.gherkin.html">Gherkin language</a>. The Gherkin language was originally created for Cucumber, a Ruby testing suite, and is meant to “enforce firm, unambiguous requirements … and a script for automated testing.” Keep in mind that good feature stories should <em>not</em>, however, be prescriptive in implementation details.The syntax is as follows: <em>GIVEN [necessary context] WHEN [action] THEN [reaction]</em>. Sometimes it helps to walk backwards to determine your GIVEN (examples to follow). If you find yourself writing multiple “and”s in the acceptance criteria, that is a smell test that indicates you should split the story into two or more.</li><li>Notes: Include additional information needed for the story, such as design notes (which might point out changes to mocks) or developer notes (which might provide insight that could help developers deliver the story).</li><li>Resources: Add mocks, wireframes, user flows, links, and other assets to help deliver the feature story.</li><li>Labels: This includes epics (larger overarching features), build #s, users, etc. These are used most effectively to help group the stories together.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/74/1*qm1KkZC1qlg4hwPX9_07FQ.png" /></figure><p><strong>Bugs: </strong>A bug is a defect in a feature that has already been accepted. You should not use bugs to detail new features and functionality (e.g., “Price should be non-negative” or “Login button doesn’t work”). Bugs are directly related to features that have already been delivered and provide no new user value, which is why they do not have points. The other reason they do not have points is that bugs can be impossible to estimate and could take 30 seconds or 30 days to resolve.</p><p>Bugs should include this information:</p><ul><li>Title: This should be short and descriptive.</li><li>Description: What is currently happening? What <em>should be</em> happening?</li><li>Instructions: Outline the steps to reproduce it.</li><li>Resources: Include screenshots and other assets to help explain/show the bug.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/74/1*t2xuh7W88tS7Mbmi9XUCrw.png" /></figure><p><strong>Chores:</strong> A chore is a story that is necessary but provides no direct, obvious value to the user (e.g., “Setup new domain and wildcard SSL certificate to create test environments” or “Evaluate tools for system troubleshooting”). Chores can represent technical debt and/or points of dependency on other teams. Chores are not estimated (i.e., pointed), as they do not contribute user value directly. This means that if a chore feels like it provides user value then it should be incorporated into a feature story. For example, if you are using an analytics service, the additional complexity of the service setup should be taken into account in the first analytics feature story, rather than separated out as a chore.</p><p>Chores should include this information:</p><ul><li>Title: This should be short and descriptive.</li><li>Description: Why is it needed? Does it help the team go faster or is it a dependency that could cause problems in the codebase if it’s not done?</li><li>Resources: Including instructions, additional context, or other assets that help execute the chore.</li></ul><p><strong>Feature and Bug Story Templates:</strong></p><p>The templates below are a great starting point for writing feature stories and bugs. We haven’t included a template for chores as they vary significantly, but we have provided examples of chores at the end of the post. These templates have been iterated on over the years to provide consistency, clarity, and simplicity. For easy access, we copy and paste them into the Icebox with a title of, “Cheat Sheet: Story Template — Reference When Writing Feature Stories” and “Cheat Sheet: Bug Template — Reference When Writing Bugs.”</p><p><strong>Feature Story Template [</strong><a href="https://docs.google.com/document/d/1tDHkfwfZTmxUnVEjsByVI7473mjh2i--kE_EJwd-6SA/edit?usp=sharing"><strong>copy &amp; paste version</strong></a><strong>]</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/610/0*KQLMGF30-IUsM4AB." /></figure><p><strong>Bug Template [</strong><a href="https://docs.google.com/document/d/1fJh3yRjT2IiGYVfMGxMtGiP2Od-QkPql2lNO4lTj9LQ/edit?usp=sharing"><strong>copy &amp; paste version</strong></a><strong>]</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/664/0*gkiL3neYdKLY6qOo." /></figure><p><strong>Conclusion</strong></p><p>We have no doubt that as you become comfortable with story writing, you will formulate your own style that works best for your team or project and undoubtedly move away from the basic templates that we have provided. To that end, we’ve included below what we consider to be examples of great stories. As you’ll see, while they vary in style and syntax, they exemplify the core principles that we’ve highlighted in this post.</p><p><strong>Examples of Well-Written Stories:</strong></p><p><strong>Feature Stories</strong></p><p><em>Using a persona name for a consumer-facing product</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/646/0*lFFT9Qphfqbtt96W." /></figure><p><em>Using a persona name in an internal tool</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/609/0*bfpD4LO9p2Ty76aa." /></figure><p><strong>Bug</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/609/0*BE2Ve6FwyenRSzzf." /></figure><p><strong>Chores</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/658/0*f-cl0cfpPff1N6pn." /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/742/0*OOjUazGYzekiGi6E." /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=76da56031f82" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-labs/principles-to-effective-story-writing-the-pivotal-labs-way-76da56031f82">Principles To Effective Story Writing: The Pivotal Labs Way</a> was originally published in <a href="https://medium.com/product-labs">Product Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Product Managers Can Bring to Test Driven Development]]></title>
            <link>https://medium.com/product-labs/what-product-managers-can-bring-to-test-driven-development-b8b1abb7d699?source=rss-fb33a25f7249------2</link>
            <guid isPermaLink="false">https://medium.com/p/b8b1abb7d699</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[test-driven-development]]></category>
            <dc:creator><![CDATA[Ryan Jones]]></dc:creator>
            <pubDate>Tue, 15 Mar 2016 15:51:15 GMT</pubDate>
            <atom:updated>2016-03-18T00:30:27.612Z</atom:updated>
            <content:encoded><![CDATA[<p>By <a href="https://medium.com/u/863add11ea59">David Julia</a> (Developer) and <a href="https://medium.com/u/fb33a25f7249">Ryan Jones</a> (Product Manager)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*tOj1UPbgYy4UGK4MdJc9yw.jpeg" /></figure><p>On a recent project at <a href="http://pivotal.io/labs">Pivotal Labs</a>, we challenged the team to think about possible solutions to minimize the amount of bugs we had reaching our development environment. The unanimous answer was focused on product testing. Traditionally, software testing was executed by the QA team (unpredictable — after development), but with the movement to <a href="https://en.wikipedia.org/wiki/Extreme_programming">XP/Agile, </a>software developers have begun driving testing strategies (predictable — before development) with <a href="https://en.wikipedia.org/wiki/Test-driven_development">Test Driven Development</a> (TDD). While the engineering teams may be driving the testing strategies with TDD, Product Managers (PMs) can add significant value and need to involve themselves/facilitate discussions around those strategies.</p><p>Putting aside the maintainability and architectural benefits, testing is important to mitigate product risk. If the core of your application is unreliable or buggy it can negatively impact the end user, hurt adoption, cause customer attrition and in turn, hurt your brand. As a PM it is your responsibility to determine ways to decrease product risks. While most PMs will not be writing tests, they can have an active role in shaping the testing strategies of the team.</p><p><strong>Determine Trends</strong></p><p>In an XP environment, PMs can help by writing their user stories with testable acceptance criteria and taking the lead in performing the acceptance testing themselves. Doing so can help identify defects and patterns in those defects. For example, the links in a web application tend to break routinely with new builds. A developer seeing a single instance might not identify this as a trend, but a PM is in a unique position to point out this common thread and drive conversation around testing strategies to reduce the likelihood of future regressions.</p><p><strong>Make Use of Research and Analytics</strong></p><p>PMs are also responsible for keeping an eye on user behavior whether it be through small-scale user testing alongside designers (qualitative) or through analytics dashboards (quantitative).</p><ul><li>From the qualitative research perspective PMs can help inform teams of possible edge cases and flows that the user could take. This information can help the engineering team add tests to handle these edge cases so that when another developer picks up the code and makes changes they are cognizant of all the cases that they need to address. It is important to rotate engineers on projects to have fresh eyes on the code base. A new engineer may look at a specific segment of code and initially wonder “why would you write something this way? There are much better ways to implement this feature.” But after looking through the tests, they will have a better understanding of why it was written that way.</li><li>From the quantitative perspective a PM might notice that the way users interact with a specific portion of the application was not how they initially anticipated and is causing a high level of crashes. As a PM the immediate problem must be addressed, but they should also ask themselves if a similar scenario could happen in other parts of the application. If so, they must discuss with the engineering team to determine the best ways to make sure the new edge cases are incorporated in the testing coverage. Questions to ask of developers could include: “How could we simulate this kind of situation in a test?” and “Are any other critical pieces of functionality affected by this potential change? ”</li></ul><p><strong>Understand Feature Importance</strong></p><p>With the PM sitting at the intersection of development, design and business they have a great sense of the importance of the features they are building, as well as the potential cost if something goes wrong. The effectiveness of testing strategies can be dictated by how well this information is disseminated to the rest of the team. Here are a couple of examples of conversations that could be had:</p><blockquote><em>PM — “By our metrics, 90% of our orders come through the One click purchase button. It is vital to our business to make sure any scenarios the customer can take are bug-free. Are there tests that we can implement to make sure that we are testing the happy path and the edge cases we talked about as a team? ”</em></blockquote><blockquote><em>Devs — “We better test that flow itself thoroughly, maybe this warrants a true end-to-end test where we might not have had one before”</em></blockquote><blockquote><em>PM — “We have to have that feature to list it on our sales copy, but no one really uses it.”</em></blockquote><blockquote><em>Devs — “Well, maybe we don’t do exhaustive end-to-end, gui-driving tests for this feature, the costs outweigh the benefits in risk reduction”</em></blockquote><p>Once the PM takes an active role in making sure the team understands the reasons for and relative importance of features, flows, and edge cases, the engineering team can make a better decision about their testing strategies.</p><p>Testing strategies should not be something dictated by QA teams or engineers, but should include the entire team. PMs have unique perspectives and sets of information that can assist overall product stability. Along with the engineering team, PMs can also be responsible for ensuring that testing strategies cover edge cases, focusing efforts on high-value product features and preventing regressions from happening in the future. There is no such thing as writing bug-free code, but by incorporating those outside of QA and engineering to help with testing, risks can be minimized.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b8b1abb7d699" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-labs/what-product-managers-can-bring-to-test-driven-development-b8b1abb7d699">What Product Managers Can Bring to Test Driven Development</a> was originally published in <a href="https://medium.com/product-labs">Product Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>