<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:s="http://www.techrepublic.com/search" xmlns:dc="http://purl.org/dc/elements/1.1/"  xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
    <title><![CDATA[Discussion on Planning Projects portfolios ]]></title>
    <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-279237]]></link>
    <atom:link rel="hub" type="application/rss+xml" href="http://pubsubhubbub.appspot.com/" />
    <atom:link rel="self" type="application/rss+xml" href="http://www.techrepublic.com/forum/discussions/102-279237/rss" />

    <description><![CDATA[]]></description>
    <language>en-us</language>
    <lastBuildDate>2013-05-23T10:03:12-07:00</lastBuildDate>
             

    <item>
        <title><![CDATA[Planning Projects portfolios]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-279237-2644063]]></link>
        <description><![CDATA[Can anyone provide me with examples of strategies they have employed to plan and prioritise projects. I personally like the thought of having a pipeline of &quot;things to do&quot;, change requests, defects, new features etc.. which are added to a backlog and prioritised by Product Owner(s)...but how can this work at a say corporate level, can a Giant SCRUM work which feeds into multiple teams that pick the &quot;things to do&quot; from the prioritised list work? We like most companies are constrained by resource so I see a kanban style as a possible way to feed the development teams, but not sure how this would work in practice, anyone shed any light on how they have done this.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-279237-2644063]]></guid>
        <dc:creator><![CDATA[kevin@...]]></dc:creator>
        <pubDate>Thu, 20 Nov 2008 15:24:29 -0800</pubDate>
    </item>
    </channel>
</rss>

