Centercode experience from a CSM perspective
Use Cases and Deployment Scope
Pros
- The Project Management style of logging tasks allows us to be nitty gritty with our beta testing
- The ability to be able to cross check what other or similar items in the group captured adds value by visibly other issue similarity other testers captured
- The ability to manage view access on a SSO config allows easy access only to those that are part of the actual beta testers on a "need to know" basis
Cons
- The first thing I noticed that was raised was that when we were all logged in and adding stuff, the performance was somewhat degraded (slow)
- I think it would've been easier to have drop-downs created/added per category/area of what's being tested. This adds up to productivity instead of just free text typing
- I definitely had an issue using this with Safari as it wouldn't load some of the items eventhough I had mine updated to the latest version. It'd be great if it worked well regardless of the browser used
Most Important Features
- Bug listing by keyword allows one to move on quickly to test other items allowing the project to progress rapidly
- The "need to only" access basis allows us the right people to have visibility on the entire project
- The part where it's synced with SSO and the SAML attributes select only the right people enabled was both convenient and secured
Return on Investment
- A project and beta testing that could've taken > 6 months or even years was cut down to a month and few weeks only
- Overall accessibility, ease of use, and security were right on the money
- Collaboration tools and features allowing everyone to innovate and spark great ideas and share it







