Question { 12316 }

How does agile communication differ from tradition software
engineering communication? How it is similar?

Answer

Agile communication is quicker than traditional software
development communication in the following ways:
First, the project teams are "co-located" so that any
questions are immediately answered instead of using phones,
email, etc to ask coworkers for ideas, thoughts or answers.
Every day an Agile team meets for a quick 15 minute meeting
(sometimes called a daily scrum) to refine what tasks were
completed the previous day, what will be done by the team
today and what impediments are prohibiting the team from
getting the work done.
Agile teams are constantly refining scope based on empirical
data from previous releases, test results and discoveries
where traditional projects design and code up to the
delivery date only to discover problems when it's very
expensive to correct.

Question { TCS, 6919 }

DIfference between ISO and CMM level

Answer

The difference is that the CMM is a way to communicate
capabilities, and ISO is a way to communicate the process.
They are not necessarily incompatible.

The Capability Maturity Model is a very specific way of
classifying an organization's software development methods.
In a certain way, it tells how the quality of its software
designs is likely to be repeated.

ISO-9000 procedures describe a (possibly) definite
development process but gives no indication of the likely
quality of the designs or whether multiple software efforts
are likely to produce software of similar quality.

Question { Cordys, 12112 }

What is QMS?

Answer

A quality management system in accordance with ISO 9001:2000
will provide your organization with a set of processes that
ensure a common sense approach to the management of your
organization.

The system should ensure consistency and improvement of
working practices, which in turn should provide products and
services that meet customer's requirements. ISO 9000 is the
most commonly used international standard that provides a
framework for an effective quality management system.

Question { 3532 }

What are the various role and responsibilities of
organization SQA?

Answer

There are some interesting challenges for SQA role &
activities in my organization.
This is with reference to Software Industry.

Basically there is at a gross level lack of compliance to
Quality Management system (This is more to do with a mindset
issue & ego, high esteem perspective, ‘I can delivery
without QMS’)

Even the people in escalation path just listen, but do not
take much action.

SQA is supposed to co-ordinate reviews (tech and management)
However the fact is that practitioners preciously know when
a review is required as they have higher and bigger stake in
the project and they do it exactly when required
irrespective of what SQA says.
SQA is then merely a coordinator.

If SQA recommends a practice, no one follows (even though it
is understood that SQA is a customer advocate), when the
same thing is asked by customer, without fail everyone follows!

I find something wrong with the way SQA
Roles/Responsibilities are defined & implemented in the
organization I work with.

In one of the CMM Books I came across a Disadvantage of SQA
concept that was indicative of organizations would not want
to assign their best technical talent into such roles.