Hi Ryan,
first of all let me say that I feel that you try to solve a social
problem using technology and this is extremly hard - usually this will fail.
IMHO your best option would be to apply scrum + use Agilo's traceability
features:
- Do a real sprint planning meeting where you fill the sprint backlog.
Make it clear to your PO (and your company) that the *development
team* decides what goes into the sprint backlog!
This 'pull principle' is essential for Scrum!
- If a user story does not contain all necessary information, the team
will not commit to it.
- In Agilo you can see very easily if someone added a user story later
to the sprint backlog. Reject these and remove the sprint.
That being said there is a possibility to restrict existing permissions
even more (though not to the level of detail you described) by writing a
custom trac policy (coding required) and build the rules you like.
fs
--
Follow Agilo on Twitter: http://twitter.com/agiloforscrum
-----
You received this message because you are subscribed to the Google
Groups "Agilo for Scrum" group. This group is moderated by agile42 GmbH
http://www.agile42.com and is focused in supporting Agilo for Scrum users.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/agilo?hl=en
