In all seriousness, buy/read a couple books: Agile Estimating and Planning - Mike Cohn Planning Extreme Programming - Beck & Fowler And still quite seriously,...
Mike Cohn's other book User Stories Applied (Addison Wesley, 2004) is practical and helpful on the requirements side of this. Reviews of this and many other...
The Case of the Missing Fingerprint <http://www.stickyminds.com/BetterSoftware/magazine.asp?fn=cifea> February 2007- Better Software Magazine Feature Article ...
Hi All, According to CMMI model, Requirements Engineering is covered in 2 process area. REQM (Requirements Management) and RD (Requirements Development)...
Kasim Level-2 is all about managing sw projects and changes on it, REQM focus on tracing requirements in order to understand how changes on them impact ...
Hi Kasim, CMMI is a project management process; not likely developed by Business Analysts. - This addresses an issue I've been thinking about for a while....
Kasim, If you regard CMMI as an appraisal model, usually in the Staged representation (maturity levels), then one would expect to see Maturity Level 2 PA's in...
Dear All, I'm currently defining a RD process and i'm facing problem distiguishing between the operational concepts and scenarios. My company uses a RUP...
Here is where I have to step in. Kasim, you as a project manager, I can see your point of managing the requirements, but as a Quality Engineer I have to say...
214
linda.ibrahim@...
Feb 7, 2007 5:51 pm
Hi, Our approach in developing the FAA integrated capability maturity model (iCMM) was NOT to have two separate process areas dealing with RE. We have a...
This is not likely to help - but we use event/data flow models for eliciting requirements and for defining the work of a project. Use case is put together...
I am little confused that how one can manage some thing which one does not possess yet. CMMI's Requirements Development PA should have been part of level 2 and...
Initial level we right requirements and try to manage it, we don't focus on quality of those requirements document. Then day by day we try to improve the...
Badar SEI in CMMI states on level 2 that no matter HOW you develop your requirements, first you must to control them in order to manage the impact of...
My understanding CMMI Level 2 applies to project level behaviour as opposed to organizational level. CMMI model suggests that, no matter how you develop your ...
Hey Small query for anyone who can help me out here. In CMMi, who is responsible of collecting data for measurement? I'll appreciate if anyone can provide me ...
Furqan, You must build a Measurement plan that defines, among many things, who is responsible for collecting the measures. This activity can be automated by ...
Furquan The CMMI model does not state exactly who is reponsible for collecting measurement data since this depends upon the organisation. The generic practices...
CMMI requires it be done, not that it be done by a specific person, organization, or tool. Organization structure, policies, procedures, and project plans are ...
Hi Furqan, CMMI is just a model for software development activities. Measurement is main point for management and therefore CMMI has a M&A process and GP 2.6...
Thanks Kasim for your reply The only issue in my case is that our QA department persists that measurement will be done by each PA owner. Since i am a...
228
David Longstreet
Knowledge@...
Feb 14, 2007 2:18 pm
The point of measurement is to help you control and manage your environment. The responsibility for measurement should be the process owner, but that does...
We are working on this hybrid solution in which we are integrating a IBM product. There's few development activity's as well but most of the activities are...
Hey all Here we have measurement specialists ( I´m one of them ) responsible for defining measure specifications. These specs include who's responsible for ...
Furqan: To achieve software integration, you need to first come up with a comprehensive, integrated understanding of the essential functionality and -...
Furqan, Tony, Use Cases were invented precisely to provide a convenient unit of description for add-ons to existing large (telephone) systems. The problem is...
