Quality Assurance and Project Management:

software development


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, 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

December 23, 2009  10:00 AM

Productivity Metrics vs. Quality Metrics



Posted by: Jaideep Khanduja
quality, software development, software quality

Imagine a Pen manufacturing company having lot of orders from their customers to manufacture various types of pens. There can be two scenarios – either the delivery is production centric, or quality centric. Let us see what the difference in both...


December 22, 2009  10:00 AM

Eight Facts About Developers



Posted by: Jaideep Khanduja
developer, software development

A developer when joins a company carries some expectations to deliver and expectations to get. He has lot of things in mind what extra edge he is going to deliver to make him different from other along with being a warm contributor to the team. Also...


November 26, 2009  10:00 AM

Product Version should match with Feedback by Development Team



Posted by: Jaideep Khanduja
Bug, development team, functional testing, load testing, performance testing, product development, product release, QC, Regression Testing, software, software build, software development, software product, testing

Development Team has finished with a new version of the software product. The product is ready for testing before releasing it to production team provide QC approves it after testing that no severe bugs are there. Test environment is prepared for QC team to perform the complete...


November 23, 2009  10:00 AM

Project Management and the Risk Factor



Posted by: Jaideep Khanduja
Project Development, project implementation, Project Lifecycle, project management, project methodology, risk, Risk Management, software development, software management, software requirement, tester, testing

Any software development and implementation project comprises of risks. The visible risks are easy to handle or manage. Invisible risks are more vulnerable. Invisible risks are like volcanoes that can erupt without any warning and can...


November 20, 2009  10:00 AM

How your Web Application Performs on Various Browsers?



Posted by: Jaideep Khanduja
application performance, browser, developer, development team, legacy software, project management, software design, software development, Software Project, software requirement, tester, testing, web application, web browser

You are in software development and in today’s world you can’t escape from most of your customer demanding either replacing their legacy software in use with new web application or the development of a new web application. Every customer wants to keep maximum...


November 6, 2009  10:00 AM

Ten cautions in case of a self sponsored project



Posted by: Jaideep Khanduja
Development, project management, project methodology, Project Plan, project sponsor, Risk Management, risk mitigation, risk severity, software development, Software Project

What if you have chosen to develop a product for which you don’t have a customer right now? If you perceive that by the time you complete development phase and the product will be ready to launch if will not be obsolete as per technology or concept, go ahead but take care of following cautions to...


October 9, 2009  6:29 AM

Project Lifecycle – 2012



Posted by: Jaideep Khanduja
developer, implementation, Project Lifecycle, project phase, project team, software development, software product, Software Project, software testing, tester

Phase I: There is nothing called ‘off the shelf” product. It is all ‘made-to-fit’ technique. You specify your requirements and that too at a broader level. For micro level leave a red-mark at areas that need to be looked into at the time of building of software. The more red-marks will mean...


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, 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...


August 26, 2009  10:00 AM

Software Developers – Do you imagine, dream and innovate? Continuously?



Posted by: Jaideep Khanduja
Software developer, software development

If answer to the first question is No, start moving into the direction of converting it to Yes. Answer to second question also has to be yes. Let us see what is meant by Imagine, Dream and Innovate and how to adopt them at workplace. Imagination- The ability to create, and paint a mental picture...


August 24, 2009  10:00 AM

If SaaS is acceptable, why not give birth to QaaS?



Posted by: Jaideep Khanduja
developer, Development, software, Software developer, software development, tester, testing

A software division in an IT company is considered to be a profit center whereas the Testing division is considered as cost center. A set of developers develop software, get it tested by a set of testers, sell it in the market and earn profits. The credits and benefits on success of the software...


August 19, 2009  11:00 AM

Software developer or bug developer



Posted by: Jaideep Khanduja
Bug, product testing, Software developer, software development, software testing, tester, unit testing

If a person who develops software is software developer, why not the same person developing bugs in the software be called bugs developer. How many developers ethically perform the unit testing after completing development of a unit? It could be - None, a few of them, some of them, most of them or...


August 17, 2009  1:00 PM

Dear software developer – what is your mileage?



Posted by: Jaideep Khanduja
developer, documentation, planning, software development, software requirement, software testing

I have two sets of developers. Both bunches contain quite considerable number of developers. Let us call it first set of developers and second set of developers. Both sets have their own unique way of functioning and performing. First set of developers work randomly with no documentation, no...


August 7, 2009  10:00 AM

Ten Mantras for a software developer



Posted by: Jaideep Khanduja
application, application building, Application development, application functionality, application performance, Bug, bug fixing, bug identification, bug-free, business process, business requirements, Business Rules, code validation, code writing, collaboration, customer experience, end user, process owner, quality, software, Software application, software build, Software developer, software development, software functionality, software performance, software testing, tester

Lot of efforts can be saved in terms of time and money if we reach to a stage of ‘first time right’ in application development. It has been proven largely that no good application can be built and released without extensive testing. Testing is not developers’ ball game – this is also a well...


August 5, 2009  10:00 AM

User Acceptance Testing (UAT)



Posted by: Jaideep Khanduja
appearance testing, bug fixing, business process, business rule, customer specification, defect fixing, functional requirement, functional specification, functional testing, integration test, interfacing, product testing, software bug, software build, software defect, software development, software product, software testing, testing lifecycle, UAT, user acceptance test, validation testing

UAT or user acceptance testing comes as the last exercise in software testing lifecycle. It is probably the first phase or beginning of customer preparing to takeover the charge of the product. Actually this is a sort of test drive by a perspective buyer who has studied well about a car, has made...


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”...


June 29, 2009  10:00 AM

Outsource in a software project without losing control over it



Posted by: Jaideep Khanduja
documentation, handholding, outsourcing, post implementation, project component, project control, project execution, project implementation, project management, project offload, project outsource, project phase, Project Planning, requirement analysis, requirement freezing, requirement gathering, software design, software development, Software Project, software testing, training

We learnt in earlier two posts about the strategic decision of a management to outsource a complete project or part(s) of a project depending on certain factors, and the factors respectively. In this post let us see at the various components of a project that are most widely outsourced or otherwise...


June 12, 2009  10:00 AM

Ten symptoms to know if your project is infected with influenza A (H1N1)



Posted by: Jaideep Khanduja
project management, project manager, project performance, software development, Software Project, software quality

10. When you start getting increased number of bugs as compared to earlier releases 9. When your developers stop thinking about quality in code 8. When bugs pass through QC unnoticed 7. When you stop acknowledging quality efforts and start giving more importance to speed and volume of...


June 8, 2009  10:00 AM

Five pitfalls if you are leaving a scope of software development at customer site



Posted by: Jaideep Khanduja
functional lead, on-site development, project completion, project delay, project implementation, project management, project organization, project quality, project team, QC, quality, software development, software implementation, Software Project, software quality, technical lead, tester, testing

Ideally, in a software project, for an offshore customer, the requirement gathering phase should be given an extra care to understand to a maximum extent so that the product developed and tested when ready for implementation at customer site requires no development. Practically, it is very...


May 20, 2009  10:00 AM

Customer’s role in business study and requirement gathering phase of a software project



Posted by: Jaideep Khanduja
business study, customer, project agreement, project benefit, project director, project meeting, project review, project role, project sponsor, project stages, requirement gathering, software benefit, software development, Software Project, Software vendor, top management

Usually it is the customer top level person who is project sponsor for a software development project, be it in-house or from a software development vendor. A Project Sponsor may presume that his/her roles during the project would be – sign agreement and papers, assign roles down the line for the...


May 18, 2009  10:00 AM

Vendor’s role in involving customer top management while requirement gathering phase



Posted by: Jaideep Khanduja
business study, customer, customer expectations, end user, process owner, project completion, project management, project stakeholders, requirement gathering, software development, software product, Software Project, Software Project Lifecycle, Software vendor, top level requirement, top management, user level requirement

The most critical stage in software project lifecycle is business study and requirement gathering. Vendor has to be very cautious and careful in understanding all levels expectations from the product they are going to build for the customer. Skipping top level at this stage could be disastrous for...


May 11, 2009  10:12 AM

Two aspects in Change Management in Software Project



Posted by: Jaideep Khanduja
business critical change, business requirements, Business Rules, business study, change management, customer management, customer requirements, project cycle, Project Development, project implementation, project management, project manager, project team, software development, software implementation, Software Project, software requirements

Change management is a subset of project management. In any software project change is to be managed during the whole cycle of development and implementation. Requirements once specified by customer at the business requirements study phase does not mean that there will be no change in requirements...


April 13, 2009  10:01 AM

Project Manager’s vision has to be perfect 6/6 for project implementation



Posted by: Jaideep Khanduja
project implementation, Project Lifecycle, project management, project manager, software development, software implementation, Software Project, software testing

No project manager can claim there was not a single problem in any of his projects. But then he is to tackle them. To tackle them he should be aware of them. To be aware of them, he has to have an ability to foresee them than to overlook them. The earlier he envisages those problems, the more time...


April 10, 2009  9:59 AM

Application developed, tested and built well does not ensure successful implementation



Posted by: Jaideep Khanduja
Application development, application implementation, application readiness, post implementation, project director, project management, project manager, project sponsor, project vision, software development, software implementation, software project manager, software testing, stakeholder, successful implementation

It is not only the project manager but all stakeholders who get affected by the project over-run or failure. It could happen due to any reasons. One of the major reasons that have emerged is the lack of vision of the project manager, project sponsors, project directors and other stakeholders to...


April 8, 2009  10:18 AM

10 stages of Risk in software application development and testing



Posted by: Jaideep Khanduja
application testing, impact analysis, risk, Risk analysis, risk assessment, risk classification, risk closure, risk identification, risk perception, Risk Plan, risk plan analysis, risk plan execution, Software application, software development, software testing

A risk is a bigger than its size if it is not identified well in advance. An identified risk is as risky as unidentified if its assessment is not done. Risk assessment is useless if there is no impact analysis. Impact analysis has no worth if its countermeasure is not identified. Let us...


March 30, 2009  9:50 AM

A good programmer is not always useful



Posted by: Jaideep Khanduja
project manager, quality program, software development, Software programmer, software programming, Software Project, software skills

Once upon a time there was a programmer, a very good programmer. Good here means skilled, learned, experienced, and serious. He was appointed by an organization for a large project for a job to write quality programs. He was doing it well and was able to prove his point that he is good for the...


March 11, 2009  10:15 AM

6 mandates for Supplier Organization on Software Project Ownership



Posted by: Jaideep Khanduja
1. Software Supplier Organization, Project Initiation phase, Project Lifecycle, project manager, project monitoring, roles and responsibilities, software development, Software Project, Software Project Ownership

Ownership is a big issue in a software project. Customer organization assumes that since they are spending money, it is the sole responsibility of supplying organization to make the project a success. Vendor organization on the other hand assumes otherwise. Who is right? I think both are wrong at...


March 9, 2009  10:28 AM

20 points for organizational self evaluation to check where it stands in Software Project Management



Posted by: Jaideep Khanduja
1. organizational self evaluation, Code repository, continuous improvement, customer expectations, customer feedback, customer request, empowerment, innovation process, off-site project, on-site project, organizational goals, post implementation, process integration, product release, project implementation, project management evaluation checklist, Project Management Methodology, project manager, project metrics, project overrun, project team, Risk analysis, Risk Plan, roles and responsibilities, software bug, software development, software implementation, software project management, software testing, test case repository

  • 1. Does a formal Project Management Methodology exist in your organization? 2. Are you using some metrics to check if this is the right methodology? 3. What is the degree of improvement required in your current methodology to meet your customer expectations? 4. What are your...


  • March 6, 2009  9:42 AM

    Why software testing effort estimation is important after functional specifications finalization phase?



    Posted by: Jaideep Khanduja
    bug report, bug-proofing, bugs report, business process, business rule, developer, development team, functional coverage, functional specifications, functional specifications finalization, quality standards, sizing of software testing effort, software development, software testing, software testing effort estimation, test case, test estimation guidelines, Test Plan, test plan guidelines, test report, test result, testcase, tester, testing, testing effort, testing guidelines, testing knowledge, testing plan, testing time-line, testing timeline

    If we go by quality standards the sizing of software testing effort has to be done before the tester(s) start writing the test cases for the purpose. The estimate will clearly draw out of the functional specifications signed off between the customer and vendor. Without sizing the Testing manager...


    March 4, 2009  10:03 AM

    10 top “Do this if you want blunders!” in Software Development and Software Testing



    Posted by: Jaideep Khanduja
    business requirements, change management, Code library, Code repository, development plan, implementation plan, organizational goals, product development, project close-out, project documentation, project management, project methodologies, Project Plan, project standards, Quality Goals, requirements analysis, Risk Management, Risk Plan, software development, software development methodologies, software development standards, Software Project, software quality, Software Repository, software testing, SQA, SQC, test case, test case repository, Test Plan, test standards, time to test, top management requirements

    1. Quality Goals are meant only for Quality Department: No department other than quality (project management, product development, documentation, general management etc.) has to read, understand and learn about the quality goals of the organization. It is only the responsibility of...


    February 16, 2009  11:10 AM

    Dear Project Manager – Are your efforts in tune with your schedules (goals?)



    Posted by: Jaideep Khanduja
    project goals, project management, project manager, Project Plan, software, software development, Software Project, team management

    During one of my initial management trainings (years back) I learnt the different between hard worker and smart worker. This example I could never forget even after so many years. Example of a hard worker is a person who comes to office in the morning, puts off his shirt, start pushing a wall, and...


    February 6, 2009  10:00 AM

    Regression Testing “has to be” rigorous – for a “good” cause!



    Posted by: Jaideep Khanduja
    QC, Regression Testing, software development, software product, software testing, tester, testing

    Regression testing comes into picture in “re-testing” of a product. The purpose is very clear – a thorough testing. Regression testing has to be as rigorous as possible, for this reason. And regression testing never happens once, it has to happen again and again till the product reaches at a...


    February 4, 2009  9:54 AM

    Dear Project Manager – Do you know (during a Project) how important the “Project Status” is?



    Posted by: Jaideep Khanduja
    PM, Project Development, project manager, Project Plan, Project Status, software development, Software Project

    The most wrong statement from a Project Manager to the management during a project can be – “Everything is as per plan”. This is never, never possible during a project where a software development is required. If this is the statement from the Project Manager, there could be two realities...


    January 22, 2009  11:03 AM

    Is testing merely a Bug filtering process?



    Posted by: Jaideep Khanduja
    Bug, bug filtering, project lead, project management, QC, software, software development, software testing process, tester, testing, testing process

    In an organization engaged in software development, usually each software goes through testing process by a separate set of team in the organization know as Testers meant exclusively for the purpose of testing. It matters most what this process is being thought as by the development team, project...


    January 19, 2009  10:14 AM

    Bugs are invincible, developers have to be convincible



    Posted by: Jaideep Khanduja
    Bug, Bug Control Management, Bug Management, developer, QC, software, software development, software quality, software quality assurance, Software testers, software testing, tester

    Bugs are often invincible during development, especially in large projects when multiple sub-teams of developers are working on development of different sub-modules of the project. The software developed (or during development) will always appear innocent and bug-free to the team of developers. It...


    January 12, 2009  10:04 AM

    Top 5 Quality killers in a software product



    Posted by: Jaideep Khanduja
    business management, business requirements, customer requirements, defect free software, Development, documentation, Project Development, Project Lifecycle, project management, SDLC, software, software development, software quality, software quality assurance, software requirement, software testing

    In software development project what matters most is the timely accurate delivery that gives the benefit of defect free product, customer satisfaction, profits, market edge, growth, motivation across the organization etc. All this is not easy to achieve having so many enemies in and outside the...


    January 9, 2009  9:55 AM

    Top 10 reasons to prove software development is an easiest job



    Posted by: Jaideep Khanduja
    developer, software development, software quality, software testing

    Software development is the easiest task and requires no development or quality standards, provided you are ready to manufacture software which: - Is full of bugs - Has no buyer - Is never ready to launch - Has success-failure ratio as 0:100 - Is ready for unlimited budget inflow - Is only...


    January 7, 2009  9:59 AM

    Reference Model in Software Development – a boon for Project Manager



    Posted by: Jaideep Khanduja
    Development Manager, Project Development, Project Head, project management, Refrence Model, software development, SoftwareProjectManager

    A reference model is a non-arbitrary model of software that is to be referred to when a new software requirement comes from a customer. The reference model will suit and fit most of the requirements given by the customer. The model is the most ideal scenario befitting the technical and functional...


    January 2, 2009  9:45 AM

    Timesheet – its purpose, use and importance



    Posted by: Jaideep Khanduja
    developer, Development Manager, measuring effectiveness, Project Development, project management, project manager, software, software development, tasksheet, team management, tester, timesheet

    In an organization engaged in software development business, timesheet is filled by all developers and testers working on any project. Timesheet a sheet of pre-formatted fields in which daily tasks performed by each person are filled in their individual sheet. The intent of timesheet varies from...


    December 30, 2008  9:46 AM

    The charter of a Project (or Development Manager) at the start of a new Development



    Posted by: Jaideep Khanduja
    Development Manager, Project Development, Project Head, project implementation, Project Lifecycle, project management, project manager, software development, SoftwareProjectManager

    The charter of a project manager or development manager at the start of a new project which requires extensive fresh development comprises of many pitfalls or showstoppers. To win over them, the project manager or development manager requires a well defined charter to adhere to. The key points...


    December 17, 2008  10:08 AM

    When your development team is at job – don’t interrupt



    Posted by: Jaideep Khanduja
    development approach, Project Development, Project Head, project management, project manager, software, software development, SoftwareProjectManager

    When a new project lands into the hands of a project manager for development, he converts the whole project into smaller units and allocates it to different developers. Developers are divided into the groups based on the work allocated. These teams prepare their plan to develop and start working...


    December 15, 2008  9:55 AM

    Mr Tester, please feel PRIDE in doing what you are doing at job



    Posted by: Jaideep Khanduja
    Project Development, software, software development, Software testers, softwaretesting, tester

    Hey my dear Tester, what you are doing is a tremendous effort in streamlining the business of your organization. It is you who understands the business requirements of your customer, learning their business rules, understanding the product built by your development team to cater to those needs,...


    December 8, 2008  10:07 AM

    15 checkpoints for a Project Manager at the start of a new Project



    Posted by: Jaideep Khanduja
    ChangeManagement, development approach, implementation approach, measuring effectiveness, metrics, project implementation, project management, project manager, software development, team management

    Usually at the start of a new project, a project manager has to forget the sad points of the previous projects and also to get to ground from the unusual achievements too. At this juncture a project manager is supposed to start afresh with new zeal, a new team or new members in the team, a new...