I'm currently in a situation where my organization wants to transition to using Scrum for software development and enhancements but we don't have a clear idea as to who will assume which role. Any feedback is appreciated. Thanks!
Should stories be kept in place of requirements to provide permanent system documentation or should a functionally organized set of requirements be maintained as this documentation. Either way, I am trying to figure out the best way to maintain a description/model of the system being maintained that is understandable to non technical and technical staff and provides a starting point for analyzing future changes to the system.
When product owner express the userstories, scrum team asks for clarification for better understanding.What is the order of actions in sprint planning, is it that tasks of particular user story should be entered in in scrum board or acceptance criteria of the user should be defined first and then entering the details of develeopment tasks with the estimates derived? can you help me with this?
In my research study, I need to identify the list of key features of user story management tools that can be used to support agile development. So far, I identified the following general groups of features: User role modeling and personas support, User stories and epics management, Acceptance testing support, High-level release planning, Low-level iteration planning, and Progress tracking. Each group contains some specific features, e.g., support for story points, writing of acceptance tests, etc.
Please help me elaborate the list by posting your list of such features, such as those that you've already used as part of a user story management tool, or those that you'd like to see in the software tool you use. Do you find some features more important than the others? Many thanks in advance!