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.
Recent Q&A Activity
By Salam ELIAS 1 Answer
I have a customer who is not mature in Agile. He is thinking of using agile methodology to migrate several open source collaborative software/platforms to a single identified platform.
His is thinking that migration team is ready to learn and carry out migration at the same time? Is tghis a good idea? Is there any case studies or tips on using agile methodologies for migration projects and which methodology?
Thanks in advance
What importance does you company put on the usability of its products? Do they focus on desinging and testing for usability?
If not, why not?
By Lisa Anderson 3 Answers
We're curious as to what other groups use Sprint 0 for. What tasks are you doing during sprint 0?
Thanks,
LisaAn
Below are some observations I've made and I'd like to solicit the communities feedback on the conclusion I've drawn from it.
When looking at industrializing software development by creating a fully integrated and automated pipeline through which changes flow from check-in, through integration, build, testing, packaging and deployment; there are 2 paths one can follow:
By Manuel Trinidad 3 Answers
I have been tasked by my company to come up with a single page document that shows the "value" that QA provided to the project. Basically we need to show how we have saved and/or made the company money through any given project.
I have things like number of hours tested, if we went over budget, number of defects found, etc., but what are your suggestions?
How do I show the value of the defects found and come up with a comparison to what it would cost to fix these things in the field?
By Kent J. McDonald 3 Answers
I'm looking to hear about people's experience with different ways of creating a backlog that is more than just a list of stories and does not cause the team to lose the forest in the trees.
By Justin Gamble 2 Answers
I'm interested to know of other projects where this situation has come up. Would you recommend this? Or should each team have only one QC tester?
I have used 5 Whys, 5 S, Kanban, JIT, Value Stream Mapping
Pages
AgileConnection is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.