Loading ...
Sorry, an error occurred while loading the content.

36270RE: [scrumdevelopment] Any recommendations on tools for Product Owner?

Expand Messages
  • Roy Morien
    Jan 29, 2009
    • 0 Attachment
      Got it! :) But your explanation here makes me more convinced that you should start simple, and take it from there. First establish a need for something more technically complex than the shoe box and 3" x 5" cards that someone else has suggested, or the simple spreadhseet that I have suggested, then upgrade if necessary. Gain the experience of the simple solution before you assume it is inadequate. A simple solution is quicker and easier to implement, and iof you get it wrong, your wasted time is minimal.
       
      The other end of this scale was demonstrated in the 80s with the huge, monumental CASE tools tha were available at the time. Companies that bought into these had a huge job of implementing them, training personell, getting them to work in their organisation. They then found that they were tied in very tightly. If they decided to move away from them, the sunk cost was enormous, the transfer costs were enormous.
       
      So, don't try to 'get it right' right at the start by introducing apparently useful but complex tools, just in case the features are needed.
       
      Regards,
      Roy Morien




      To: scrumdevelopment@yahoogroups.com
      From: nikhil@...
      Date: Thu, 29 Jan 2009 23:06:47 -0800
      Subject: RE: [scrumdevelopment] Any recommendations on tools for Product Owner?


      Don’t get me wrong!!! These executives are not fighting as such over the tool. We have a ton of ideas for 2009 that need to be prioritized and then executed upon.

       

      The problem I am seeing is that arriving at a consensus on deciding which is the right order of tackling those priorities is getting difficult. Believe me that these guys have the best in their hearts for the growth of the company but I seeing them struggle in order to find a common way in which to prioritize all the # 1 and # 2 items.

       

      My reason to ask for a tool recommendation was simple. I am sure that every company with limited dev resources struggles at some point in deciding which projects amongst the 100’s will have the most bang for the buck. How to finalize on that list is the key issue here. Tool is just to make the mundane part of the job easier.

       

      Being a developer my first thought was on how I can automate (or make it easier) the task of listing the projects, their business value and a rough estimation of time so that a logical priority can emerge.

       

      Thanks

      Nikhil

       

       

      From: scrumdevelopment@ yahoogroups. com [mailto:scrumdevelo pment@yahoogroup s.com] On Behalf Of Roy Morien
      Sent: Thursday, January 29, 2009 9:50 PM
      To: scrumdevelopment@ yahoogroups. com
      Subject: RE: [scrumdevelopment] Any recommendations on tools for Product Owner?

       

      Don't these executives have any idea about a decision making process, where at first all ideas are put forward, each one is then explained to all interested parties, and then a decision is made and one outcome is converged upon.
       
      Are these executives so egotistical that they can't give up their favourite tool suggestion, and see the benefits of any other suggestion.
       
      Anyway, what do they actually want in such a tool? Perhaps you can ask them to list the characteristics of such a tool that they see as necessary. Then you can pick the tool that best meets their requirements.
       
      HAven't these executives got anything better to do than squabble about this. Why don't they leave it up to you to decide?
       
      Regards,
      Roy Morien

      > To: scrumdevelopment@ yahoogroups. com
      > From: basv@...
      > Date: Fri, 30 Jan 2009 13:43:53 +0800
      > Subject: Re: [scrumdevelopment] Any recommendations on tools for Product Owner?
      >
      >
      > Hi,
      >
      > How can a tool be a roadblock (especially since you didn't selected it
      > yet!)
      >
      > Bas
      >
      > On Jan 30, 2009, at 12:22 PM, Nikhil Singhal wrote:
      >
      > >
      > > Now that our management is taking the SCRUM concept a little bit
      > > more seriously, the biggest roadblock (as I see it) is a good tool
      > > on which the executive mgmt can agree for maintaining the product
      > > backlog. Some seem to like excel, some like activeCollab and some
      > > word.
      > >
      > >
      > >
      > > Is there a tool which most SCRUM product owners use? On a side note,
      > > we do have Microsoft TFS for sourc e control, reporting, etc.
      > >
      > >
      > >
      > > Thanks for the advice.
      > >
      > > Nikhil
      > >
      > >
      > >
      > >
      > >
      >
      >
      > ------------ --------- --------- ------
      >
      > To Post a message, send it to: scrumdevelopment@ eGroups.com
      > To Unsubscribe, send a blank message to: scrumdevelopment- unsubscribe@ eGroups.comYahoo ! Groups Links
      >
      > <*> To visit your group on the web, go to:
      > http://groups. yahoo.com/ group/scrumdevel opment/
      >
      > <*> Your email settings:
      > Individual Email | Traditional
      >
      > <*> To change settings online go to:
      > http://groups. yahoo.com/ group/scrumdevel opment/join
      > (Yahoo! ID required)
      >
      > <*> To change settings via email:
      > mailto:scrumdevelop ment-digest@ yahoogroup s .com
      > mailto:scrumdevelop ment-fullfeature d@yahoogroups. com
      >
      > <*> To unsubscribe from this group, send an email to:
      > scrumdevelopment- unsubscribe@ yahoogroups. com
      >
      > <*> Your use of Yahoo! Groups is subject to:
      > http://docs. yahoo.com/ info/terms/
      >



      Get what you want at ebay. Get rid of those unwanted christmas presents!




      Sell your car for just $40. It's simple!
    • Show all 25 messages in this topic