<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Workflow / BPM - Articles</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Workflow / BPM Articles feed</description>
    <item>
      <title>Article: Building Workflows with AWS Step Functions</title>
      <link>https://www.infoq.com/articles/workflows-aws-step-functions/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Workflow+%2F+BPM-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/workflows-aws-step-functions/en/headerimage/building-workflows-with-AWS-step-functions-header-1661853537630.jpg"/&gt;&lt;p&gt;AWS Step Functions use a state machine to represent the workflow. A workflow consists of a set of tasks, each of which represents a discrete activity to be performed. Each task is defined by a state of the state machine. In this article, we will learn about the main concepts of AWS Step Functions and apply those to build a workflow for a sample business process: Order Fulfillment.&lt;/p&gt; &lt;i&gt;By Pratik Das&lt;/i&gt;</description>
      <category>Workflow / BPM</category>
      <category>Amazon Web Services</category>
      <category>AWS Lambda</category>
      <category>FaaS</category>
      <category>Cloud</category>
      <category>AWS</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>DevOps</category>
      <category>article</category>
      <pubDate>Thu, 01 Sep 2022 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/workflows-aws-step-functions/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Workflow+%2F+BPM-articles</guid>
      <dc:creator>Pratik Das</dc:creator>
      <dc:date>2022-09-01T09:00:00Z</dc:date>
      <dc:identifier>/articles/workflows-aws-step-functions/en</dc:identifier>
    </item>
    <item>
      <title>Article: The Implication of Feedback Loops for Value Streams</title>
      <link>https://www.infoq.com/articles/feedback-loops-value-streams/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Workflow+%2F+BPM-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/feedback-loops-value-streams/en/headerimage/the-implication-of-feedback-loops-for-value-streams-header-1661774785949.jpg"/&gt;&lt;p&gt;Lead time and throughput are dynamic variables which impact flow in a value stream.  Capacity, processing time and feedback loops (such as error conditions) have a significant impact on WIP and flow and need to be mapped and measured when building value stream maps.&lt;/p&gt; &lt;i&gt;By Pavel Azaletskiy, Jack Maher&lt;/i&gt;</description>
      <category>Workflow / BPM</category>
      <category>Value Stream Mapping</category>
      <category>Culture &amp; Methods</category>
      <category>article</category>
      <pubDate>Wed, 31 Aug 2022 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/feedback-loops-value-streams/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Workflow+%2F+BPM-articles</guid>
      <dc:creator>Pavel Azaletskiy, Jack Maher</dc:creator>
      <dc:date>2022-08-31T09:00:00Z</dc:date>
      <dc:identifier>/articles/feedback-loops-value-streams/en</dc:identifier>
    </item>
  </channel>
</rss>
