Post

1 follower Follow
0
Avatar

Team Board - User Story Access

I'm struggling with the usage of the Team Board application regarding who has access to view user stories tasks.  The way we have it set up know, there are two leads (one Dev / one QA) that have Project access and can hence see the user stories.  All the team members (the individual coders, testers, etc.) can only see the specific tasks they are assigned.  This arrangement causes two problems - it's difficult for the individual members to see who else is working on their user story (e.g. the developer can't see which QA is assigned to test his code) and there is no common place to have a discussion about requirement (under the user story makes sense but everyone needs access).

For an Agile organization, does Clarizen recommend that ALL team members have Project access so everyone can see the user stories, etc.?  Or are there other alternatives I'm missing?  I'm curious as to what the Clarizen development team themselves are doing?

Thanks,

-Mike

 

 

Michael Ebeling Answered

Please sign in to leave a comment.

1 comment

0
Avatar

Hi Mike,

You are correct that Team Members only have access to their own assigned tasks. If you want them to see other members working on their user stories, you would have to convert them to Full license or permission. 

Tom Do 0 votes
Comment actions Permalink