Recent Q&A Activity

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?


I have a PMP, but would like to get certified Scrum Master also. What is the best and most economical way to get the training and pass the exam to get CSM certification? Would Rally or Version One offers the training and voucher to take the exam to get CSM certification? Thank you.

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.

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?

We were asked to estimate the effort for epics but declined to do so until it was broken out into stories. Is there any realistic way to accurately estimate the effort for an epic?

We are a small IT company developing a variety of IT products. I want to incorporate best practices into our product lifecycle management (PLM) process


I have used 5 Whys, 5 S, Kanban, JIT, Value Stream Mapping

This can be either adapted from a more "conventional" CM plan or written entirely from scratch. This question may be answered somewhere else in the Agile Forum and, if so, I would appreciate anyone sending me where such a plan may be found.

I would like to know about your experience with the co-location of Agile and SCM practices in your organization.



Can anyone shed some light on best practices of when / where/ how to establish the scope of the Release in the Agile Development Lifecycle model?

Our problem seems to be that we can never get to the point when we can nail down what the scope of the release is. When we do, it seems to be last minute and I am sure that this is not the best method for testing.

I recently assisted a presentation of Rational Team Concert, and I am shocked.

It could have been, I am sure, some other product. I don't intend to bash RTC.


AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.