<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Fujitsu Agile Development Guidebook on Fujitsu Agile Development Guide</title><link>https://onebase-fujitsu.github.io/agile-dev-guide/en/</link><description>Recent content in Fujitsu Agile Development Guidebook on Fujitsu Agile Development Guide</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 01 Jan 0001 00:00:00 +0000</lastBuildDate><atom:link href="https://onebase-fujitsu.github.io/agile-dev-guide/en/index.xml" rel="self" type="application/rss+xml"/><item><title>Introduction</title><link>https://onebase-fujitsu.github.io/agile-dev-guide/en/docs/introduction/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://onebase-fujitsu.github.io/agile-dev-guide/en/docs/introduction/</guid><description>&lt;h1 id="introduction"&gt;&#10; Introduction&#10; &lt;a class="anchor" href="#introduction"&gt;#&lt;/a&gt;&#10;&lt;/h1&gt;&#10;&lt;p&gt;Agile development and in-house development have been talked about for quite some time now, and our company is no exception.&#10;However, unlike the traditional waterfall approach, agile development cannot be done in a one-size-fits-all way,&#10;and for that reason it has also been an area where knowledge has rarely been put into writing.&lt;/p&gt;&#10;&lt;p&gt;If things stay that way, knowledge becomes concentrated in a few individuals, and the organization cannot scale agile development.&#10;Experience is extremely important in agile development.&#10;It is essential to actually go through the development process, internalize it, and make it a habit.&#10;In the first place, you will not become able to do agile development just by taking a particular training course,&#10;nor will you become able to do it just by reading this guide.&lt;/p&gt;</description></item></channel></rss>