(Professional Business Analyst Training organisation)
It's, Quality Function
Deployment !
 Quality Function Deployment (QFD):-
In starting with this “QFD” terminology I
start thinking that its not meant for people
like me(yes! I belong to Normal crowd).
But it is !!. As I am obsessed about quality
of product I use, I decide to go further....
 So first starts firsts, “Quality”.
 It is alluring word for any customer.
 It could be anything services provided by
your maid or hotel manager or even a sweet
smile of receptionist of any reception desk.
 But, how to convert this smile in quantitative
aspect to create benchmark of satisfaction…?
 Here it goes a person with good IQ & good
personal, who is more keen to provide
consumer satisfaction (Dr. Yoji Akao) did all
hard work & came up with solution &
technique to find out the functions of quality
which are like HOQ (House Of Quality) “Pugh
concept Selection”, Modular function
deployment [To understand this HOQ & all
other technology, we need, another Blog topics
consider.]
Traditional BA (Waterfall) Agile BA
Requirements are documented in Use
Cases,Business Requirements, Functional
requirements, UI Specifications, Business Rules.
Requirements are documented in Epics, User
Stories and optionally Business (or Essential) Use
cases.
Focuses on completeness of requirement and
spends time in ensuring the requirement is
unambiguous and has all the details.
Focuses on understanding the problem and being
the domain expert so that s/he can answer
questions from the development team swiftly and
decisively.
Focuses on getting a ‘sign off’ on the requirements.
Focuses on ensuring the requirements meet the
currentbusiness needs, even if it requires
updating them.
Often there is a wall between the BA/Business and
the Development team.
Agile BA (Often called as Product Owner) is part of
the team.
Tends to dictate solutions.
Has to remain in the problem domain, leaving the
development team ‘space’ to explore different
solutions.
Long turnaround. Quick turnaround.
Focus on what the requirements document said. In
other words, output (Artifact) is a well written
thorough requirements document.
Focus on the functionality of the developed
software. In other words, output (Artifact) is the
software that meets thebusiness needs.
 So Basic QFD approach provide us to satisfy
customer through four stages:
 Product Planning - includes defining and
prioritizing the customer’s needs; analyzing
competitive opportunities, planning a product
that responds to the perceived needs and
opportunities and establishing critical
characteristics and target values.
 Assembly/Part Deployment - includes
identifying critical parts, components and
assemblies of the product, decomposition of
critical product characteristics, and translation of
critical components into class characteristics and
target values.
 Process Planning - includes determining
critical processes and process flows,
development of required techniques and
technology, and establishing process control
targets.
 Process/Quality Control - includes
determining individual part and process
characteristics, creating process control
methods to support measurement and
establishing standard inspection and testing
processes.
throughout this process we maintain Quality
Function Deployment Matrix, which defines
prioritization & ranking.
Now we can define it in My own term like
“ if I am satisfied , they are qualified”.
They are able to Transfer my Satisfaction
(Quality) to me in my own aspect.
Thanks...
CONCLUSION:
Gap Analysis helps organisations in getting
comprehensive outlook of an entire organization or
respective function or process within the organization
and to assess and reassure the current available
resources which are apt to meet the future
expectations, this result in the decreased project cost,
and strict timelines on the other hand
GAPanalysis is an esteemed and most acceptable approach
which need to be followed by organizations at all levels of
hierarchy to get help in allocation of resources efficiently,
crisp planning the budgets and effective prioritizing the
needs and requirements.
It's, quality function

It's, quality function

  • 1.
    (Professional Business AnalystTraining organisation) It's, Quality Function Deployment !
  • 2.
     Quality FunctionDeployment (QFD):- In starting with this “QFD” terminology I start thinking that its not meant for people like me(yes! I belong to Normal crowd). But it is !!. As I am obsessed about quality of product I use, I decide to go further....
  • 4.
     So firststarts firsts, “Quality”.  It is alluring word for any customer.  It could be anything services provided by your maid or hotel manager or even a sweet smile of receptionist of any reception desk.  But, how to convert this smile in quantitative aspect to create benchmark of satisfaction…?
  • 5.
     Here itgoes a person with good IQ & good personal, who is more keen to provide consumer satisfaction (Dr. Yoji Akao) did all hard work & came up with solution & technique to find out the functions of quality which are like HOQ (House Of Quality) “Pugh concept Selection”, Modular function deployment [To understand this HOQ & all other technology, we need, another Blog topics consider.]
  • 6.
    Traditional BA (Waterfall)Agile BA Requirements are documented in Use Cases,Business Requirements, Functional requirements, UI Specifications, Business Rules. Requirements are documented in Epics, User Stories and optionally Business (or Essential) Use cases. Focuses on completeness of requirement and spends time in ensuring the requirement is unambiguous and has all the details. Focuses on understanding the problem and being the domain expert so that s/he can answer questions from the development team swiftly and decisively. Focuses on getting a ‘sign off’ on the requirements. Focuses on ensuring the requirements meet the currentbusiness needs, even if it requires updating them. Often there is a wall between the BA/Business and the Development team. Agile BA (Often called as Product Owner) is part of the team. Tends to dictate solutions. Has to remain in the problem domain, leaving the development team ‘space’ to explore different solutions. Long turnaround. Quick turnaround. Focus on what the requirements document said. In other words, output (Artifact) is a well written thorough requirements document. Focus on the functionality of the developed software. In other words, output (Artifact) is the software that meets thebusiness needs.  So Basic QFD approach provide us to satisfy customer through four stages:  Product Planning - includes defining and prioritizing the customer’s needs; analyzing competitive opportunities, planning a product that responds to the perceived needs and opportunities and establishing critical characteristics and target values.
  • 7.
     Assembly/Part Deployment- includes identifying critical parts, components and assemblies of the product, decomposition of critical product characteristics, and translation of critical components into class characteristics and target values.  Process Planning - includes determining critical processes and process flows, development of required techniques and technology, and establishing process control targets.
  • 8.
     Process/Quality Control- includes determining individual part and process characteristics, creating process control methods to support measurement and establishing standard inspection and testing processes. throughout this process we maintain Quality Function Deployment Matrix, which defines prioritization & ranking.
  • 9.
    Now we candefine it in My own term like “ if I am satisfied , they are qualified”. They are able to Transfer my Satisfaction (Quality) to me in my own aspect. Thanks...
  • 10.
    CONCLUSION: Gap Analysis helpsorganisations in getting comprehensive outlook of an entire organization or respective function or process within the organization and to assess and reassure the current available resources which are apt to meet the future expectations, this result in the decreased project cost, and strict timelines on the other hand
  • 11.
    GAPanalysis is anesteemed and most acceptable approach which need to be followed by organizations at all levels of hierarchy to get help in allocation of resources efficiently, crisp planning the budgets and effective prioritizing the needs and requirements.