Loading Profile...
Integrate scrum'd with a source control repo
Add the ability to integrate with a source-code repository. SVN/git whatever. It will allow me to have a full cycle between requirements and development. One interesting option is presented by Unfuddle. They have HTTP callbacks on commits. If scrum'd had an API it would be possible to call it with the callback and have scrum's match the commit to the story based on some marker.
I’m hopeful
4
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The company has this under consideration.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?I like this idea as well, and we've been talking about it internally. We're thinking that we can implement it as an optional feature, so that users can turn it on/off. We'll send this out in the next community newsletter. Thanks Guy.
I’m liking it
-
Inappropriate?I know this is 8 months old, but this lets me avoid work so I'll bite:
Previously I worked in an environment where I was responsible for a very large scale adoption of Basecamp by a largely non-technically savvy user base. The added complexity of integration with a version control system would have put the application well beyond their grasp. Just seeing information that they couldn't comprehend would frustrate these particular users to no end. (Admittedly this might be specific to the culture of their company, not universal.) It would have also strengthened their argument that it was "just a tool for the developers" and that they didn't need to learn how to use it.
If the integration can be easily toggled or hidden from certain users, that would be fine, I suppose. On some level though, I think you have to decide whether or not your target market for Scrum'd is developers managing development projects or people managing projects and allocate your development resources accordingly. Perhaps you've already made that decision. In case you haven't: I'd argue that scrum is extremely applicable outside of development projects (which you'd probably agree with) and that Scrum'd should be as well. With that in mind, focusing on an API that would allow Guy to do what he needs rather than munging up the interface to make it happen easily for everyone would probably be the better approach.
Meh. Back to work, I suppose.
I’m unsure
-
Inappropriate?Hi Thomas,
We have worked to make scrum'd a tool that both developers and non-development folks can easily use. As long as they are doing scrum, they can use scrum'd. Having said that, we ourselves our developers, and we use version control, and having that integration, and being able to toggle it on/off is something we see as a great idea. Right now we're looking into integrating with Github. Are there others that you had in mind, or hooking it into in-house repos somehow? Also, would the commits be connected to stories or tasks? Which would work better for you?
Thanks for the feedback.
I’m excited
EMPLOYEE
