Scrum’d Updates and Getting Involved

by Robert Dempsey on March 18, 2009

We’re hammering bugs and updating UI like nobody’s business. Hot on the heals of our updates last night, here’s the latest as of this evening.

Fixes

  • ‘Change your subscription level’ link broken
  • Canceling an account throws a render error
  • The expand/collapse toggle on the product planning page causes rjs errors
  • Add more flash messages to the application
  • Only scrum team members can edit tasks
  • New sprint form shows deleted release in drop-down of releases
  • A scrum team member should not be able to sort stories in the product backlog
  • A scrum team member should not be able to move user stories from backlog into sprint
  • Scrum master should not be able to move tasks from one state to the next
  • Flash messages don’t show up on the product planning page when deleting objects
  • Support link is gone
  • Cannot delete users from an account
  • A user can drag a story under a release (support ticket)
  • Footer disappears if projects or users is clicked

Getting Involved

Yesterday I posted the roadmap for scrum’d, along with the fixes we were putting in place. The path I have chosen for scrum’d is partially an experiment on my part. I believe that by being open and transparent with what is good and bad about scrum’d, what we are doing to correct the bad, getting our users deeply involved with the product and helping us to determine it’s direction, we can be successful. To that end, here is how you as a customer, or a potential customer, can get involved.

First, use our support site. You can:

  • Ask a question
  • Share an idea
  • Report a problem
  • Give praise

As our product owners, you determine what gets developed when. So when you share an idea, the more people that like that idea, the higher up the list it goes. Problems work the opposite. When you create one of those, we’ll put it on the list and balance them out with new features. Here’s what we have so far thanks to Anthony Eden of Chi.mp (which is very cool by the way):

  • Once I create a Release I should be provided with direction on what to do next (link)
  • If I don’t have any sprints yet, don’t show me the empty drop down. (link)
  • Overuse of AJAX breaks back button. (link)

If you think these are great ideas too, click the “I like this idea!” button. If you are experiencing the same problem as someone else, click the “I have this problem, too!” button.

So, get involved and help us make scrum’d work better for you. We look forward to hearing from you.

Bookmark and Share

Other Posts That Might Interest You

  1. Scrum’d Updates for March 20th
  2. Scrum’d Updates and Roadmap
  3. Expens’d Updates and the Current Roadmap
  • Hi Nick - I am highly confident that we can make this model work.
  • This is a really cool idea, and an interesting way to approach a product. My fear with running my applications this way has always been that it would turn into a cluster-you-know-what of compromise, making everyone happy, watering down the product, etc. The other view I've always held is that most of the time users don't know what they want until they actually use it. A lot of the time an idea will sound terrible, until you actually experience it yourself (it's hard for me to get some non-techies to use Twitter, for example, even though I know they'd love it).

    What you're doing is different though...

    As a Scrum Master, you're someone that knows how to prioritize better than most. Additionally, a high level of transparency will allow you to develop a solid relationship with your users, so that when they're asking for something that doesn't really make sense, you can discuss is with them and explain why you think it's a bad idea.

    Awesome job with this so far. I'm really interested to see how this goes!
blog comments powered by Disqus

Previous post:

Next post: