<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>IT Planning on Sulprobil</title>
    <link>https://www.sulprobil.de/tags/it-planning/</link>
    <description>Recent content in IT Planning on Sulprobil</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 03 Jun 2026 03:45:00 +0100</lastBuildDate>
    <atom:link href="https://www.sulprobil.de/tags/it-planning/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>IT Planning</title>
      <link>https://www.sulprobil.de/it_planning_en/</link>
      <pubDate>Wed, 03 Jun 2026 03:45:00 +0100</pubDate>
      <guid>https://www.sulprobil.de/it_planning_en/</guid>
      <description>&lt;p&gt;&lt;strong&gt;&amp;ldquo;Adventure is just bad planning.&amp;rdquo; [Roald Amundsen]&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;h2 id=&#34;abstract&#34;&gt;Abstract&lt;/h2&gt;&#xA;&lt;p&gt;If you have to make a plan for an IT project, think BIG:&#xA;What will the environment of your application look like ten years from now?&#xA;Five years? One year? The scope of your timeframe as well as the scope of your&#xA;application will define the range or the necessary depth of your plan.&lt;/p&gt;&#xA;&lt;p&gt;If you develop together with five colleagues or more, consider using Microsoft Project.&#xA;I used it only to devise an initial project plan, never to monitor a project during execution.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
