<?xml version='1.0' encoding='UTF-8'?><rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearchrss/1.0/" xmlns:blogger="http://schemas.google.com/blogger/2008" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" version="2.0"><channel><atom:id>tag:blogger.com,1999:blog-1733080910397920398</atom:id><lastBuildDate>Sat, 31 Aug 2024 06:12:01 +0000</lastBuildDate><category>release planning</category><category>scrum</category><category>Freemind</category><category>agile</category><category>brainstorming</category><category>customer</category><category>epics</category><category>interviews</category><category>mind-map</category><category>organizing</category><category>product owner</category><category>retrospective</category><category>user stories</category><title>Scrum Shepherd</title><description>Sharing my successes and failures of getting a distributed development shop up to speed on implementing scrum and agile techniques.  &#xa; Anything that I can do to help others in similar situations or connect with people to offer me ideas is the goal of this blog.</description><link>http://scrumshepherd.blogspot.com/</link><managingEditor>noreply@blogger.com (Janine)</managingEditor><generator>Blogger</generator><openSearch:totalResults>6</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1733080910397920398.post-6177949109909657772</guid><pubDate>Sat, 06 Jun 2009 13:48:00 +0000</pubDate><atom:updated>2009-06-06T10:27:12.189-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">epics</category><category domain="http://www.blogger.com/atom/ns#">interviews</category><category domain="http://www.blogger.com/atom/ns#">mind-map</category><title>Customer Interviews</title><atom:summary type="text">In preparing for the next release as well as defining a &quot;bigger picture&quot;, our Product Owner has been conducting extensive customer interviews.  This has involved traveling to their sites as well as phone interviews.  As I sat in on these calls, for the first time, I was able to get a better perspective on customers pain-points, desires, rational for certain functionality as well as what&#39;s good </atom:summary><link>http://scrumshepherd.blogspot.com/2009/06/customer-interviews.html</link><author>noreply@blogger.com (Janine)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1733080910397920398.post-6897361641768500700</guid><pubDate>Mon, 25 May 2009 01:11:00 +0000</pubDate><atom:updated>2009-05-24T21:25:29.361-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">customer</category><category domain="http://www.blogger.com/atom/ns#">release planning</category><title>Approaching the finish line of a release</title><atom:summary type="text">We are winding down with a release and I am already thinking about the next one.  What can be done better the next time around?  Well, for one thing, having a release backlog before the release.  I&#39;m happy to say that there is more talk about users and framing our next release from the user&#39;s perspective.  I&#39;m hoping that starting from the top we can generate some good epics and then break them </atom:summary><link>http://scrumshepherd.blogspot.com/2009/05/approaching-finish-line-of-release.html</link><author>noreply@blogger.com (Janine)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1733080910397920398.post-5278046624347233722</guid><pubDate>Tue, 28 Apr 2009 02:37:00 +0000</pubDate><atom:updated>2009-04-27T23:40:02.447-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">release planning</category><category domain="http://www.blogger.com/atom/ns#">scrum</category><category domain="http://www.blogger.com/atom/ns#">user stories</category><title>defining users</title><atom:summary type="text">With the next release closing in, and a new one to think about, I want to be better prepared with a release backlog.  Since last release focus was getting everyone familiar and up to speed with scrum, some things fell to the wayside.  Now that the teams are familiar with the general rhythm of a sprint cycle, I want to focus my efforts on having a better 6-month plan, in addition to fine-tuning </atom:summary><link>http://scrumshepherd.blogspot.com/2009/04/defining-users.html</link><author>noreply@blogger.com (Janine)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1733080910397920398.post-2883365621177907408</guid><pubDate>Mon, 27 Apr 2009 01:35:00 +0000</pubDate><atom:updated>2009-04-28T12:42:30.962-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">organizing</category><category domain="http://www.blogger.com/atom/ns#">product owner</category><title>How to organize?</title><atom:summary type="text">It&#39;s difficult trying to be up and keep people energized.   Not to mention the lack of direction of future goals.  I see it as a problem, but don&#39;t know how to attack this situation. I&#39;ve got most of the team into the &quot;flow&quot; of scrum...although I&#39;m sensing a dullness.   How do I challenge the teams in a positive and encouraging way?  And how does one get a PO organized with a vision?  Maybe my </atom:summary><link>http://scrumshepherd.blogspot.com/2009/04/can-economy-crush-me-again.html</link><author>noreply@blogger.com (Janine)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1733080910397920398.post-1395861435934790757</guid><pubDate>Tue, 14 Apr 2009 03:26:00 +0000</pubDate><atom:updated>2009-04-27T23:15:57.160-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">brainstorming</category><category domain="http://www.blogger.com/atom/ns#">Freemind</category><category domain="http://www.blogger.com/atom/ns#">retrospective</category><title>Retrospective on a Retrospective</title><atom:summary type="text">I&#39;ll have to fill in all the pieces as to what lead me to where I am right now during a later time.  If I wait to do that before I can actually blog my days, I&#39;ll never get current.So anyway, we had our 3rd retrospective last week.  The first two were pretty similar in format.  Since I am running...(not really sure what my role is actually) but since I am the Scrum Shepherd, so-to-speak, I am </atom:summary><link>http://scrumshepherd.blogspot.com/2009/04/retrospective-on-retrospective.html</link><author>noreply@blogger.com (Janine)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1733080910397920398.post-8043392450019203548</guid><pubDate>Sat, 28 Mar 2009 23:11:00 +0000</pubDate><atom:updated>2009-04-27T22:27:00.156-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">agile</category><category domain="http://www.blogger.com/atom/ns#">scrum</category><title>I should have thought of this sooner</title><atom:summary type="text">While attending the Emerging Technology for the Enterprise conference yesterday, I was talking with a former co-worker of my woes at my current position as a scrum master.  I&#39;ve been feeling nothing but frustrations and fighting an uphill battle for the past few months since I&#39;ve been hired at a company as a project manager to implement scrum to a company that was no using any formal methodology.</atom:summary><link>http://scrumshepherd.blogspot.com/2009/03/i-should-have-thought-of-this-sooner.html</link><author>noreply@blogger.com (Janine)</author><thr:total>0</thr:total></item></channel></rss>