BugTracker.net vs. Powernoodle

See above. Recommended questions: What type of feedback or tracking will we be doing? Will this need to be client-facing? How will we track content edits? How many users will be assigned to issues in a given project?

Incentivized

Well Suited:

• Groups needing to make a decision
• Democratically based decision making
• Sensitive topics
• Discussions Groups needing input

• Ability to split our multiple projects and assign a user base.
• Ability to set permissions based on user base/ roles.
• Customization of fields on a project level.

Incentivized

• Powernoodle has ignited deeper, more candid conversations among our team leaders. We've been able to see through these discussions that we haven't always told our story in the most compelling manner, and that we need to be clearer, more concise and less wordy. Since Powernoodle limits your contributions to a certain number of characters, it forces you to think hard about what you really want to say. This feature was particularly powerful for our organization, which has tended to verbosity.
• Powernoodle allowed us to vet old and new ideas in a safe space, minimizing biases and groupthink. In many organizations there are some who speak more than others, and often their ideas get more attention. What Powernoodle does brilliantly is it allows, actually requires, each participant to write what they wish anonymously and without interruption. Each participant is equal in the sense that all input into Powernoodle is brief (limited number of characters) and the anonymity definitely prevents the usual bias toward those who speak the most.
• Powernoodle increased critical thinking about our organization and forced us to re-examine why and how we do what we do. With Powernoodle, we were able to look at everyone's ideas, comment on them, decide if some should be merged, and ultimately vote on them. The Powernoodle process forced us to be clear, which meant we each needed to think critically about what has worked and what hasn't worked for us, and how we move forward with what has worked and with new ideas.

• User interface for client-facing feedback
• Content and design updates tracking

Incentivized

• It's not mobile friendly yet, but other than that no complaints!

I would plan on renewing and staying with BugTracker.net simply because it is a no nonsense easy to use tool. Once you get it set up and understand the small nuances with this custom piece of software, it really is a great tool to help your organization get started with Defect Management and BugTracking without having to drop several thousands of dollars on tools that are more fluff than function.

Incentivized

I didn't choose the product or evaluate other options, but I've been satisified with it except for tracking content changes.

Incentivized

• Decreased turn around time for defect fixes.
• Smoother builder deploys
• Clearer communication from QA to Dev Team

Incentivized

• While we are still in the beginning stages of taking action on the decisions we made using the Powernoodle process, I have no doubt that there will be a very positive ROI on our overall objectives.