<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.10.0">Jekyll</generator><link href="https://brocketthub.github.io//feed.xml" rel="self" type="application/atom+xml" /><link href="https://brocketthub.github.io//" rel="alternate" type="text/html" /><updated>2024-08-22T15:32:29+00:00</updated><id>https://brocketthub.github.io//feed.xml</id><title type="html">Chris Brockett</title><subtitle>Write an awesome description for your new site here. You can edit this line in _config.yml. It will appear in your document head meta (for Google search results) and in your feed.xml site description.</subtitle><entry><title type="html">Agile</title><link href="https://brocketthub.github.io//article/2024/08/15/Agile.html" rel="alternate" type="text/html" title="Agile" /><published>2024-08-15T00:00:00+00:00</published><updated>2024-08-15T00:00:00+00:00</updated><id>https://brocketthub.github.io//article/2024/08/15/Agile</id><content type="html" xml:base="https://brocketthub.github.io//article/2024/08/15/Agile.html"><![CDATA[<h1 id="agile-methodology">Agile Methodology</h1>

<p>Agile methodology is a way of making software that’s flexible and team-focused. It helps teams work better and deliver what customers really want.</p>

<h2 id="key-ideas">Key Ideas:</h2>
<ol>
  <li><strong>Keep Customers Happy</strong>: Always aim to deliver what the customer wants, quickly and often.</li>
  <li><strong>Welcome Changes</strong>: If something needs to change, it’s no big deal. Adjust and keep going.
    <ul>
      <li>While no big deal should have fence posts and a defined end to project.  Minor changes are no problem but something big might need to create a new project so that it doesnt derail current project.</li>
    </ul>
  </li>
  <li><strong>Work in Short Cycles</strong>: Break the work into small chunks (called iterations or sprints) that last 1-4 weeks.</li>
  <li><strong>Teamwork</strong>: Work closely with your team and talk a lot to make sure everyone’s on the same page.
    <ul>
      <li>Team can be as small as 1 person</li>
    </ul>
  </li>
  <li><strong>Show Progress</strong>: Always have something to show that works, even if it’s just a small part.</li>
  <li><strong>Keep It Simple</strong>: Do only what’s necessary to get the job done well.</li>
  <li><strong>Self-Organizing</strong>: The team decides the best way to do the work.</li>
  <li><strong>Regular Check-Ins</strong>: Frequently look at how things are going and make improvements.</li>
</ol>

<h2 id="agile-frameworks">Agile Frameworks:</h2>
<ul>
  <li><strong>Scrum</strong>: Work in short sprints, with roles like Scrum Master (coach) and Product Owner (the one who knows what’s needed). Have daily check-ins and review progress regularly.</li>
  <li><strong>Kanban</strong>: Use a board to track tasks (like a to-do list) and limit how many tasks are in progress at once.</li>
  <li><strong>XP (Extreme Programming)</strong>: Focus on writing high-quality code with practices like pair programming (two people work on one task) and test-driven development (write tests before the code).</li>
</ul>

<h2 id="why-its-good">Why It’s Good:</h2>
<ul>
  <li><strong>Flexible</strong>: Can quickly adapt to changes.</li>
  <li><strong>Better Quality</strong>: Continuous testing and feedback improve the product.</li>
  <li><strong>Customer Focused</strong>: Regular updates and feedback ensure it meets customer needs.</li>
  <li><strong>Team Spirit</strong>: Promotes a collaborative and supportive work environment.</li>
</ul>

<h2 id="challenges">Challenges:</h2>
<ul>
  <li><strong>Change is Hard</strong>: It can be tough for some people to get used to this new way of working.</li>
  <li><strong>Big Teams</strong>: Managing large teams with Agile can be tricky.</li>
</ul>

<p>In short, Agile helps teams create better software by working together closely, being flexible, and always focusing on what the customer really needs.</p>

<h2 id="learn-more">Learn More</h2>
<ul>
  <li><a href="https://agilemanifesto.org/">Agile Manifesto</a></li>
  <li><a href="https://scrumguides.org/">Scrum Guide</a></li>
  <li><a href="https://www.atlassian.com/agile/kanban">Kanban</a></li>
  <li><a href="http://www.extremeprogramming.org/">Extreme Programming (XP)</a></li>
</ul>]]></content><author><name></name></author><category term="article" /><category term="education" /><summary type="html"><![CDATA[agile methodology]]></summary></entry><entry><title type="html">Enhance your Learning</title><link href="https://brocketthub.github.io//article/2024/08/10/Learning.html" rel="alternate" type="text/html" title="Enhance your Learning" /><published>2024-08-10T00:00:00+00:00</published><updated>2024-08-10T00:00:00+00:00</updated><id>https://brocketthub.github.io//article/2024/08/10/Learning</id><content type="html" xml:base="https://brocketthub.github.io//article/2024/08/10/Learning.html"><![CDATA[<h1 id="some-of-my-favorite-learning-sites">Some of my favorite learning sites</h1>

<p>This will be a collection of some of my go to sites for learning.  If you have a site that you think I should check out and add to this list then please send it to me.</p>

<ul>
  <li>
    <p><a href="https://www.linkedin.com/learning/creating-github-portfolios/are-you-a-developer-looking-for-a-portfolio?resume=false&amp;u=67698794" target="_blank">How to build a portfolio in Git-Hub</a></p>
  </li>
  <li>
    <p><a href="https://sqlshortreads.com/" target="_blank">SQL refresher</a></p>
  </li>
  <li>
    <p><a href="https://www.youtube.com/watch?v=Vqz2d7pTOV8&amp;list=PLv2BtOtLblH13vCbf99BptWWk-EWx7QQG" target="_blank">Guy in a cube - Power Bi</a></p>
  </li>
</ul>]]></content><author><name>Chris Brockett</name></author><category term="article" /><category term="writing" /><summary type="html"><![CDATA[This article list various sites you can use to enhance your skills and knowlege.]]></summary></entry><entry><title type="html">Product Rating vs Returns</title><link href="https://brocketthub.github.io//work/2024/08/10/Excel.html" rel="alternate" type="text/html" title="Product Rating vs Returns" /><published>2024-08-10T00:00:00+00:00</published><updated>2024-08-10T00:00:00+00:00</updated><id>https://brocketthub.github.io//work/2024/08/10/Excel</id><content type="html" xml:base="https://brocketthub.github.io//work/2024/08/10/Excel.html"><![CDATA[<h2 id="executive-summary">Executive Summary</h2>
<p>To explore if there is a correlation between product ratings and return rates, we analyzed the available data but were unable to see an impact on returns based on the ratings given by customers. The ratings only deviated by 3%, and products with mediocre ratings had the highest sales. This suggests that factors other than quality may influence customer ratings.</p>

<p>We would need to work with the business/it and capture verbatims, shipping delays and follow up with customers to get a better understanding of what is important to the customer.</p>

<p>Check out the excel version <a href="https://1drv.ms/x/s!Agou-xgvW5RZxBepQE0xpTCSkim7?e=YeJur1">Project</a></p>

<iframe src="https://docs.google.com/spreadsheets/d/e/2PACX-1vS5hJ1X57oGWZWlp8BAoUR3eEeI9wRqSuaWvGl9b0Zqz5FzAQe_2uVx0rtzelP1Sg/pubhtml?widget=true&amp;headers=false" width="900" height="400"></iframe>

<h2 id="findings">Findings</h2>
<ul>
  <li>Correlation Between Ratings and Return Rates:
    <ul>
      <li>The ratings of products did not show a significant impact on return rates.</li>
      <li>Ratings varied within a small range (3%), making it difficult to draw a definitive conclusion.</li>
      <li>Products with mediocre ratings had the highest sales, which was unexpected.</li>
    </ul>
  </li>
  <li>Review vs. Transaction Rate:
    <ul>
      <li>Only 7% of transactions had reviews.</li>
      <li>This percentage is satisfactory when compared to other similar surveys.</li>
    </ul>
  </li>
</ul>

<h2 id="follow-up">Follow up</h2>
<ul>
  <li>Survey Capture Verification:
    <ul>
      <li>Investigate how surveys are captured and address any anomalies (e.g., the outlier where there was a survey but no sale).</li>
      <li>Are we capturing verbatims.</li>
    </ul>
  </li>
  <li>Leadership Engagement:
    <ul>
      <li>Engage with leadership to understand if there are current initiatives or budgets allocated to driving survey rates.</li>
    </ul>
  </li>
  <li>Survey Promotion:
    <ul>
      <li>Ensure survey capture methods are robust.</li>
      <li>Gain a deeper understanding of how surveys are promoted to potentially enhance survey response rates.</li>
    </ul>
  </li>
</ul>

<h2 id="final">Final</h2>
<ul>
  <li>If funds are currently being used to improve ratings, consider reallocating these resources to drive survey participation or add additional data points to increase insights.</li>
  <li>Increasing the survey take rate should help in reducing return rates for categories lacking reviews and potentially boost sales.</li>
</ul>

<h2 id="learnings">Learnings</h2>
<ul>
  <li>How to embed worksheet into github</li>
  <li>How to do various different functions in google sheets</li>
</ul>

<h2 id="sql">SQL</h2>
<p>Check out the SQL tab to see some of the sql I used to pull in the data.</p>]]></content><author><name>Chris Brockett</name></author><category term="work" /><category term="Excel" /><summary type="html"><![CDATA[A mix of Sql and Excel]]></summary></entry><entry><title type="html">Real Estate Launch</title><link href="https://brocketthub.github.io//work/2024/08/10/RealEstate.html" rel="alternate" type="text/html" title="Real Estate Launch" /><published>2024-08-10T00:00:00+00:00</published><updated>2024-08-10T00:00:00+00:00</updated><id>https://brocketthub.github.io//work/2024/08/10/RealEstate</id><content type="html" xml:base="https://brocketthub.github.io//work/2024/08/10/RealEstate.html"><![CDATA[<h2 id="executive-summary">Executive Summary</h2>
<p>The primary objective of this project was to analyze Zillow data to provide strategic recommendations for launching a real estate company. Given the drastic downward trend with average homes sold dropping 30% since 2020, I recommend a limited scope launch.</p>

<p>Launching in Los Angeles offers a balanced approach to entering the real estate market, leveraging strong local performance while minimizing broader market risks. This strategy allows for establishing a solid operational foundation and market presence, setting the stage for future growth and expansion.</p>

<h2 id="goal">Goal</h2>
<p>This project was to look at Zillow data and provide recommendations on how to launch a real estate company.  All data used for this project came from Zillow.  This one is a bit different from other projects that I have built as I tailored it for a presentation with the thought of converting it to a tracking tool if the company went live.</p>

<iframe src="/assets/pdf/realestate.pdf" width="900" height="400"></iframe>

<h2 id="project">Project</h2>
<p>I began by analyzing the data to identify trends based on area. While graphing the data, I noticed a drastic change from 2020 to 2023. The Covid lockdowns drove a spike in sales due to increased remote work, but this also led to a subsequent downturn, making it a challenging environment to launch a real estate business.</p>

<h2 id="recommendation">Recommendation</h2>
<p>There were three options to consider: a nationwide launch, a limited scope launch, or no launch at all. Given the 30% decrease in home sales since 2020, launching nationwide carries a high degree of risk. My recommendation is to launch in a single location, such as Los Angeles. Los Angeles still has a strong average number of homes sold per month and a lower mean number of days to close. This approach allows the company to establish its culture, define its market presence, and then expand into other markets.</p>

<p>The last couple of pages outline potential future offerings and data sets that could help the company grow and dive deeper into the business.</p>

<h2 id="dax">Dax</h2>
<p>Used 2 dax calculations to determine the difference between 2023 and 2020.  Set it up to ensure that if they changed the date filter it wouldnt break the results</p>

<p>2023 price = CALCULATE([AVG Sale Price],FILTER(all(‘Calendar Cust’),’Calendar Cust’[Year] = 2023 ))</p>

<p>Calendar function - tied to min /max date off of data project so that if data was updated the calendar updated as well.  Also broke out the date so that I could filter properly and the months would not filter in wrong order.</p>

<p>Calendar Cust = 
ADDCOLUMNS (
    CALENDAR (MIN(‘Client Analyst Data Project - Sales Count’[Month]), max(‘Client Analyst Data Project - Sales Count’[Month])),
    “Calendar Date”, [Date],
    “Year”, YEAR ( [Date] ),
    “Calendar Month”, FORMAT ( [Date], “MMM” ) &amp; “ “ &amp; right(format([Date], “yyyy”),2) ,
    “Calendar Week”, “CY “ &amp; right(format([Date], “yyyy”),2) &amp; “ - “ &amp;FORMAT ( [Date], “MMM” ) &amp; “ WK “ &amp;weeknum([Date]),
    “Month Number”, VALUE(YEAR ( [Date] ) &amp; format(MONTH([Date]),”00”)),
    “Month Sort”,MONTH([Date]),
    “Month Name”, FORMAT ( [Date], “MMMM” ),
    “Day”, DAY ( [Date] ),
    “Day of Week Number”, WEEKDAY ( [Date] ),
    “Day of Week Name”, FORMAT ( [Date], “dddd” )
)</p>
<h2 id="learning">Learning</h2>
<ul>
  <li>It was interesting to see the real estate data and the impact to the market due to Covid</li>
  <li>How to create a calendar function.  So use to having calendars within the databases that I could use.</li>
</ul>]]></content><author><name>Chris Brockett</name></author><category term="work" /><category term="PBI" /><summary type="html"><![CDATA[A mix of Sql and PBI]]></summary></entry><entry><title type="html">Animal Shelter</title><link href="https://brocketthub.github.io//work/2024/08/10/AnimalShelter.html" rel="alternate" type="text/html" title="Animal Shelter" /><published>2024-08-10T00:00:00+00:00</published><updated>2024-08-10T00:00:00+00:00</updated><id>https://brocketthub.github.io//work/2024/08/10/AnimalShelter</id><content type="html" xml:base="https://brocketthub.github.io//work/2024/08/10/AnimalShelter.html"><![CDATA[<h2 id="executive-summary">Executive Summary</h2>
<p>We are successfully maintaining our no-kill shelter status by staying above the 90% threshold, currently achieving a 93.9% live release rate. While this is commendable, it marks an 8% decrease from the previous year.</p>

<p>The primary factor contributing to this decline is the incidence of rabies within the “other” classification of animals. To address this issue, it is recommended to:</p>

<ul>
  <li>Stop accepting bats and raccoons. Currently, these animals have a combined successful release rate of only 10%. By preventing them from being taken in, we can increase our overall success rate for this year to 96%.</li>
  <li>Check with state laws to see if these animals should count within the no kill percentage.</li>
  <li>Targeted Health Interventions: Implement focused health and safety measures for the identified animals to reduce rabies cases.</li>
</ul>

<p>By addressing these areas, we can work towards improving our live release rate and ensure the ongoing success of our no-kill shelter.</p>

<iframe src="/assets/pdf/Animal no kill.pdf" width="900" height="400"></iframe>

<h2 id="project">Project</h2>
<p>Since I have been volunteering with an animal shelter, this data was fun to peek at to understand more about how shelters work.</p>

<h2 id="data-cleaning">Data Cleaning</h2>
<p>This particular data set threw some unique challenges.  I expected some duplication within the data as some animals could come through the system multiple times.  To check I performed a ranking function within power query to see if that would remove duplications based on animal id and date.  There were still duplications but since it was only 90 records out of 160 k, I just had power query remove duplicates.</p>

<h2 id="dax">Dax</h2>
<p>To compare this year vs last year crafted 2 dax measures and set them up so if they changed filters it wouldnt change the value.  Here is one of them.
Current Year = CALCULATE([Cases], filter(all(Austin_Animal_Center_Outcomes_20240818),year(Austin_Animal_Center_Outcomes_20240818[DateTime])=year(today())&amp;&amp; Austin_Animal_Center_Outcomes_20240818[Outcome Type] = “Euthanasia” )) / CALCULATE([Cases], filter(all(Austin_Animal_Center_Outcomes_20240818),year(Austin_Animal_Center_Outcomes_20240818[DateTime])=year(today())))</p>

<h2 id="future">Future</h2>
<ul>
  <li>See why there was data duplication within data set.</li>
  <li>Look at transfers and spray and neuter rates.  See if there is data points on reasons for transfers and what it would take to convert transfers to adoptions.  Also saw that it was possible that animals were being transfered / adopted without being spayed or neutered.  Currently no data points as why but this would be a good data point to look at to drive to 100%.</li>
</ul>

<h2 id="learning">Learning</h2>
<p>How to do ranking within power query</p>]]></content><author><name>Chris Brockett</name></author><category term="work" /><category term="PBI" /><summary type="html"><![CDATA[A mix of excel and PBI]]></summary></entry><entry><title type="html">Pizza Restaurant</title><link href="https://brocketthub.github.io//work/2024/08/10/Pizza.html" rel="alternate" type="text/html" title="Pizza Restaurant" /><published>2024-08-10T00:00:00+00:00</published><updated>2024-08-10T00:00:00+00:00</updated><id>https://brocketthub.github.io//work/2024/08/10/Pizza</id><content type="html" xml:base="https://brocketthub.github.io//work/2024/08/10/Pizza.html"><![CDATA[<h2 id="executive-summary">Executive Summary</h2>
<p>Our initial goal was to provide recommendations for business improvements based on the sales data. However, during our analysis, we identified several data discrepancies that need to be addressed before moving forward.
Key issues include:</p>
<ul>
  <li>Unusually Low Monthly Sales Variance: The sales data shows a surprisingly uniform monthly variance ranging from only $12 to $280, which is atypical for a retail operation and raises concerns about data accuracy.</li>
  <li>Limited Pizza Variety: The data indicates that only one type of pizza was sold in XL or XXL sizes, which is unusual for a business that typically offers a variety of options.</li>
  <li>Topping Distribution: It was found that only 50% of pizzas were sold with a cheese topping, and garlic was listed as the most popular topping. These patterns are inconsistent with standard consumer preferences and further suggest potential data integrity issues.
Given these anomalies, it’s crucial to pause on making any business recommendations. I recommend scheduling a meeting with the business owner to review these findings and determine if they align with their expectations. If discrepancies are confirmed, we should collaborate with the IT department to investigate and rectify the data issues before proceeding with our analysis.
This will ensure that any future recommendations are based on accurate and reliable data.</li>
</ul>

<h2 id="project-summary">Project Summary</h2>

<p>The initial objective of this project was to analyze sales trends over time, focusing on different types of pizzas down to the ingredient level. The insights gathered would have been utilized for forecasting ingredient usage and optimizing stocking levels.</p>

<h2 id="data-validation">Data Validation</h2>
<p>During the data build-out, I noticed that the data appeared unusually uniform. This prompted a deeper investigation, revealing several anomalies that raised concerns about the accuracy of the data:</p>

<ul>
  <li>Size Discrepancy: Sales of XL and XXL pizzas were exceptionally low, with only one type of pizza sold in these sizes.</li>
  <li>Cheese Topping Issue: Surprisingly, cheese, a common topping, was only present on 50% of the pizzas, which is highly irregular.</li>
</ul>

<h2 id="data-preparation">Data Preparation</h2>
<p>In preparation for a more detailed analysis, I aimed to explore the topping distribution in depth. To achieve this, I:</p>

<ul>
  <li>Duplicated the table and removed unnecessary rows.</li>
  <li>Split the ingredients by commas and unpivoted the data to tie it back to the main table.</li>
</ul>

<p>This process revealed another inconsistency: garlic emerged as the most frequent topping, which was unexpected.</p>

<h2 id="next-steps">Next Steps</h2>
<p>Given these discrepancies, the following actions are recommended:</p>

<ul>
  <li>Business Consultation: Engage with the business owner to verify whether these data patterns were expected.</li>
  <li>IT Collaboration: If the data is found to be inaccurate, collaborate with IT to identify the source of the issue and implement necessary fixes.</li>
</ul>

<h2 id="learnings">Learnings</h2>
<p>This experience reinforced the importance of trusting instincts when data appears abnormal. Continued diligence in investigating anomalies ensures the integrity of the analysis.</p>]]></content><author><name>Chris Brockett</name></author><category term="work" /><category term="PBI" /><summary type="html"><![CDATA[A mix of excel and PBI]]></summary></entry><entry><title type="html">Welcome to Jekyll!</title><link href="https://brocketthub.github.io//article/2024/08/09/welcome-to-jekyll.html" rel="alternate" type="text/html" title="Welcome to Jekyll!" /><published>2024-08-09T10:24:42+00:00</published><updated>2024-08-09T10:24:42+00:00</updated><id>https://brocketthub.github.io//article/2024/08/09/welcome-to-jekyll</id><content type="html" xml:base="https://brocketthub.github.io//article/2024/08/09/welcome-to-jekyll.html"><![CDATA[<p>You’ll find this post in your <code class="language-plaintext highlighter-rouge">_posts</code> directory. Go ahead and edit it and re-build the site to see your changes. You can rebuild the site in many different ways, but the most common way is to run <code class="language-plaintext highlighter-rouge">jekyll serve</code>, which launches a web server and auto-regenerates your site when a file is updated.</p>

<p>Jekyll requires blog post files to be named according to the following format:</p>

<p><code class="language-plaintext highlighter-rouge">YEAR-MONTH-DAY-title.MARKUP</code></p>

<p>Where <code class="language-plaintext highlighter-rouge">YEAR</code> is a four-digit number, <code class="language-plaintext highlighter-rouge">MONTH</code> and <code class="language-plaintext highlighter-rouge">DAY</code> are both two-digit numbers, and <code class="language-plaintext highlighter-rouge">MARKUP</code> is the file extension representing the format used in the file. After that, include the necessary front matter. Take a look at the source for this post to get an idea about how it works.</p>

<p>Jekyll also offers powerful support for code snippets:</p>

<figure class="highlight"><pre><code class="language-ruby" data-lang="ruby"><span class="k">def</span> <span class="nf">print_hi</span><span class="p">(</span><span class="nb">name</span><span class="p">)</span>
  <span class="nb">puts</span> <span class="s2">"Hi, </span><span class="si">#{</span><span class="nb">name</span><span class="si">}</span><span class="s2">"</span>
<span class="k">end</span>
<span class="n">print_hi</span><span class="p">(</span><span class="s1">'Tom'</span><span class="p">)</span>
<span class="c1">#=&gt; prints 'Hi, Tom' to STDOUT.</span></code></pre></figure>

<p>Check out the <a href="https://jekyllrb.com/docs/home">Jekyll docs</a> for more info on how to get the most out of Jekyll. File all bugs/feature requests at <a href="https://github.com/jekyll/jekyll">Jekyll’s GitHub repo</a>. If you have questions, you can ask them on <a href="https://talk.jekyllrb.com/">Jekyll Talk</a>.</p>]]></content><author><name></name></author><category term="article" /><category term="education" /><summary type="html"><![CDATA[this is an article about education]]></summary></entry><entry><title type="html">The B.A.R.N. Framework</title><link href="https://brocketthub.github.io//article/2023/07/14/BARN.html" rel="alternate" type="text/html" title="The B.A.R.N. Framework" /><published>2023-07-14T21:13:27+00:00</published><updated>2023-07-14T21:13:27+00:00</updated><id>https://brocketthub.github.io//article/2023/07/14/BARN</id><content type="html" xml:base="https://brocketthub.github.io//article/2023/07/14/BARN.html"><![CDATA[<h1 id="introduction">Introduction</h1>
<p>Writing about your projects is crucial to giving context for the work. Writing an impactful article requires a structured approach that captures readers’ attention and delivers valuable insights. I use my BARN framework to achieve this goal: Background, Approach, Results, and Next Steps. In this article, we will delve into each element of the BARN framework and explore how it can enhance your writing skills.</p>

<h2 id="background">Background:</h2>
<p>The Background section of an article serves as the foundation, providing context and establishing the relevance of the topic. It sets the stage for readers to understand the problem or subject matter being addressed. To effectively craft this section, consider the following:</p>

<p><strong>1. Hook the readers:</strong> Begin with an engaging hook or anecdote that grabs readers’ attention and piques their curiosity.</p>

<p><strong>2. Problem statement:</strong> Clearly define the problem or questions that your project aims to address. Explain why it is significant and how it relates to the readers’ interests or concerns.</p>

<h2 id="approach">Approach:</h2>
<p>The Approach section outlines the methodology or approach used to investigate the problem or answer the problem statement. It is essential to provide readers with a clear understanding of how the research or analysis was conducted. Consider the following when constructing this section:</p>

<p><strong>1. Methodology:</strong> Describe the research design, data collection methods, and any tools or techniques employed. Ensure your explanation is concise yet comprehensive enough to allow readers to undestand your process.</p>

<p><strong>2. Data analysis:</strong> If applicable, detail the analysis techniques used to interpret the gathered data. This could include statistical methods, qualitative analysis, or any other relevant procedures.</p>

<p><strong>3. Assumptions and limitations:</strong> Acknowledge any assumptions made during the process and highlight the potential limitations. Call out any challenges you faced. This demonstrates transparency and helps readers evaluate the validity of the results.</p>

<h2 id="results">Results:</h2>
<p>The Results section presents the key findings and outcomes of your research or analysis. It is crucial to present this information in a clear and organized manner to facilitate readers’ understanding. Consider the following tips:</p>

<p><strong>1. Summarize findings:</strong> Provide a concise summary of the main findings, focusing on the most important and impactful results.</p>

<p><strong>2. Visual aids:</strong> Utilize charts, graphs, tables, or screenshots to present complex data in a visually appealing and accessible format. This enhances reader comprehension and engagement.</p>

<p><strong>3. Interpretation:</strong> Offer a thoughtful interpretation of the results, highlighting their significance in relation to the problem statement and the existing body of knowledge. Consider addressing unexpected or conflicting findings and proposing potential explanations.</p>

<h2 id="next-steps">Next Steps:</h2>
<p>The Next Steps section outlines potential future directions, implications, or recommendations based on the findings of your article. This section demonstrates your forward-thinking approach and encourages further exploration of the topic. Consider the following aspects:</p>

<p><strong>1. Implications:</strong> Discuss the broader implications of your findings and how they contribute to the field of study or the problem at hand. Consider societal, economic, or practical implications.</p>

<p><strong>2. Recommendations:</strong> Offer recommendations for further research or actions that can be taken based on your results. This could include areas that require additional investigation, potential applications, or suggested policy changes.</p>

<p><strong>3. Conclusion:</strong> Summarize the key points discussed in your article, emphasizing the value and impact of your project.</p>

<h2 id="conclusion">Conclusion</h2>
<p>Mastering the art of writing about your project requires a systematic and well-structured approach. The BARN framework, encompassing Background, Approach, Results, and Next Steps, provides a roadmap for creating engaging and informative articles. By leveraging this framework, you can effectively convey the context, methodology, findings, and future implications of your work, capturing readers’ attention and leaving a lasting impact in your field of expertise. So, pick up your pen or open your word processor, and let the BARN framework guide you on your journey to becoming a skilled and influential article writer.</p>]]></content><author><name>Leigh Stewardson</name></author><category term="article" /><category term="writing" /><summary type="html"><![CDATA[This article explains the BARN method, a framework for showcasing your projects.]]></summary></entry></feed>