<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
   <channel>
      <title>Bringing Sanity to Software Engineering</title>
      <link>http://axisitconsulting.com/</link>
      <description></description>
      <language>en</language>
      <copyright>Copyright 2008</copyright>
      <lastBuildDate>Mon, 11 Feb 2008 20:13:54 -0500</lastBuildDate>
      <generator>http://www.sixapart.com/movabletype/?v=3.2ysb5-20051201</generator>
      <docs>http://blogs.law.harvard.edu/tech/rss</docs> 

            <item>
         <title>SDLC vs. Project Execution Process</title>
         <description><![CDATA[<p><strong>No-Brainer</strong></p><p>This one seems like such a no-brainer that we don't even need to discuss it. So, why post it then?</p><p>Because I still encouter people on a regular basis that discuss Software Engineering in the context of Project Management who fail to make the distinction between the Software Development LifeCycle (SDLC) and the Project Execution Process (PEP).<br /></p><p>This failure to recognize the larger process has a litany of perils associated with it and it deserves some discussion as a way to put the PEP back in the Project Driver's Seat.<br /></p>]]></description>
         <link>http://axisitconsulting.com/blog/2008/02/sdlc_vs_project_execution_proc.html</link>
         <guid>http://axisitconsulting.com/blog/2008/02/sdlc_vs_project_execution_proc.html</guid>
         <category>High Performance Project Management</category>
         <pubDate>Mon, 11 Feb 2008 20:13:54 -0500</pubDate>
      </item>
            <item>
         <title>Bringing Sanity to &quot;Unclassfied&quot; (Under Radar) Activities:  Part 1, The Foundation</title>
         <description><![CDATA[<p class="msonospacing"><strong><span style="font-size: 10pt; font-family: Arial">For the Purists</span></strong></p>   <p class="msonospacing"><span style="font-size: 10pt; font-family: Arial">We&rsquo;ll begin by saying that this entry is specifically aimed at &ldquo;Maintenance&rdquo; or &ldquo;Operational&rdquo; activities and can be considered Part 1 of a multi-part series on bringing sanity to these necessary and challenging activities.</span></p>   <p class="msonospacing"><span style="font-size: 10pt; font-family: Arial">Before the purists begin to revolt at my last statement, let me say that there is a dangerous fallacy in trying to manage Operational activities as &quot;Projects&quot; and that is precisely what I intend to discuss here.</span></p><p class="msonospacing"><span style="font-size: 10pt; font-family: Arial">I hope that quelled the uprising.</span></p>]]></description>
         <link>http://axisitconsulting.com/blog/2008/01/bringing_sanity_to_unclassfied.html</link>
         <guid>http://axisitconsulting.com/blog/2008/01/bringing_sanity_to_unclassfied.html</guid>
         <category>Project Recovery</category>
         <pubDate>Sat, 19 Jan 2008 10:21:01 -0500</pubDate>
      </item>
            <item>
         <title>Project Recovery Efforts: The Struggling Project</title>
         <description><![CDATA[<p>First, what do I mean by &quot;<em>Project Recovery</em>&quot;?</p><p>Project Recovery is the effort and activities related to addressing troubled projects.&nbsp; In other words, the activities that lead you to recognize that&nbsp;the project is troubled, then bring you to a decision point on whether or not to save&nbsp;that project, then those activities you might undertake to drive that project to completion.</p>]]></description>
         <link>http://axisitconsulting.com/blog/2007/12/project_recovery_efforts_the_s.html</link>
         <guid>http://axisitconsulting.com/blog/2007/12/project_recovery_efforts_the_s.html</guid>
         <category>For Starters</category>
         <pubDate>Sun, 02 Dec 2007 17:26:02 -0500</pubDate>
      </item>
            <item>
         <title>Legitimizing the Project Manager Role</title>
         <description><![CDATA[<p>For openers, let's look at the meaning of the term &quot;Legitimize&quot;.&nbsp; Merriam-Webster says &quot;To make legitimate.&quot;&nbsp; Enough said, right?&nbsp; If it were, then this would be a very short post.</p><p>This post is dedicated to a better understanding of what&nbsp;a Project Manager&nbsp;is and what a Project Manager does.&nbsp; Just as important, we will also be talking about what a Project Managser isn't.</p><p>I feel compelled because I have heard the following conversation take place in <em>every</em> company for which I have provided services, <em>ever</em>.</p>]]></description>
         <link>http://axisitconsulting.com/blog/2007/11/what_or_who_makes_a_good_proje.html</link>
         <guid>http://axisitconsulting.com/blog/2007/11/what_or_who_makes_a_good_proje.html</guid>
         <category>Leadership Tips for PM</category>
         <pubDate>Wed, 21 Nov 2007 20:19:29 -0500</pubDate>
      </item>
            <item>
         <title>PM Skills - Not Just for PM&apos;s Anymore</title>
         <description><![CDATA[<p>Project Management expertise is traditionally thought of as encompassing scheduling and organizational skills in addition to some subject matter expertise.</p><p>Although, in&nbsp;considering the notion in greater detail, we have tasked our Project Managers with ultimate delivery of important products and services and we would be foolish to trust ultimate delivery of key products and services to&nbsp;a gatekeeper that is simply responsible for managing the project schedule.</p>]]></description>
         <link>http://axisitconsulting.com/blog/2007/10/pm_skills_not_just_for_pms_any.html</link>
         <guid>http://axisitconsulting.com/blog/2007/10/pm_skills_not_just_for_pms_any.html</guid>
         <category>High Performance Project Management</category>
         <pubDate>Mon, 15 Oct 2007 20:21:26 -0500</pubDate>
      </item>
            <item>
         <title>A Tale of Cost Performance Index and Schedule Performance Index (CPI and SPI)</title>
         <description><![CDATA[<span style="font-size: 7.5pt; font-family: Verdana">Cost Performance Index (CPI) and Schedule Performance Index (SPI) are the yardsticks by which we measure how well our project is tracking against cost and schedule, right? </span><span style="font-size: 7.5pt; font-family: Verdana">Although, we use these two very important popular measurements as the yardstick of success we sometimes do so without realizing that they are still open to interpretation.</span>]]></description>
         <link>http://axisitconsulting.com/blog/2007/03/schedule_performance_index_and.html</link>
         <guid>http://axisitconsulting.com/blog/2007/03/schedule_performance_index_and.html</guid>
         <category>High Performance Project Management</category>
         <pubDate>Thu, 01 Mar 2007 19:51:18 -0500</pubDate>
      </item>
            <item>
         <title>Should I Rescue My Failing Project?</title>
         <description><![CDATA[<p><span>Some may be confused when I pose this question.&nbsp; After all, it seems counter-intuitive to think in terms of <em><span>whether or not</span></em> to save a troubled project because Project Management Professionals are constantly challenged to find new and creative ways to guide projects to success.<br /></span></p><p><span>As a Project Recovery Specialist, I am constantly reminded of the perils of attempting to save the wrong project for the wrong reasons.&nbsp; While the reasons one might choose to attempt to save a project are relatively simple, the reasons one might choose <em><span>not</span></em> to save a project&nbsp;can be&nbsp;much more complex.</span><span><span><span><span><span /></span></span></span></span></p>]]></description>
         <link>http://axisitconsulting.com/blog/2007/02/project_recovery_when_is_it_a_bad_idea_to_save_a_troubled_project_part_1.html</link>
         <guid>http://axisitconsulting.com/blog/2007/02/project_recovery_when_is_it_a_bad_idea_to_save_a_troubled_project_part_1.html</guid>
         <category>Project Recovery</category>
         <pubDate>Mon, 05 Feb 2007 19:16:31 -0500</pubDate>
      </item>
            <item>
         <title>Using the Right Amount of Project Management Discpline for Your Project</title>
         <description><![CDATA[<p>I am asked this question frequently:&nbsp; &quot;How much Project Management process should I place on the [insert project name] Project?&quot;.</p><p>Most PM's and Executives struggle with this question because it seems as if a rigid and thick process can kill smaller projects and at the same time a very lightweight and agile process may not be enough to guide a complex project to success.</p>]]></description>
         <link>http://axisitconsulting.com/blog/2006/12/how_much_process_should_we_pla.html</link>
         <guid>http://axisitconsulting.com/blog/2006/12/how_much_process_should_we_pla.html</guid>
         <category>High Performance Project Management</category>
         <pubDate>Fri, 15 Dec 2006 19:43:46 -0500</pubDate>
      </item>
            <item>
         <title>Can You Make a Project Manager Out of Fairy Dust?</title>
         <description><![CDATA[<p>Can You Make a Project Manager Out of Fairy Dust?&nbsp;</p><p>Sure, with enough Fairy Dust and some wishful thinking, anyone&nbsp;can make a Worldclass Software Engineer or a Pipefitter, or a Chemical Engineer out of Fairy Dust too, right?&nbsp; You Can't?&nbsp; Then why are Project Managers different?</p><p>We all know I am simply making a point here and that is that the role of PM is often minimized in the minds of those contemplating the notion.&nbsp; For some reason, when some people think of a Project manager, they think of someone that simply manages a task list in a scheduling tool, or someone we only see when we've overrun our budget.</p><p>This in itself has been the cause of many project failures.</p>]]></description>
         <link>http://axisitconsulting.com/blog/2006/11/can_you_make_a_project_manager.html</link>
         <guid>http://axisitconsulting.com/blog/2006/11/can_you_make_a_project_manager.html</guid>
         <category>For Starters</category>
         <pubDate>Fri, 17 Nov 2006 19:25:50 -0500</pubDate>
      </item>
      
   </channel>
</rss>

