Quality Assurance and Project Management:

customer requirement

1

June 1, 2012  4:55 PM

5 Top Reasons Behind All Problems In Project Management Part I



Posted by: Jaideep Khanduja
customer requirement, project management, team management, team sizing

Though it is difficult the assume in advance what kind of problems will percolate during a particular project but more or less all kind of problems faced during a project execution/ deployment/ management can be segregated in five top most reasons or categories. These generic segments/ reasons/...

July 26, 2011  6:07 PM

Sixteen Blogs On Identificaiton Of Customer Requirements



Posted by: Jaideep Khanduja
customer requirement, project management, Software Project

Customer Requirements need to be wisely analyzed before committing its fulfilment to customer. Many a times a commitment which has not been properly analyzed and assessed...


July 24, 2011  2:18 PM

Six Sins At Product Development Stage That Can Lead Project To Disaster



Posted by: Jaideep Khanduja
customer requirement, development plan, development team, project management, Project Plan, QA, QC, quality assurance, quality control, software development, Software Project, team management

Requirement Coverage: Requirement gathering and its documentation both need to be crisply and completely covered. Any lack in either of the activity is like a volcano in the making. In fact 88 percent of project failures worldwide are due to wrong or incomplete requirement...


May 17, 2011  9:59 AM

Five Requirement Based Face Saving Statements Against Customer To Hide Shortcomings



Posted by: Jaideep Khanduja
customer requirement, project management, Software Project

A fight between customer and vendor related to requirement keeps going on till the project finish stages starting right from the requirement study phase. Whatsoever methodology or standards you adopt to capture customer requirements, there will always remain a gap between what...


April 29, 2011  9:54 AM

Segregating Customer Desire Need And Greed Carves Project Success



Posted by: Jaideep Khanduja
customer requirement, project management, project manager, Software Project

Customer will always be hesitant in declaring software project as complete by means of talking about more and more to be done in the software. This ‘more’ could be anything like functionality, requirements, confusion, frustration, appearance, performance and what not. Some of...


February 8, 2011  12:06 PM

Five Golden Guidelines While Heading For A New Customer Win



Posted by: Jaideep Khanduja
business model, customer requirement, project management, Software application, Software Project, software quality

In today’s scenario there is no life on this earth without its dependency on any software in one way or the other in professional or personal front. This is what technology and its advancement does, it makes us more dependent on it by providing us more accuracy, comfort and...


November 16, 2010  12:17 PM

Identification of Customer Requirements Part X



Posted by: Jaideep Khanduja
customer requirement

It is important to analyze any change request raised by any of the stakeholders of the product in a systematic manner. The best way would be to first differentiate business process or functional change with cosmetic or design change. Though both categories can fall into severely...


November 16, 2010  11:58 AM

Identification of Customer Requirements Part IX



Posted by: Jaideep Khanduja
change management, customer requirement

In situations when the requirement generator cannot be ignored directly due to his potential say in the management, the role of Product Owner become prime in tackling the situation. Product owner must analyze the situation, prepare a case study and put forth his point that if such...


November 15, 2010  8:53 AM

Identification Of Customer Requirements Part VIII



Posted by: Jaideep Khanduja
customer requirement

Customer requirements management with a metrics is an important factor. Requirements raised a various levels within an organization has nothing to do directly with the seriousness of requirement. Some key users or management executives though may not go into...


November 15, 2010  8:48 AM

Identification Of Customer Requirements Part VII



Posted by: Jaideep Khanduja
customer requirement

A proper understanding of any change required and its in-depth analysis are prime important factors. It doesn’t mean that the importance of other steps performed afterwards – like the development of change, testing of all kinds, etc. The later steps are equally important but...


November 9, 2010  11:57 AM

Identification Of Customer Requirements Part VI



Posted by: Jaideep Khanduja
customer requirement

A new requirement development done in already consistently stable running software may do certain good or harmful things in turn. It may turmoil; destabilize the software thereby resulting into an inconsistent and unstable product. Which in turn may result into unsatisfied users...


October 29, 2010  9:19 AM

Identification Of Customer Requirements Part IV



Posted by: Jaideep Khanduja
customer requirement

The limitations of catering to new requirements may arise due to certain other factors too which might delimited at a later stage or may not be possible at all. For example an application built on client server architecture if required to be converted to a web based application later may call for a...


October 29, 2010  9:16 AM

Identification Of Customer Requirements Part III



Posted by: Jaideep Khanduja
customer requirement

Sometimes it might happen that the requirement by the customer exists in the product but in some other way. For instance the software product in use might be handling the same requirement already but in a different manner. In that case a person with good business knowledge knowing equally well...


October 27, 2010  11:17 AM

Identification Of Customer Requirements Part II



Posted by: Jaideep Khanduja
customer requirement

Interestingly if the changes are accepted without proper analysis it results in delays in delivery, improperly woven product, un-tested product, shaken budgets. This all happens due to a later stage discovery of the change appearing not as small as anticipated earlier. So many ambiguities arise...


October 27, 2010  11:09 AM

Identification Of Customer Requirements Part I



Posted by: Jaideep Khanduja
customer requirement

Customer requirements at first instance may all appear essential. Especially the requirements listed by the top management tend to automatically fall in must-do category. But that is not so. Any requirement if without proper analysis is placed in must-do or essential requirement may create a big...


September 7, 2010  6:37 AM

A Wake Up Call For All Project Managers



Posted by: Jaideep Khanduja
customer requirement, product development, product management, project management, project manager, Software Project

Imagine yourself as a commercial builder. You are contracted for building a multi-storeyed building by the owner of that plot. The owner is too busy to concentrate on the job himself. He finds you as an expert in this line. The conceptualized model has been described to you by the...


July 23, 2010  12:25 PM

Two Approaches Of Capturing Customer Requirements



Posted by: Jaideep Khanduja
business requirement, customer requirement, project management, software product, Software Project

Let us consider a simple scenario of writing code for a new application for a customer. The process starts with a clear understanding of customer business, key user’s expectations and customer management’s expectation regarding business benefits driven out of this application....


April 30, 2010  7:09 AM

Two Questions for Quality Manager and Project Manager



Posted by: Jaideep Khanduja
customer requirement, Project Head, project management, project manager, project quality, QA, requirement analysis, software development, Software Project

1. At times development, requirement freezing gets done side by side and that too at customer location. In that case the product undergoes a lot of changes based on customer feedback on daily basis and finally product gets ready as per development team and customer. After that...


January 6, 2010  10:00 AM

Development-QC-Development-QC-Dev-Product Launch



Posted by: Jaideep Khanduja
blackbox testing, boundary value testing, Bug, business specification, BVA, customer requirement, customer specification, development team, implementation team, performance testing, project management, QC, QC feedback, quality control, Regression Testing, software development, Software Project, tester, testing

In software development life cycle when the product is completed by development team, it is handed over to testing team for thorough or


November 11, 2009  10:00 AM

Project Manager – A Solid Bridge between Customer and Product Manager



Posted by: Jaideep Khanduja
change management, customer requirement, product manager, project management, project manager, Software Project

Let us talk about existing software required to be implemented at a new geographical location. Definitely because of a different location there will be certain new requirements plus some changes here and there in the existing built to meet customer specifications. This need to be handled very...


October 26, 2009  10:00 AM

Five ‘must-have’ skills to be a Business Analyst



Posted by: Jaideep Khanduja
business analysis, business analyst, business knowledge, business process, business rule, customer requirement, Development, process, project management, quality, software, Software Project, software requirement, technical knowledge

As stated in my previous post, a Business Analyst is a quite powerful role that establishes the base of a project. It is the first visible pillar for a project which involves communication, leadership, writing, technical and functional skills together. A business analyst has to have a great depth...


October 23, 2009  10:00 AM

Various roles of a Business Analyst



Posted by: Jaideep Khanduja
business analysis, business process, business rule, customer requirement, Development, process, project management, quality, software, Software Project, software requirement

Business Analyst is a quite powerful role forming the base of a project. It is the first visible pillar for a project which involves communication, leadership, writing, technical and functional skills together. A business analyst has to have a great depth of knowledge of the business on one hand, a...


October 12, 2009  10:00 AM

What customer type you are?



Posted by: Jaideep Khanduja
business requirement, change management, code, customer requirement, software, software implementation, software product, Software Project

One customer type focuses on current requirement, rightly built, with more flexibility towards the business requirements built-in in the database rather than in the code. They believe that if the software meets their current requirements well, the future requirements will be built in at the need of...


October 9, 2009  1:17 PM

What sort of driver are you?



Posted by: Jaideep Khanduja
customer requirement, product quality, Project Development, project implementation, project management, project manager, project stage, quality, software delivery, Software Project, software quality

I have seen different type of drivers on road: some drive very fast violating all rules and regulations to reach the destination. Can this attitude work in software development and delivery? I don’t think so, if the project manager is more worried about reaching the implementation stage without...


September 16, 2009  12:00 PM

Five ways to workout ‘testing effort”



Posted by: Jaideep Khanduja
business rule, business specification, customer requirement, customer specification, development phase, development plan, functional testing, load testing, performance testing, QC, QC head, quality control, software development, software product, Software Project, team size, test case, test effort, Test Plan, tester, testing effort, testing effort estimation, testing phase, testing plan

A new project, a new product development – as a QC head how do you estimate your testing effort? Well, some quick steps for this: 1. Customer requirements: Customer specifications or requirements captured at the time of initial study period would be a quick reference guide for estimating...


September 14, 2009  1:00 PM

Ten facts (or myths) about developers and testers



Posted by: Jaideep Khanduja
Bug, business needs, business requirement, code, coding, customer requirement, developer, software, software code, Software tester, software testing

We all know developers and testers both have a tough job all the time. Developers have a key role in developing the software as per customer requirements embedding customer’s business needs into it. Similarly testers have to put all their efforts in ensuring that the software is matching customer...


July 20, 2009  10:00 AM

Responsibility of a tester – a different perspective



Posted by: Jaideep Khanduja
bugs report, code writing, coding, customer requirement, developer, Development, development team, product quality, project management, QC, quality, quality control, software product, Software Project, software quality, test case, test report, tester, testing report

The responsibility of a tester is to ensure the peace of mind of the end users who are going to use the software product. Another target should be to safeguard customer's investment in the product. In order to discharge this responsibility, the tester should focus all his skills on understanding...


July 10, 2009  10:00 AM

If you don’t change with the ‘Change’ you get [ex][change]d



Posted by: Jaideep Khanduja
business requirement, change management, customer requirement, development phase, product delay, product launch, project management, project phase, project timelines, software, software build, software development, Software Project, software testing, test phase, testing

In my June 15 2009 post – “Do’s (+) and Don’ts (X) in Project Management”...


1

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to: