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

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

Expand Messages
  • Vikrama Dhiman
    Jan 29, 2009
    • 0 Attachment
      It would depend on the product you are building and your corporate environment.

      Here is what I use:

      1. Clear reporting of business metrics through a custom built web based software for Analysis - MOST IMPORTANT
      2. Corporate Email from Google, as this keeps me mobile [their search works like a dream] - and I read each and every email that comes on support
      3. MS-office [Word/ Excel/ PowerPoint]/ Google Docs
      4. Whiteboards for quick discussions and pasting stories for next sprint/ sprint discussion
      5. Google Alerts to keep track of industry trends and coverage
      6. RSS feeds to keep updated from thought leaders in technology and domain
      7. VSS to make textual changes in web application myself
      8. MS-SQL Server querying for ad-hoc analysis
      9. I use Survey Monkey for some surveys sometimes
      10. I am trying to learn Fitnesse too
      11. You also need a tool to give you infinite patience to explain business context again and again :)

      Hope that helps!


      Participate in "Are we Really Agile Survey" - It only takes a minute.
      Vikrama Dhiman
      [Product Manager]
      Please visit my blog at:

      --- On Fri, 1/30/09, Roy Morien <roymorien@...> wrote:
      From: Roy Morien <roymorien@...>
      Subject: RE: [scrumdevelopment] Any recommendations on tools for Product Owner?
      To: scrumdevelopment@yahoogroups.com
      Date: Friday, January 30, 2009, 10:25 AM

      Yeah, that too!

      > To: scrumdevelopment@ yahoogroups. com
      > From: dmalloc@gmail. com
      > Date: Thu, 29 Jan 2009 23:54:08 -0500
      > Subject: Re: [scrumdevelopment] Any recommendations on tools for Product Owner?
      > 2009/1/29 Roy Morien <roymorien@hotmail. com>:
      > > Simplicity is a virtue. What is the Product Backlog? It is a list of User
      > > Stories (or other statements of requirements, however called) with an
      > > indication of complexity / difficulty / potential time consumption, stated
      > > as Story Points (or ideal days, or some other measure of estimated effort,
      > > however of called), and a level of priority.
      > >  
      > > So what is wrong with a simple spreadsheet? Each Product Backlog item can
      > > have a hyperlink to a Word document in which more detail is stated, if that
      > > is considered reasonable.
      > >  
      > or just use 3x5 cards and a shoe box and yes that still exists and I use it quite successfully :)
      > --
      > Sent from gmail so do not trust this communication.
      > Do not send me sensitive information here, ask for my none-gmail accounts.
      > "Therefore the considerations of the intelligent always include both benefit and harm." - Sun Tzu

      Let ninemsn property help! Need a new place to rent, share or buy?

    • Show all 25 messages in this topic